Abstract:
A hybrid single and aggregation sale system is disclosed. This invention provides the mechanism: aggregating the individual purchase, grouping into the buying power, promoting efficient way for selling goods. The system has two styles: explicit and implicit style. Explicit style defines the limitation of availability etc. deal start time, end time, which the implicit style doesn&#39;t define. For explicit style, despite the time of purchasing, the system counts the total sold units in each sequential aggregation period from start time to end time, applies the maximum sold units as buyer&#39;s aggregation sold number, and thus the same final aggregation price will apply to the buyers who entitles same aggregation period. For implicit style aggregates the total units depending on the individual entitled aggregation period, the different order time might results the difference on the final aggregation price. The system allows the price match for disadvantaged buyer, etc earliest buyer. The buyer pays the price at front; the sellers handle and ship the items after the confirmation. After system aggregate the sale, the system credits the difference between prepaid and final aggregating price into the customer&#39;s prefer account. Buyer should order with caution because the buyer is bound to the deal.

Description:
RELATED APPLICATIONS  
       [0001]     The present application claims priority to U.S. Provisional Patent Application No. 60/678,378, filed May 7, 2005, the contents of which are incorporated herein by reference. 
     
    
     FIELD OF THE INVENTION  
       [0002]     This invention relates to electronic commerce providing a system and method for taking individual orders from individual buyer into group purchasing.  
       BACKGROUND OF THE INVENTION  
       [0003]     Electronic commerce benefits the buyer with advantages on purchasing power. With online information abundant, buyers can easily locate sellers who offer the lowest price. Different websites various methods for promoting goods or services online, for example, bidding systems as with ebay.com, buyers naming their price as with priceline.com, the traditional store style where products are offered for set prices, the sellers naming their price through a third party stores as with amazon.com and conditional aggregation systems that group individual potential buyers to achieve low price under certain conditions.  
         [0004]     The bidding system, as ebay.com, offers an auction channel for sellers. Today, small business owners are actively sellers, and they create multiple bidding items for sale online and accept the bid price at the end of auction for sale of the item. The traditional online store as amazon.com, offers competitive price to attract the buyers. The buyer naming price style as priceline.com offers an alternative way to buy goods and services. The order is taken when there is a seller that agrees with the buyer&#39;s price. The conditional aggregation style aggregates individual orders, and the contract is implemented when the condition is met.  
         [0005]     The present system provides the style of hybrid—store style with aggregation capability. The bidding system, traditional store style and the buyer naming price style don&#39;t have the aggregation capability; the final aggregation price depends on the desirability. Though the auction system offers a Dutch auction variant to have multiple item sales, the price is not determined by aggregation purchasing but the desirability of product itself. Additionally, the bidder has to wait a long period until the auction is end.  
         [0006]     The conditional aggregation style does offer the aggregation capability, but both participants to the sale uncertainty as to whether the sale will ever be completed. Only when condition is met is the deal fulfilled. The buyer, who is eager to receive the product, has to wait until the deal is expired or consummated before receiving the item because the deal won&#39;t complete until the minimum condition is met. Therefore, this method is less attractive despite the fact that a lower price for purchasing the item may be achieved. Additionally, dynamic market conditions could lower the price and attract buyers away from the deal. Buyers withdrawing from the order before consummation or expiration will inevitably happen, and the whole deal may be cancelled because due to order cancellation. This will leave the buyer without a product, and the seller without a sale. Seller will also have increased inventory cost. Therefore, this method of sales is undesirable.  
         [0007]     The present invention takes the desirability and quantity into the consideration and provides a new method to aggregate individual sales to achieve a lower sale price for the buyer. The present invention provides a new channel for individual, small business owners and manufactures to sell directly to a consumer. It enables a seller to promote items at low prices and compensate with large sale volumes. Individual items are sold when a buyer orders. In other words, the sellers make the sale immediately when buyers place the order. Seller performs shipping and handling after the order is confirmed. Unlike auction or conditional aggregation style, Buyer does not need to wait until the meeting of a specified condition for the deal to end. Buyers also enjoy lower prices by aggregating the individual sales into group purchasing. Buyers prepay the retail price up front and later the system aggregates the sales and lower the prices. The differences between prepaid and the price after aggregation will be credited into the customer account. The system works like a traditional store with the additional feature of group aggregation. This creates win-win situation for the buyer and the seller.  
       SUMMARY OF THE INVENTION  
       [0008]     The present invention provides a method, and a system for performing the method, of aggregating sales of a product. The method comprises the steps of displaying product information to a buyer including a price, charging the price to the buyer and shipping the item to buyer in response to the buyer selecting the product for purchase, and providing a rebate to the buyer, the rebate calculated by determining the aggregation of sales of the product to the buyer and to other buyers occurring over a time period and comparing the aggregated sales number to a price sheet listing aggregated sales numbers cross-referenced to discounted sales prices. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0009]      FIG. 1  is a diagram of the system according to a preferred embodiment of the present invention;  
         [0010]      FIG. 2  is the seller summit product page includes two selling styles.  
         [0011]      FIG. 3  is explicit selling style elements on webpage.  
         [0012]      FIG. 4  is implicit selling style elements on webpage.  
         [0013]      FIG. 5  is user-logging page.  
         [0014]      FIG. 6  is check out page contain with quantity number to purchase, ship info and credit info.  
         [0015]      FIG. 7  is three major system processing.  
         [0016]      FIGS. 8-10  is the program flow diagram of system processing the order from the buyer.  
         [0017]      FIG. 11  is the rebate process.  
         [0018]      FIG. 12  is the program flow diagram of explicit price calculation process.  
         [0019]      FIG. 13  is the program flow diagram of implicit price calculation process.  
         [0020]      FIG. 14  is the example data of seller table.  
         [0021]      FIG. 15  is the example data of buyers table.  
         [0022]      FIG. 16  is the daily sold record table for aggregation period 7 days.  
         [0023]      FIG. 17  is the daily sold record table for aggregation period 15 days.  
         [0024]      FIG. 18  is the table shows the result of explicit style. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0025]     For an understanding of the preferred embodiment of the present invention, one must understand the following terminology: 
        1. Deal: represents the sale submitted by seller.     2. Aggregation period: the certain days to aggregate the sale. Every buyer belongs to a membership, different membership represents different aggregation periods.     3. Price list: the seller submits to the system, defines what price would be given if the item sold above certain quantity. The price list states the relationship between the number units sold and price offering.     4. Bulk price: the product&#39;s price. The quantity that a buyer orders qualifies for specific price points. For example, the price list offers a price of $15.00 per unit if the ordered quantity is greater then or equal to one. If the order greater than or equal to fifty, then the price would be $10.00 per unit.     5. Single item price: by default, the seller&#39;s price list lists a single unit price. Sellers must define the single unit price. This is the price per unit that the buyer paid up front. If the buyer bought purchases a higher quantity, the buyer qualifies for the bulk price, and the bulk price is charged per unit. After Cleanout activates, the single item price would be the price whichever less between the cleanout price and bulk price.     6. Final aggregation price: the final price is. given to the consumer after aggregating sold items. The final aggregation price is the price according to the price list that will be applied based upon the total number of units sold.     7. Rebate waiting period: considering the shipping and possible return of the item, the rebate waits for a specified amount of time to pass.     8. Notify Threshold: when current number of items available to be sold goes below a threshold, the server would notify the seller. In response, the seller might or might not take action to confirm more items are available for sale and update the total item number.     9. Cleanout activation threshold: the system activates the cleanout price when the item sold are below a specified number. Instead of a single unit price, stated in the price list, the buyer prepays the cleanout price per unit after the cleanout option is activated.     10. Secondary aggregation number: the second aggregation number next to the single unit price in the price list.     11. Secondary aggregation price: the second aggregation price next to the single unit price in the price list. For instance, the seller&#39;s price list is: if sold number equal to or greater than one unit, price is $10.00, if sold number greater than or equal to 50 units, price is $9.00. Here 50 units are secondary aggregation number. A price of $9.00 is the secondary aggregation price.        
 
         [0037]     The preferred embodiment of the present invention provides a system and method for accepting a seller&#39;s price list, calculating the aggregation price based upon demand, and crediting the difference back to user&#39;s account. The users are categorized into different aggregation periods via joining the different memberships. Depending on the business need, the aggregation period is defined by the implementer&#39;s decision. For illustration purpose, the example in this description defines four categories—membership A is 1 day, membership B is 7 days, membership C is 15 days and membership D is 30 days.  
         [0038]     The system is divided into two styles: the explicit style and implicit style. Referring to  FIG. 2 , explicit style is a method which enables sellers to define the following information: a product description ( 10 ), a product picture ( 15 ), a price list ( 20 ), a total number offered ( 25 ), a deal start time ( 30 ), a deal end time ( 40 ), and a notification threshold ( 70 ) is optional.  
         [0039]     Implicit style is a method that enables a sale without defining a deal end time. The seller provides the product description ( 10 ), the product picture ( 15 ), the price list ( 20 ) and the total number offer ( 25 ). For implicit style, the following information is optional: the deal start time ( 30 ), the notification threshold ( 70 ), a cleanout activation threshold ( 75 ) and a cleanout price ( 80 ). Implicit style continues to sell the product until current inventory is sold out, and that is why the start time and end time are not necessarily needed. In implicit style, the start time could be default to be the timestamp when system publishes the request online (i.e. immediately).  
         [0040]     The buyers purchase or are awarded the aggregation period time via joining a membership. Different memberships represent the different periods time for the aggregation period. The final aggregation price is calculated using the number of units sold during the defined aggregation period.  
         [0041]     Explicit style takes the maximum-sold record during the whole deal period. Buyers all pay the same price if they are entitled to the same membership, so there is no need of price match in explicit style. Implicit style has price differences for different buyers depending upon when the buyer places his order, so price match may be given to the disadvantaged buyer, the early buyer and latest buyers.  
         [0042]     If sale style is implicit, the implicit phenomena appear: a display of the number of items remaining is provided, the final aggregation price might or might not be shown above the secondary aggregation price. In another view, when the number of items currently left is below the secondary aggregation number, the buyers who anticipate the purchase are disadvantaged buyer. To encourage the buyer to continue in his order, the optional cleanout price is promoted to guarantee that remaining items are sold.  
         [0043]     The system receives the information from the seller when placing the item and creates the deal page online. If the buyers decide to purchase, the buyer logs into the system, places the order, provide the shipping address and credit or bank account, and pays the amount of a single item price multiplied by the order quantity.  
         [0044]     When the seller confirms the payment from the buyer, the seller handles and ships the product to the buyer within an agreement time frame.  
         [0045]     After the rebate waiting period, the system aggregates the individual sale into the group, calculates the final aggregation price based on the buyer&#39;s aggregation period and seller&#39;s price list, and the difference between the final amount and paid amount is credited back to the user&#39;s credit card or bank account or their account with the merchant.  
         [0046]     Explicit style has an advantage or implicit style in that the final aggregation price of the item is irrelevant to order date. Different membership levels entitle every buyer the same price regardless of when the buyer placed the order because the final price is determined the number of items sold after the expiration of a defined period. Price match is not an issue.  
         [0047]     A disadvantage of explicit style is that the seller clearly specifies when the deal will be expired, and when that time has passed, the deal is automatically ended despite the fact that items may remain unsold. If the seller wants to continue, the seller is required to resubmit the item with a new aggregation period. Additionally, the credit waiting period is longer in comparison to implicit style.  
         [0048]     Implicit style has the advantage that the seller does not specify the aggregation period so that the deal does not expire. The deal ends only when the item is sold out.  
         [0049]     In comparison to explicit style, the rebate process starts at an earlier time and credit waiting period is short.  
         [0050]     A disadvantage of implicit style is that the different order dates might result in different in final aggregation prices for different buyers. As a result, price match is implemented in implicit style. The early buyer and latest buyer are disadvantaged buyer. Certain promotion should be taken to encourage the disadvantage buyers to purchase. For example, a guarantee discount price can be specified for the first 20 buyers, and a cleanout price can be specified for the last buyers to purchase. Moreover, in implicit style, the rebate waiting period may be shorter than explicit style&#39;s rebate waiting period because it is of a specified duration.  
         [0051]     The rebate waiting period is a factor that may be determined by the implementer. If the return policy were separate from the aggregation price, which means when the buyer purchases the item and returns the item later, the aggregation price would not change because of the returning item.  
         [0052]     In implicit style, the earliest rebate process might begin at the latest day of aggregation. For instance, if buyer A has membership B and the aggregation period is 7 day, buyer A place order on 20:15:23 1-1-2004, and the latest date of aggregation is 20:15:23 1-8-2004.  
         [0053]     In explicit style, the earliest rebate process might starts after deal&#39;s end time.  
         [0054]     The return policy may be a factor affecting the aggregation price. For example, when the buyer purchases and returns an item, the aggregation price might increase due to the returned item.  
         [0055]     For implicit style, the earliest rebate process may start as late as the return policy time frame (defined by seller) plus the latest date of aggregation and the date consumer received shipping of the item.  
         [0056]     The last day of aggregation date could be later than the date consumer received shipping. For instance, the buyer A has 30 day aggregation period, buyer A order on 20:15:23 1-1-2004, the last aggregation date is on 20:15:23 1-31-2004, buyer A received product on Jan. 12, 2004. For explicit style, the earliest rebate process starts after the return policy time frame plus the latest date between end of deal and the date last consumer received shipping.  
         [0057]     As demonstrated as above, the rebate-waiting period is a factor that is determined by business considerations and negotiation, rather than a precise value. For example, the rebate waiting period might be defined by as much as a six to ten week period after the last day of aggregation period.  
         [0058]     A hybrid aggregation purchase system may also be implemented using different membership categories. The different membership categories implement different aggregation periods. The longer the aggregation period, the larger the aggregation number will be. As a result, the final aggregation price will be less.  
         [0059]     The system also need provide a system for individuals to purchase a membership. For example, the system offers different prices for different memberships.  
         [0060]     Referring to  FIG. 1 , this is the diagram of a system according to the preferred embodiment. Buyers ( 1 ) and Sellers ( 2 ) are connected via a network. Clients include sellers and buyers utilizing the terminals, such as computer, laptops, interactive TV, personal digital assistants (PDAs), telephones communicating with the system server ( 3 ) over the network. The system server keep the records of buyer&#39;s and seller&#39;s information in a database, publishes the seller&#39;s product online and confirms the buyer&#39;s order. The network is preferably the world wild web, but the network is not so limited and may comprise merely a telephone network.  
         [0061]     In  FIG. 2 , the seller may provide the elementary information for placing a product for sale on the system. Sellers must choose one of two selling styles: implicit style  50  and explicit style  60 . Based upon this selection, information is submitted differently. This results in showing different information to the seller based upon the style of selling he has chosen and adopting different price calculation methods.  
         [0062]     As discussed above, implicit style  50  is the style where the system continuously sells product without having a sale expiration day. Explicit style  60  is the style where the system is limited to product sale within a fixed time frame.  
         [0063]     An item picture  15  is the item&#39;s picture provided by seller. An item description  10  is textual information describing the item&#39;s features. A price list  20  is the relationship between the aggregation sold unit number and price specified by the seller. A total item offer  25  is the total quantity of product offered by the seller. If the item is sold out, the deal will end regardless of whether the deal end time has occurred or not. The system may or may not publish information regarding completed sales.  
         [0064]     A deal start date  30  is the deal&#39;s beginning time. In explicit style, the deal start date is published to the buyer. In implicit style, a deal start date is optional, and the default value is the time when system publishes information online. The default date and time format is HH:MM:SS MM-DD-YYYY.  
         [0065]     A deal end date  40  is the deal&#39;s expiration time. The deal will end if deal end date has passed or the item is sold out. In explicit style, the deal end time is published on screen. In implicit style, there is no deal end date. The default format is HH:MM:SS MM-DD-YYYY.  
         [0066]     Notification threshold  70  represents a point whereby the seller is informed that only a specified amount of product remains. When the amount of product is below the notification threshold, the system would notify the seller and the seller can take the opportunity to indicate that more product is available, if possible. It is optional for seller. If seller does not specify the value, then the system will not create the event to notify the seller.  
         [0067]     Cleanout activate threshold  75  indicates the number of items remaining that will activate a cleanout price. If the quantity of product left is below the cleanout activate threshold, the system would activate the cleanout price and notify the seller. The default value is the secondary aggregation number. It is optional for seller, and is only available in implicit style. If seller does not specify a value, the system won&#39;t create the event to activate a cleanout price.  
         [0068]     The activate condition choice  78  includes the options: “as soon as possible” means the activate cleanout when the current number of items left is below the cleanout activate threshold. “Wait for ______ hours for seller response to the notification threshold” means the system will wait up to a specified number of hours for a seller&#39;s response on notification threshold. Cleanout price  80  is the prepaid price after cleanout is activated. Default value is the secondary aggregation price. Cleanout price is only available when seller specifies the cleanout activate threshold. A submit button  85  is provided for submitting the information to server. Seller can login and change the deal information before the deal&#39;s expiration time.  
         [0069]      FIG. 3  is the diagram showing the explicit deal information online. When the seller logs into the system and chooses the explicit style to sell a product, the seller submits the following information: style ( 50  or  60 , ref  FIG. 14, 1700 ), Product description ( 10 ) and picture if available ( 15 , ref  FIG. 14, 1200 ), the Price List ( 20 , ref  FIG. 14, 1600 ), Total items offer—Quantity ( 25 , ref  FIG. 14, 1500 ), Deal start date ( 30 , ref  FIG. 14, 1300 ), Deal end date ( 40 , ref  FIG. 14, 1400 ) and Notification threshold ( 70 , ref  FIG. 14, 1800 ) is optional.  
         [0070]     The server  3  receives the information submitted by seller, creates a record in a seller table in database. A Deal ID ( 1000 ) is a unique number generated to distinguish the deals submitted by sellers. As the  FIG. 14  seller table shows, Deal ID  1  ( 1001 ) represents a deal record from seller 30max.com ( 1101 ), the product is Toshiba E330 PC handheld ( 1201 ). The deal starts at 12:00:00 Oct. 12, 2004 ( 1301 ), ends at 12:00:00 Nov. 10, 2001 ( 1401 ) with a quantity of 500 ( 1501 ).  
         [0071]     The seller provides the price list (ref  FIG. 14, 1601 ) as:  
                                                   If (num &gt;= 1) price is $345.00           If (num &gt;= 50) price is $330.00           If (num &gt;= 100) price is $315.00           If (num &gt;= 200) price is $300.00.                      
 
 and style the seller has chosen ( 1701 ) is Explicit. One hundred units is the notification threshold ( 1801 ). If left item number below the number  100 , notify the seller, seller could have chance to confirm and update the total item offer number. 
 
         [0072]     The system publishes the relevant information provided by the seller in corresponding field in a database. The server ( 3 ) dynamically updates the following information: membership correspondent price ( 140 ), today sold ( 145 ), item number left ( 155 ) and current date ( 161 ).  
         [0073]     The seller will also specify the aggregation period for the various membership levels. For example:  
         [0074]     Membership A Aggregation Sold Number (1 Days) 10  
         [0075]     Membership B Aggregation Sold Number (7 Days) 50  
         [0076]     Membership C Aggregation Sold Number (15 Days) 100  
         [0077]     Membership D Aggregation Sold Number (30 Days) 120  
         [0078]     According to the price list offer by seller, the deal ID  1 &#39;s final aggregation price will be:  
         [0079]     Membership A: $345.00.  
         [0080]     Membership B: $330.00.  
         [0081]     Membership C: $315.00.  
         [0082]     Membership D: $315.00.  
         [0083]     This information would publish based upon the viewing member&#39;s membership level.  
         [0084]      FIG. 4  shows the implicit style deal&#39;s information published by the system. When sellers choose the implicit style to sell the product, the following information is submitted: product (description ( 10 ) and picture if available ( 15 , ref  FIG. 14, 1200 ), the Price List ( 20 , ref  FIG. 14, 1600 ), Total item offer, Quantity ( 25 , ref  FIG. 14 .  1500 ), Deal start date ( 30 , ref  FIG. 14 .  1300 ), Deal end date ( 40 , ref  FIG. 14, 1400 ), Style ( 50  or  60 , ref  FIG. 14, 1700 ), Notify Threshold ( 70 , ref  FIG. 14, 1800 ), Cleanout Activation threshold ( 75 , ref  FIG. 14, 1900 ), Cleanout Price ( 78 ), the condition choice ( 80 , ref  FIG. 14, 2000 ). Notify Threshold ( 70 , ref  FIG. 14, 1800 ), Cleanout Activation threshold ( 75 , ref  FIG. 14, 1900 ), Cleanout Price ( 78 ) and the condition choice ( 80 , ref  FIG. 14, 2000 ) are optional.  
         [0085]     When the system receives the information, it creates a record in the database table, and a deal ID number distinguishes the deal submitted by the seller. As described above, the  FIG. 14  seller table shows, ID  3  ( 1003 ) represents a deal record from seller 30max.com ( 1103 ), the product is Toshiba E330 PC handheld ( 1203 ). If the seller didn&#39;t submit the start time, the start time defaults to the earliest time system received the deal. The seller provides the price list ( 1603 ) as:  
         [0086]     If item &gt;=1 unit, the price is $345.00  
         [0087]     If item &gt;=50 unit, the price is unit $330.00  
         [0088]     If item &gt;=200 unit, the price is unit $300.00,  
         [0089]     The seller choice Style ( 1703 ) is Implicit, and one hundred units is the Notification threshold ( 1803 ). Fifty units is the default value of cleanout activation threshold. If the current number of items left is below the cleanout activation threshold, the cleanout process will activate ( 1903 ) in twenty-four hours unless the seller intervenes. $330.00 is the default value of cleanout price ( 2003 ).  
         [0090]     If the left item number is below the number 100, notify the seller, and the seller could have chance to confirm and update the total number of items offered. If left number is below 50, the system sends another message to the seller that the cleanout condition is impending. If the seller has not responded to the notification threshold, the system check whether current time over 24 hours from the time system sent the notification. If yes, the cleanout process activates. After the cleanout price activates, the price of the item is adjusted from the single unit price to the next best pricing level is offered.  
         [0091]     The system publishes that information in correspondent field at  FIG. 4 : Product description Toshiba E330 PC handhold ( 110 ), product picture if available ( 100 ), price list offered by seller is ( 120 ),  
         [0092]     If item &gt;=1 unit, the price is $345.00  
         [0093]     If item &gt;=50 unit, the price is unit $330.00  
         [0094]     If item &gt;=200 unit, the price is unit $300.00,  
         [0095]     the total number of units offered is 334 units ( 150 ), the deal start time is 12:00:00 Oct. 12, 2004, the seller didn&#39;t specify a start time (therefore the start time is when the system publishes the deal online ( 160 )). Moreover, the following information dynamically updates: membership correspondent price ( 140 ), number sold today ( 145 ), number of items left ( 155 ) and current date ( 161 ).  
         [0096]     For example, if current aggregation sold number for each membership as following:  
         [0097]     Membership A Aggregation Sold Number total (1 Days) 10 items  
         [0098]     Membership B Aggregation Sold Number total (7 Days) 50 items  
         [0099]     Membership C Aggregation Sold Number total (15 Days) 100 items  
         [0100]     Membership D Aggregation Sold Number total (30 Days) 120 items  
         [0000]     The deal ID  1 &#39;s current aggregation price will be:  
         [0101]     Membership A: $345.00.  
         [0102]     Membership B: $330.00.  
         [0103]     Membership C: $330.00.  
         [0104]     Membership D: $330.00.  
         [0105]     This information would published on the membership correspondent price ( 140 ),  
         [0106]      FIG. 5  shows the login information for clients.  
         [0107]     If wile viewing a product, the user decides to make a purchase, by clicking on a “BUY” ( 170 ) button, the system validate the user status. If the user has not logged, the user must do or become a member ( 190 ) if the user has no username ( 180 ) and password ( 185 ).  
         [0108]      FIG. 6  shows the information that the user sees at checkout. After a user successful logs in, in  FIG. 6  the buyer needs to provide the quantity ( 200 ) that the buyer wants to purchase, a shipping address ( 230 - 260 ) and credit card or bank account information ( 215 - 225 ).  
         [0109]     The address is defaulted to be the address stored in membership information and credit card or bank information is defaulted to be the credit card or bank information provided by the buyer when joining, if any was provided.  
         [0110]     If buyer wants to change the quantity, the buyer may modify the number in quantity field, and click on “update” ( 210 ). The system will then reflect the changes that the user made. The system also calculates the total price ( 205 ).  
         [0111]      FIG. 7  demonstrates the three major processes in the server: the Order Process ( 280 ), Price Define Process ( 285 ) and Rebate Process ( 290 ). The Order Process is an order procedure, and the logic of the order process is shown in  FIGS. 8-10 . The Price Define Process is a procedure that calculates the item price dynamically. The price define process is shown in  FIGS. 12 and 13 . The Rebate Process is the process whereby the system credits back money to buyers after finalizing the item&#39;s aggregation price and is shown in  FIG. 11 .  
         [0112]     After the buyer clicks the checkout ( 265 ), system receives the buyer&#39;s request and starts the order process as shown in  FIG. 8 . The system checks whether the user is a valid user ( 300 ), and if not, returns and notifies the error and asks the user to join the club ( 310 ). If the buyer is a valid user, the system verifies whether the deal is expired ( 320 ), if the deal is expired, the system notifies the user that the order cannot be processed because deal has ended ( 340 ).  
         [0113]     If the deal has not expired, the system compares the quantity of buyers ordering and the number of available ( 330 ). If the quantity is valid and there are enough items for purchasing, the process continues to  FIG. 9 . Otherwise, the system notifies the buyer that there are not enough items for purchase and asks the buyer to modify the order quantity. Next, the system checks whether the style is the implicit style ( 342 ), and, if yes, the system checks whether the cleanout process has been activated ( 344 ). If yes, the price would be whichever is less between the cleanout price and the bulk price, depending on the buyer&#39;s order quantity ( 346 ). If the deal is explicit style, the system will get the single item price based on buyer&#39;s order quantity. If the buyer buys a large quantity and qualifies for a bulk price, the price is the bulk price stated in price list. Otherwise, the single item price would be the single unit price ( 348 ). Next, the system applies the total price to the credit card or bank information ( 350 ). The total price is the quantity purchased multiplied by the price.  
         [0114]     Next, the process advances to  FIG. 10 . If the charge is successful ( 352 ), the system checks whether the number of items left is below the notification threshold ( 366 ). If the number is below the threshold, the system should only notify the seller that current left item number is below the threshold for the first time and save the notification&#39;s date and time into the database ( 368 ). Meanwhile, the system checks whether the style is the implicit style ( 356 ), and, if yes, the system checks whether quantity of items left is below the cleanout activation threshold ( 358 ). If yes, the system checks whether the activation condition ( 360 ) has been met. If it has been met, the cleanout process activates ( 370 ), and if it has not been met, the server will continue to verify.  
         [0115]     When the current number of items left is above the cleanout threshold, the system starts aggregation. If the deal is implicit style, the apply implicit price calculate process ( 380 ) is started. If the deal is explicit style, the apply explicit price calculate process ( 385 ) is started. The detail of implicit price calculate process and explicit price calculate process will be explained below. Each membership&#39;s aggregation price will publish on field  140 , and the aggregation price is not the final price for item, it just shows the price trend of the item to buyers.  
         [0116]     The system updates the relevant information into the database ( 362 ), and notifies the user that the order is processed ( 364 ). The system creates or updates the record in buyer&#39;s table  FIG. 14 , including fields such as: Customer Name ( 2100 ), Deal ID ( 2200 ), Aggregation Period ( 2300 ), Order Time ( 2400 ), Quantity ( 2500 ), Single Item Price ( 2600 ), Prepaid ( 2700 ). If the charge fails, the system notifies user that his credit was inadequate ( 354 ).  
         [0117]      FIG. 11  is the diagram of the rebate process. After the rebate waiting period, the rebate process calculates the final aggregation price and credits the difference back to the customer&#39;s preferred account. The method used differs based upon whether the deal  1  explicit or implicit style. Explicit style uses the max aggregation sold number during the aggregation period from start time to the end time. Implicit style only counts the max aggregation sold number in the period, starting with the date that the buyer ordered the product. According to the choice style, the system applies the implicit style calculation process  380  or explicit style calculation process  385 . The credit total amount equals (the purchase price minus the final aggregation price) multiplied by the quantity. The system updates the database information  390  and notifies the credit event  395 . In  FIG. 15 , the system updates the buyer&#39;s table on Aggregation sold Number ( 2800 ), Final Aggregation Price ( 2900 ) and Rebate Credit ( 2950 ).  
         [0118]      FIG. 12  shows the price calculation process in implicit style. The process  380  is demonstrated as follows. When the rebate process starts, the first step  400  is to retrieve the buyer&#39;s information, such as: the purchase date, aggregation period, the quantity, and prepaid price from the buyer table. In a next step  410 , to determine the max aggregation sold number in aggregation period, the system counts product sold number for a sequential aggregation period, which must include the order date:  
         [0119]     For instance, Sam Daily (ref  FIG. 15, 2217 ), who has membership A, entitles aggregation period as 1 day ( 2318 ).  
         [0120]     The system counts the product sold number: 
        1. From: 1-day period prior to the time ordered,     2. From: 1-day period after the time ordered.        
 
         [0123]     The larger of the two numbers will be the aggregation sold number.  
         [0124]     Referring to  FIG. 15 , Sam Daily purchases the product on Oct. 12, 2004 ( 2417 ). Oct. 12, 2004 is the beginning of the deal, no prior record happened before this date. The sale style is implicit.  
         [0125]     On Oct. 12, 2004, five units were sold 5 ( 501 ). On Oct. 13, 2004 three units were sold ( 502 ). Buyer Sam Daily bought 1 unit ( 2517 ) and prepaid the unit for $345.00( 2618 ). The aggregation sold number is calculated, where Agg ( ) represent the aggregation sold number and Num ( ) represent the sold number on specific date.  FIG. 16  shows the daily sold record information as in  FIG. 17 . 
 
Agg(Oct. 12, 2004-Oct. 13, 2004)=Num(Oct. 12, 2004)+Num(Oct. 13, 2004)=5(501)+3(502)=8(2817); 
 
         [0126]     If Sam Daily purchases 50 items, the instant unit price will be $330.00 instead of $345.00.  
         [0127]     Buyer Jack Mackin (ref  FIG. 15, 2218 ) purchases the product on Oct. 22, 2004. Quantity is 1. The sale style is in implicit style.  
         [0128]     On Oct. 22, 2004 six items were sold (ref  FIG. 17, 511 ), and on Oct. 21, 2004 fourteen items were sold (ref  FIG. 17, 510 ). On Oct. 23, 2004 seventeen items were sold (ref  FIG. 17, 512 ). 
 
Agg(Oct. 21, 2004-Oct. 22, 2004)=6+14=20; 
 
Agg(Oct. 22, 2004-Oct. 23, 2004)=6+17=23, 
 
         [0129]     Because Agg (Oct. 22, 2004-Oct. 23, 2004)&gt;Agg (Oct. 21, 2004-Oct. 22, 2004), Buyer Mackin&#39;s aggregation sold number is 23( 2818 ).  
         [0130]     Buyer, who has membership B, entitles aggregation period as 7 day.  
         [0131]     The system counts all possible sequential 7-day aggregation period, which must include the order date, as following case:  
         [0132]     1. From: the 6 day period prior to the time ordered  
         [0133]     2. From: 5 days prior to the time ordered to the 1 day after time ordered.  
         [0134]     3. From: 4 days prior to the time ordered to the 2 days after time ordered.  
         [0135]     4. From: 3 days prior to the time ordered to the 3 days after time ordered.  
         [0136]     5. From: 2 days prior to the time ordered to the 4 days after time ordered.  
         [0137]     6. From: 1 day prior to the time ordered to the 5 days after time ordered.  
         [0138]     7. From: the time order and including the 6 day period after the time ordered.  
         [0139]     The aggregation sold number will be selected as the case that results in the highest number.  
         [0140]     Buyer Alex Donald ( 2101 ) purchases the product on Oct. 12, 2004 ( 2401 ). Quantity is 1. Oct. 12, 2004 is the beginning of the deal, and no prior record happened before this date. His Aggregation period is 7 days ( 2310 ). The sale style is implicit. 
 
Agg(Oct. 12, 2004-Oct. 18, 2004)=Num(Oct. 12, 2004)+Num (Oct. 13, 2004)+Num(Oct. 14, 2004)+Num(Oct. 15, 2004)+Num(Oct. 16, 2004)+Num(Oct. 17, 2004)+Num(Oct. 18, 2004) 
 
Agg(Oct. 12, 2004-Oct. 18, 2004)=5+3+7+3+12+15+9=53 
 
         [0141]     Buyer Alex Donald&#39;s aggregation sold unit number is 53.  
         [0142]     Buyer Emma Natasha ( 2110 ) purchases the product on Oct. 25, 2004( 2410 ), and her quantity is 1 ( 2510 ).  
         [0143]     From 6 days prior to Oct. 25, 2004 to the order time Oct. 25, 2004: 
 
Agg(Oct. 19, 2004-Oct. 25, 2004)=98(3108); 
 
         [0144]     From 5 days prior to Oct. 25, 2004 to 1 day after Oct. 25, 2004: 
 
Agg(Oct. 20, 2004-Oct. 26, 2004)=87(3109). 
 
         [0145]     From 4 days prior to Oct. 25, 2004 to 2 days after Oct. 25, 2004: 
 
Agg(Oct. 21, 2004-Oct. 27, 2004)=84(3110). 
 
         [0146]     From 3 days prior to Oct. 25, 2004 to 3 days after Oct. 25, 2004: 
 
Agg(Oct. 22, 2004-Oct. 28, 2004)=81(3111). 
 
         [0147]     From 2 days prior to Oct. 25, 2004 to 4 days after Oct. 25, 2004: 
 
Agg(Oct. 23, 2004-Oct. 29, 2004)=96(3112); 
 
         [0148]     From 1 day prior to Oct. 25, 2004 to 5 days after Oct. 25, 2004: 
 
Agg(Oct. 24, 2004-Oct. 30, 2004)=89(3113); 
 
         [0149]     From the order time of Oct. 25, 2004 to 6 days after Oct. 22, 2004: 
 
Agg(Oct. 25, 2004-Oct. 31, 2004)=91(3114); 
 
         [0150]     The max aggregation sold number among Agg (Oct. 19, 2004-Oct. 25, 2004), Agg (Oct. 20, 2004-Oct. 26, 2004), Agg (Oct. 21, 2004-Oct. 27, 2004), Agg (Oct. 22, 2004-Oct. 28, 2004), Agg (Oct. 23, 2004-Oct. 29, 2004), Agg (Oct. 24, 2004-Oct. 30, 2004), Agg (Oct. 25, 2004-Oct. 31, 2004) is: 
 
Agg(Oct. 19, 2004-Oct. 25, 2004)=98. 
 
         [0151]     Emma Natasha&#39;s aggregation sold number is 98.  
         [0152]     If the buyer belongs to membership C or membership D, the rule is same, except the aggregation periods are different.  
         [0153]     For buyers who belong to membership C, the aggregation sold number is 212 ( 3308 ). For buyers who belong to membership D, the aggregation sold number is 334.  
         [0154]     In a third step  420 , the aggregation sold number is applied to the price list to determine the final aggregation price, which equals (prepaid price minus final aggregation price) multiplied by the quantity.  
         [0155]     Emma Natasha&#39; aggregation sold number is 98. Applying the price list ( 1603 ), final aggregation price is $330( 2910 ), and she is credited $15.00 ( 2960 ) back to her account.  
         [0156]     In a fourth step  430 , the system credits the total back to the buyer&#39;s preferred account, updates the database and notifies the customer.  
         [0157]     During Nov. 1, 2004 (ref  FIG. 16, 3005 ), the total left item number is below the notification threshold 100( 1803 ). The seller was notified that the left item was less than notification threshold number 100( 1803 ). The seller could confirm and update the total item available item or ignore the notification. If seller wants to re-supply the product, after seller confirms that more items are available (for example, if seller confirms that there is another 100 unit items are available), the total offered items will be updated in step  434 .  
         [0158]     The seller has a choice to edit the published item information at anytime when seller has logged in. The seller will not be able to update the total item number when cleanout is activated, unless the seller decided to continue the deal and update total number of items with cleanout price as prepaid price.  
         [0159]     The Cleanout is activated on Nov. 7, 2004 if seller did not confirm more items are available upon the notification threshold event. On Nov. 7, 2004, the number of items left is less than 50, the cleanout is activated and the item price will be the price whichever less between the bulk price and cleanout price. The final aggregation price will be the price that is less between the cleanout price and aggregation price from the price list.  
         [0160]      FIG. 13  shows the price calculation process in explicit style. The process  385  starts the rebate process in a first step  405  by retrieving buyer&#39;s information, aggregation period, the quantity, single item price and prepaid price.  
         [0161]     In a second step  415 , the explicit style process determines the number of items sold during the aggregation period, which is the time of the deal for explicit style. The method is based on implicit style without the requirement that the period must include the purchase date. Instead, the period is from the start of the deal to the end. The maximum aggregation sold number would apply for the membership. In explicit style, the final aggregation price is not influenced by the order date, as with implicit style. The price match is not needed in explicit style as with implicit style. This is demonstration as following:  
         [0162]     Alex Donna has membership B, and the aggregation period is 7 days (ref  FIG. 15, 2301 ). Alex Donna ordered product on Oct. 12, 2004 (ref  FIG. 15,2405 ) and his quantity is 1. The system applies the max aggregation sold number among the aggregation periods from Oct. 12, 2004 to Nov. 10, 2004.  
         [0163]     As shown in  FIG. 16 , the max sequential 7 days aggregation period happened from Oct. 27, 2004 (ref  FIG. 16, 3004 ) to Nov. 2, 2004 (ref  FIG. 16, 3005 ). The aggregation sold number is 102 (ref  FIG. 16, 3204 ). All buyers who are in membership B entitle the same aggregation sold number as Alex Donna, in another words, all membership B buyers receive the same price.  
         [0164]     In a third step  420 , the system will apply the max aggregation sold number 102 (ref  FIG. 16, 3204 ) to seller&#39;s price list (ref  FIG. 14, 1601 ), so all buyers with membership B are entitled to the same aggregation sold number, which equals 102.  
         [0165]     Determining the final aggregation price, the total credit amount equals (prepaid price minus final aggregation price) multiplied by quantity.  
         [0166]     Alex Donna&#39;s aggregation sold number is 102, and this number applies to the price list (ref  FIG. 14, 1601 ), final aggregation price is $315 (ref  FIG. 15, 2701 ) and credited $30 (ref  FIG. 15, 2951 ) back to her account.  
         [0167]     In a fourth step  430 , the system credits the total back to the buyer&#39;s preferred account, updates the database and notifies the customer.  
         [0168]      FIG. 14  shows the exemplary seller table stored in the server. The table is corresponding to information discussed with reference to  FIG. 2  which was the Seller submit information page, such as Deal ID ( 1000 ) is a unique number identifying the deal. No duplicates are allowable, although one seller could have multiple deals, Seller ( 1100 ) is a description of the seller, Product ( 1200 ) is the product that seller posted to sell and it contains the information of description of the product detail and picture of product supplied by seller. Start Date ( 1300 ) is the time of seller wishes to publish online (If seller didn&#39;t specify the start date, the default value is the time when system server publish on web.), End Date ( 1400 ) (for implicit mode) is the time of seller wishes to stop the sale, Quantity ( 1500 ) is the total number of items the seller wishes to sell, Price List ( 1600 ): refers to the defined Price List, defined by seller, Model ( 1700 ) chosen by seller when seller submits the sale style (the different style leads the different approach towards to count the aggregation number and final price), Notify threshold ( 1800 ), Cleanout Threshold ( 1900 ) and Cleanout Price ( 2000 ).  
         [0169]      FIG. 15  shows&#39;the exemplary buyer table, the information store in system server. The table contains: Customer ( 2100 ) is the description of buyer, Deal ID ( 2200 ) is the unique number to identify the deals from the seller, Aggregation Period ( 2300 ), Order Time ( 2400 ), Quantity ( 2500 ), Single Item Price ( 2600 ), Prepaid Price ( 2700 ), Aggregation sold Number ( 2800 ), Final Aggregation Price ( 2900 ), Rebate Credit ( 2950 ). The table contains example records to demonstrate difference between explicit and implicit style when buyers purchase at different times and with difference memberships.  
         [0170]     For Explicit Style:  
         [0171]     Membership B (7 day aggregation period) buyer: Alex Donald ( 2101 ) purchase one item at the beginning of the deal Oct. 12, 2001, and Collin Fuller ( 2103 ) purchase one item at the end of the deal Nov. 10, 2001, the aggregation sold number is the same, thus the final price and rebate are the same.  
         [0172]     The difference in purchase time has no impact on the final price and rebate.  
         [0173]     With membership C (15 day aggregation period), buyer Bob Sander ( 2014 ) and Nancy Mig ( 2016 ) share the same final price and rebate credit. Comparing that to the buyer with membership B (7 day aggregation period), the membership C buyer is entitled to a larger aggregation sold number and cheaper final aggregation price.  
         [0174]     For Implicit Style:  
         [0175]     Membership B (7 day aggregation period) buyer has a difference in aggregation sold number when buyers purchase items at different times. It may result in a difference in final aggregation price and rebate.  
         [0176]     Compare that to the buyer with membership B (7 day aggregation period), the membership C entitles the buyer to larger aggregation sold number and a cheaper final aggregation price.  
         [0177]      FIG. 16  shows the exemplary table of implicit style aggregation table for 7 days.  
         [0178]     Date: shows the date time.  
         [0179]     Unit Sold: shows the unit sold within that date.  
         [0180]     Total unit sold (7 days aggregation After Order Date): the sum of sequential 7 days total unit number.  
         [0181]     For example on Oct. 25, 2004 (ref  FIG. 16, 3003 ), total units sold (7 days aggregation after Order Date) equals 91. The result is sum of units sold from Oct. 25, 2004 to Oct. 31, 2004.  
         [0182]     Implicit mode Aggregation sold number: the max aggregation sold number within the 7-day aggregation sold number. For example on Oct. 25, 2004, total sold unit (7 days aggregation after Order Date) is 91, but the Aggregation sold number is the 98, which is the sum of units sold from Oct. 19, 2004 to Oct. 25, 2004.  
         [0183]      FIG. 17  shows the exemplary table of implicit style aggregation table for 15 days, same definition as above except the aggregation period is 15 days.  
         [0184]      FIG. 18  shows the exemplary explicit style aggregation table and conclusion from  FIG. 16  and  FIG. 17 .  
         [0185]     From  FIG. 16 , the max 1 day period unit sold is 23; max 7 day period unit sold is 102.  
         [0186]     From  FIG. 17 , the max 15 day period unit sold is 212 and the total sold within 30 days unit is 334.  
         [0187]     The embodiments and variations shown and described herein are merely illustrative of the principles of this invention. Various modifications may be implemented without departing form the scope and spirit of the invention.