[go: up one dir, main page]

WO2000052556A2 - Procede et dispositif pour le traitement d'offres recurrentes d'acheteurs dans un systeme commercial de collecte des demandes - Google Patents

Procede et dispositif pour le traitement d'offres recurrentes d'acheteurs dans un systeme commercial de collecte des demandes Download PDF

Info

Publication number
WO2000052556A2
WO2000052556A2 PCT/US2000/005741 US0005741W WO0052556A2 WO 2000052556 A2 WO2000052556 A2 WO 2000052556A2 US 0005741 W US0005741 W US 0005741W WO 0052556 A2 WO0052556 A2 WO 0052556A2
Authority
WO
WIPO (PCT)
Prior art keywords
conditional purchase
offer
buyer
stipulation
purchase offer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2000/005741
Other languages
English (en)
Other versions
WO2000052556A3 (fr
Inventor
Jay S. Walker
James A. Jorasch
Daniel E. Tedesco
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Priceline com LLC
Original Assignee
Priceline com LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Priceline com LLC filed Critical Priceline com LLC
Priority to AU38669/00A priority Critical patent/AU3866900A/en
Publication of WO2000052556A2 publication Critical patent/WO2000052556A2/fr
Publication of WO2000052556A3 publication Critical patent/WO2000052556A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Definitions

  • the present invention relates generally to buyer-driven commerce systems, and more particularly to a buyer-driven commerce system that enables a buyer offer to be processed multiple times in accordance with predetermined stipulations.
  • Examples of seller-driven commerce systems include conventional retail systems, both in a traditional store environment, and in an electronic environment as established on the Internet.
  • Amazon.com for example, is representative of a traditional seller-driven commerce system, i.e. a bookstore, that has been implemented electronically on the Internet. It is the applicant's belief that the vast majority of consumer sales are transacted using the seller-driven model.
  • a heretofore less common method of selling products is buyer-driven commerce, where a buyer creates an offer setting the terms and conditions of a potential purchase.
  • the buyer offer is made available to many sellers, for example through a paper or electronic 'want ad,' and interested sellers may contact the buyer to complete the transaction.
  • buyer-driven commerce represents a somewhat newer, lesser used type of commerce having much less supporting infrastructure.
  • electronic networks such as the Internet, and certain business models developed thereunder, applicant's believe no cost-effective infrastructure existed for supporting buyer-driven commerce systems.
  • Facilities for supporting seller-driven commerce include, for example, highly-effective advertising channels, automated payment processing systems, established and readily available fulfillment systems, and other similar facilities for supporting steps of the seller-driven sales process.
  • many of the analogous facilities necessary to support buyer- driven commerce do not exist on the same established, economically feasible and effective scale.
  • Communications and advertising channels through which buyers may reach sellers are not, for example, as well established and effective as are the communications and advertising channels available for sellers to reach buyers.
  • the development of electronic networks, as well as the invention of new commerce models and infrastructures using these networks, have moved towards making the process of buyer-driven commerce more practical and economically feasible on a large-scale basis.
  • Priceline.com Incorporated of Stamford, CT is a merchant that has successfully implemented a buyer-driven commerce system for the sale of products such as airline tickets, hotel accommodations, and automobiles.
  • Priceline.com utilizes a Conditional Purchase Offer (CPO) Management System, described in U.S. Patent No. 5,794,207 and International Application Number PCT/US97/15492. that processes buyer-generated conditional purchase offers (CPOs) received from individual consumers.
  • CPOs contain one or more buyer-defined conditions for the purchase of goods or services, at a buyer-defined price. They may be guaranteed by a general purpose account, such as a debit or credit card account, thereby providing sellers with a mechanism for collecting payments on accepted CPOs.
  • the CPO Management System operates to automatically process CPOs for potential fulfillment by a seller. Automated processing systems developed by priceline.com make the buyer-driven commerce system cost-effective on a large scale. The potential to receive customer offers backed by credit cards, i.e. "guaranteed demand", makes the system very effective for sellers. If a seller accepts a CPO, the CPO Management System may bind the buyer on behalf of the accepting seller, to form a legally binding contract between the parties.
  • the CPO Management System thus empowers individual consumers to obtain goods and services at their own specified prices.
  • the CPO Management System provides numerous commercial advantages to sellers as well. For example, certain features of the system, including anonymity and data security, enable the seller to adjust his price and terms to meet a consumer offer without publicly undercutting his own retail price structure. This enables the seller to identify and accept incremental, price-sensitive sales in a manner not typically feasible through a conventional retail process.
  • CPOs terminate on the occurrence of a predetermined time and/or a single fulfillment.
  • Unfilled CPOs typically expire upon the passage of a predetermined period of time, for example as specified by a buyer, a seller, or a system operator.
  • a successfully filled CPO becomes inactive, according to current practice, upon its first successful fulfillment by a seller.
  • Buy orders are known, for example as used on the stock market, wherein a buyer may place an order to buy a specified quantity of goods within defined limits, for example within a certain price range and/or a certain time period. Buy orders, however, represent a single order for multiple products. They are filled, to the best knowledge of Applicants, as quickly as supply becomes available. They do not permit a buyer to control the recurrence of multiple purchases.
  • Seller-driven commerce tools are known which prompt a buyer to make purchases at the convenience of a seller. Sales offers, promotional events, promotional mailings and the like are examples of tools that sellers use in efforts to motivate buyers to purchase products. Such seller-driven events, however, are not typically within the control of the buyer.
  • a principle object of the present invention is to provide a system and method to facilitate the creation and processing of recurrent Conditional Purchase Offers.
  • a method and system of processing a buyer-driven commercial transaction comprising the steps of: receiving a conditional purchase offer including a buyer-specified condition, an offer price, a payment identifier, and an authorization to pay the offer price with the payment identifier; identifying at least one stipulation for processing the conditional purchase offer on a recurrent basis; and processing the conditional purchase offer on a recurring basis in accordance with the stipulation.
  • a method and system of processing a buyer-driven commercial transaction comprising the steps of: receiving a conditional purchase offer including a buyer-specified condition, an offer price, a payment identifier, and an authorization to pay the offer price with the payment identifier; identifying at least one stipulation provided by the buyer for processing the conditional purchase offer on a recurrent basis including at least one specified time for renewing the conditional purchase offer; processing the conditional purchase offer; terminating the conditional purchase offer; retrieving the at least one stipulation; and if the at least one stipulation is satisfied, renewing the conditional purchase offer at the specified time.
  • a method and system of processing a buyer-driven commercial transaction comprising the steps of: receiving a conditional purchase offer including a buyer-specified condition, an offer price, a credit card account identifier, and an authorization to pay the offer price with the credit card account identifier; identifying at least one stipulation provided by the buyer for processing the conditional purchase offer on a recurrent basis including at least one specified time for renewing the conditional purchase offer with at least one amended condition; making the conditional purchase offer available at a first time to a plurality of sellers to fill; terminating the conditional purchase offer; evaluating the predetermined stipulation; and making the conditional purchase offer available at the specified time to a plurality of sellers to fill, if the predetermined stipulation is met.
  • Fig. 1 is a block diagram of a CPO Management System in accordance with the invention
  • Fig. 2 is a block diagram of the central controller of Fig. 1;
  • Fig. 3 is a table showing the data contents of an exemplary seller database;
  • Fig. 4 is a table showing the data contents of an exemplary buyer database
  • Figs. 5 A-B together show a table showing the data contents of an exemplary recurrent offer database
  • Fig. 6 is a table showing the data contents of an exemplary processed offer database
  • Fig. 7 is a flow chart showing a process for registering a recurrent offer in accordance with the present invention.
  • Fig. 8 is a flow chart showing a process for creating and processing a first CPO of a plurality of recurrent CPOs
  • Fig. 9 is a flow chart showing a process for processing a CPO; and Figs. 1 OA-C together show a flow chart showing a process for processing a recurrent offer in accordance with the present invention.
  • the present invention has application in the field of buyer-driven commerce, used herein to described methods of commerce wherein buyers assemble and submit offers to sellers, the sellers having the opportunity to consider and fill the offer.
  • buyer-driven commerce is the 'want ad,' which may be implemented today both electronically and in paper publications.
  • the present invention is operative to enable the creation and processing of recurrent buyer-driven offers.
  • a buyer may create through a single submission an offer that will be assembled and processed recurrently in accordance with buyer stipulations. These stipulations may control, for example, the timing of recurrent buyer offers.
  • the present invention is shown and described with respect to the creation and processing of buyer offers for airline tickets.
  • a single submission may be used to create a series of recurrent offers for airline tickets on, for example, different dates. It will be understood that the present invention is not limited to offers for airline tickets, but may be practiced to create and process recurrent offers for essentially any goods and/or services.
  • a conditional purchase offer is a buyer offer that contains at least a buyer-specified condition for the purchase of a product, and a buyer-specified price.
  • a conditional purchase order desirably has some financial obligation on the part of the buyer associated with it, for example a penalty for failure to execute on an offer accepted by a seller.
  • a conditional purchase offer may also be binding, wherein a buyer at the time of offer commits to pay his offer price if a seller accepts the offer.
  • Binding CPOs are typically guaranteed with a financial account identifier, for example a credit or debit card account number. The inclusion of a payment guarantee raises the buyer offer, or demand unit, to the level of "guaranteed demand," making the offer less risky and hence more cost-effective for a seller to consider.
  • CPO model Other features that are applicable to the CPO model include the provision of anonymity to a seller, and the provision of flexible terms and conditions in the buyer's CPO.
  • the seller's identity anonymous, at least until the seller accepts an offer, sellers may participate in the system with a much diminished concern about undercutting their own retail structure.
  • the CPO By requiring the CPO to include flexible terms, terms that may be specified by the seller (i.e. delivery date, quality, brand name, etc.), the seller is again given the ability to fill the offer with lessened concern about undercutting their own retail structure.
  • a CPO management system 100 including a central controller 200 for communicating CPOs and CPO-related information with a plurality of buyers 102 A- 102N, and communicating CPO and seller acceptance-related information with a plurality of sellers 106A- 106N.
  • CPOs and related information may be communicated by any appropriate means, for example, through an electronic network, by telephone, or by mail.
  • CPOs may be received directly from a buyer, or through an agent 104 on behalf of a buyer, the agent shown herein as operating with buyer 102 A.
  • central controller 200 is connected to a credit card authorization system 108.
  • Credit card authorization system 108 comprises one of many known commercial business systems that provide the service of authorizing a debit against a consumer credit card account, the account typically identified by an account number embossed on a credit card. Such credit card authorization systems are typically accessed using a telephone connection.
  • credit card authorization system 108 may comprise a system for authorizing a debit against a debit account, or against any other account that may be debited to pay a price. Other suitable payment schemes are discussed in
  • buyers communicate with central controller 200 electronically via the Internet, and the central controller in turn communicates with sellers through an appropriate electronic data interface. Buyers
  • central controller 200 likewise communicate with the central controller 200 through an appropriate computer, for example a personal computer, a server, or a mainframe computer.
  • an appropriate computer for example a personal computer, a server, or a mainframe computer.
  • selected sellers receive CPOs directly from central controller 200, while other sellers provide agency-based rules for use by the central controller to itself evaluate CPOs on behalf of such sellers.
  • central controller 200 is seen to comprise a generally conventional computer, including a central processing unit (CPU) 202 connected to random access memory 204, a read-only memory 206, and a clock 208.
  • CPU 202 is further connected to a communications port 210, such as a modem or a network interface, and a storage device 212.
  • Storage device 212 can comprise, for example, a conventional combination of magnetic, optical, and/or semiconductor memory.
  • storage device 212 is seen to include a seller database 300, a buyer database 400, a recurrent offer database 500, and a processed offer database 600, each of which is described in further detail below.
  • Storage device 212 further includes software instructions for performing a recurrent offer registration process 700 and a recurrent offer evaluation process 800, each of which are also described in further detail below.
  • Central controller 200 further includes those standard hardware and software components necessary to the operation of a computer, as are well known to those of ordinary skill in the art.
  • seller database 300 is seen to include four data records, indicated at 30OA-300D.
  • Each data record includes four data fields: a seller identifier field 302 containing an identifier assigned by central controller 200, a seller name field 304 including an alpha-numeric seller name, a seller contact information field 306 indicating an address or other method of communicating information with a seller, and a seller agent status field 308 indicating whether the seller has provided rules for local evaluation of a CPO by the central controller.
  • Airline 1 is seen to be associated with identifier 1231 and to have an electronic contact address of 'E-ADDRESS#1'.
  • the seller agent status is "no," indicating the seller has not provided rules for local evaluation of CPOs, and is thus to have direct access to CPOs in the manner described below.
  • Airline 2 as identified in data record 300B is seen to have provided CPO evaluation rules, which are available for use at a local database address "DBASE- ADDRESS#2.” Though not shown, an external contact address or information may also be provided for Airline 2.
  • buyer database 400 including three data records 402A, 402B and 402C, each including four fields: a buyer identifier field 404 including an identifier either generated by central controller 200 or provided by a buyer (e.g. a social security number), a financial account identifier field 406 including a financial account identifier such as a credit or debit card number provided by the buyer, a buyer name field 408. and a contact information field 410 including buyer contact information.
  • buyer identifier field 404 including an identifier either generated by central controller 200 or provided by a buyer (e.g. a social security number)
  • a financial account identifier field 406 including a financial account identifier such as a credit or debit card number provided by the buyer
  • buyer name field 408 e.g. a buyer name
  • contact information field 410 including buyer contact information.
  • recurrent offer database 500 is seen to include three data records 502A, 502B, 502C, each including ten data fields: a recurrent CPO identifier field 504 including a system-generated index number for identifying a recurrent CPO, a buyer identifier field 506 including buyer identifier data from field 404 of buyer database 400 for identifying a buyer, a conditions field 508 including buyer-supplied CPO conditions, and a timing field 510 including buyer-specified quantities and periodicity of purchase conditions for the CPO.
  • a recurrent CPO identifier field 504 including a system-generated index number for identifying a recurrent CPO
  • buyer identifier field 506 including buyer identifier data from field 404 of buyer database 400 for identifying a buyer
  • a conditions field 508 including buyer-supplied CPO conditions
  • a timing field 510 including buyer-specified quantities and periodicity of purchase conditions for the CPO.
  • a price-per-unit field 512 including a buyer-specified offer price for each unit purchase, a total number of authorized purchases field 514 including the total number of purchases authorized by the buyer for a given CPO, a total number of purchases consummated to date field 516 calculated by the system as CPOs are fulfilled, a submission date/time field 518 supplied by the system when the CPO is received into the system, an expiration date/time field 520 containing an expiration date and optionally an expiration time supplied by the buyer and/or the system, and a status field 522 generated by the system indicating the status of the CPO. Status types and meanings are set out in Table 1 below.
  • the combination of information available from fields 510 and 514 are used together to determine if and when a recurrent CPO is to be generated, and is referred to herein as the buyer recurrence "stipulations.”
  • the CPO conditions and recurrence stipulations for each of the illustrated data records are set out and evaluated in Table 2 below.
  • non-recurrent CPOs may be identified and stored for processing in database 500, and/or in a separate database.
  • Recurrent CPOs may be identified as distinct from non-recurrent CPOs by, for example, the format of the CPO identifier.
  • processed offer database 600 is seen to include three data records 602A, 602B, 602C, each including eight data fields: a CPO identifier field 604 generated by the system each time a CPO is processed, a recurrent CPO identifier field 608 containing the recurrent CPO identifier data from field 504 of database 500 when the CPO is a recurrent CPO, a buyer identifier field
  • a price-per-purchased-product unit field 614 including the CPO offer price (for recurrent CPOs, copied from field 512 of database 500), a posting date field 616 provided by the system and identifying the date the CPO was made available to buyers, an expiration date field
  • a status field 620 containing the status of the CPO.
  • the different available statuses are described in Table 3 below.
  • CPO Identifier "019827038” is seen to identify a recurrent CPO "C92724" submitted by buyer " 1234" for a round-trip ticket from NY to LA, leaving on a Friday and returning on a Sunday.
  • the particular posting date for this recurrent CPO is 1 October 1998 and it would have expired on 8 October 1998.
  • the accepted status indicates the CPO was filled by a seller.
  • recurrent CPO "C92724" will result in multiple CPOs such as this one, during different dates, in accordance with the buyer recurrence stipulations as set out in database 500 and discussed above.
  • the CPO identified in data record 602A was generated in accordance with the buyer conditions and recurrence stipulations during the week of 4-9 October 1998.
  • data record 602B is seen to identify CPO data for a non-recurrent, expired CPO.
  • Data record 602C is seen to include CPO data for recurrent CPO "C29176", in accordance with the buyer conditions and recurrence stipulations set out in database 500, and is seen to be active and available for a seller to fill.
  • a process 700 for receiving for processing, i.e. registering, recurrent CPOs is shown, the first step including receiving the recurrent CPO data from a buyer 102 into system 200 through communications port 210 (step 702).
  • a recurrent CPO includes buyer conditions and recurrence stipulations within the CPO data that define the creation and processing of recurrent CPOs based on the single recurrent CPO submission.
  • Buyer data is read from the recurrent CPO, including a buyer name, contact information, and a financial account identifier, and this buyer information is indexed with a buyer identifier in buyer database 400 (step 704).
  • a recurrent CPO data record is created and the data is populated in recurrent CPO database 500 (step 706).
  • Such data consists of that shown and described with respect to Fig. 5 above, including the buyer conditions and recurrence stipulations necessary to identify and process recurrent CPOs.
  • available buyer credit based on the buyer financial account information may be verified (step 708) as between central controller 200 and credit card authorization system 108 (Fig. 1) in accordance with one of many such processes known in the art.
  • the data in recurrent CPO database 500 is queried to identify buyer condition data (from field 508 of database 500) and the buyer recurrence stipulations (from fields 510 and 514) (step 710), and subsequently processed to generate the initial CPO (step 712).
  • the process 800 of generating a first CPO is initiated by processing buyer conditions to determine a product type (step 802). For purposes of illustration, these steps will be considered in view of the recurrent CPO data record 502A of Fig. 5.
  • the conditions in field 508 are thus seen to identify a round-trip airline ticket from New York to Los Angeles, leaving on a Friday and returning on a Sunday.
  • the buyer stipulations in data fields 510 and 514 are used to determine a first CPO active period.
  • the illustrated recurrent CPO is seen to authorize purchases of one ticket per week, up to five tickets during the period of 01 October 1998 through 01 May 1999. It will thus be seen that the first CPO of the recurrent CPOs is to be posted for the remainder of the week, from the date of receipt, which would enable a first ticket to be purchased by the first Friday following the recurrent CPO submission date. Because the submission date is a Thursday evening, the first CPO may be posted for that Thursday evening, 01 October 1998, specifying a ticket for a flight departing on Friday, 02 October 1998, and returning on Sunday, 04 October
  • the per-ticket offer price is retrieved from field 512 of database 500 (step 806), and the initial CPO is generated and stored in database 600 (step 808).
  • the initial CPO for recurrent CPO "C92724" is seen to have been stored in record 602A.
  • the CPO described in record 602A thus shows an active period of 01 October 1998 (i.e. the submission date) through 08 October 1998 (the following Thursday) for the purchase of a round-trip ticket on that Friday (10/15/98), returning that Sunday (10/11/98).
  • the offer price is three hundred dollars.
  • the status in field 620 indicates that the offer has been accepted (and would no longer be active).
  • a process is shown for processing CPOs, including both recurrent and non-recurrent CPOs.
  • a process is shown for processing CPOs, including both recurrent and non-recurrent CPOs.
  • CPO is identified for processing (step 902). That CPO is made available to remote sellers (also termed 'broadcast-based' sellers) (step 904) and compared to rules provided by rules-based sellers (also termed 'agency-based' sellers) (step 906).
  • the step of making such an offer available to remote sellers may include, for example, transmitting the offer to the remote sellers electronically or by paper, and/or making the offer available for viewing by remote sellers, such as on an Internet website.
  • the step of comparing such an offer to rules includes comparing the terms of the offer to rules of acceptance provided by a seller(s) for local processing and acceptance. Such rules, for example, may be collected and stored in a database in central controller
  • step 908 It is next determined if any seller accepts the CPO (step 908). If neither of steps 904 or 906 identify an accepting seller, then the buyer is notified with a rejection of the offer (step 910). If an acceptance by a seller is identified in step 908, then the accepting seller is identified (step 912) and provided with the necessary buyer data (step 914). The buyer is likewise notified (step 916) of the acceptance, and provided necessary information relating to the seller.
  • a recurrent offer evaluation process 1000 is shown for identifying and assembling recurrent offers for processing in accordance with Fig. 9 above. This process may be performed cyclically on a periodic basis, for example once per minute, or continuously on an ongoing basis.
  • the data in recurrent CPO identifier field 608 of processed CPO database 600 is accessed to identify recurrent offers (step 1002). If no recurrent offers exist in the database (step 1004), the process cycles back to perform the first step 1002 at the beginning of the next process cycle.
  • recurrent CPOs are identified in database 600 (step 1004), the status and the expiration dates, in fields 522 and 520, respectively, are examined to determine if any recurrent CPO is newly expired or newly accepted (step 1006). Newly expired CPOs will have a status of active and an expiration date of post the last cycle of the current process.
  • One method to determine if a CPO is newly accepted is for the system to store the previous status conditions from the last process cycle, and compare them to the current status conditions in the most recent process cycle. If a newly accepted CPO is identified, the total purchases consummated field 516 of database 500 is incremented for the corresponding CPO data record (step 1008).
  • the total purchases consummated is then compared to the total purchases authorized (field 514 of database 500) (step 1010). If they are equal, then the corresponding status in field 522 of database 500 is set to terminated (step 1012), and the process ends. If the total purchases consummated is less than the total purchases authorized, then the buyer stipulations are retrieved from fields 510 and 514 (step 1014), and it is determined if the CPO has expired (step 1015). A CPO has expired if the expiration date in field 518 is equal to or earlier than the current date. If the CPO is expired, then the status is set to "terminated" (step 1012) and the process ends.
  • the active period for the next recurrent CPO is calculated (step 1016).
  • the next active period will be that which enables the purchase of a single round-trip ticket having the conditions specified: i.e. NY-LA, leave Friday, return Sunday.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un système et un procédé facilitant la création et le traitement d'offres d'achat récurrentes assorties de conditions. L'offre est reçue, avec les conditions spécifiées par l'acheteur, un prix d'offre, un identificateur de paiement, et une autorisation de paiement du prix d'offre via l'identificateur de paiement. Au moins une stipulation est identifiée pour le traitement de l'offre sur une base récurrente. L'offre est traitée sur cette base conformément à la stipulation.
PCT/US2000/005741 1999-03-03 2000-03-03 Procede et dispositif pour le traitement d'offres recurrentes d'acheteurs dans un systeme commercial de collecte des demandes Ceased WO2000052556A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU38669/00A AU3866900A (en) 1999-03-03 2000-03-03 Method and apparatus for processing recurring buyer offers in a demand collection commerce system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US26132299A 1999-03-03 1999-03-03
US09/261,322 1999-03-03

Publications (2)

Publication Number Publication Date
WO2000052556A2 true WO2000052556A2 (fr) 2000-09-08
WO2000052556A3 WO2000052556A3 (fr) 2001-03-29

Family

ID=22992794

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/005741 Ceased WO2000052556A2 (fr) 1999-03-03 2000-03-03 Procede et dispositif pour le traitement d'offres recurrentes d'acheteurs dans un systeme commercial de collecte des demandes

Country Status (2)

Country Link
AU (1) AU3866900A (fr)
WO (1) WO2000052556A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017021986A1 (fr) * 2015-08-06 2017-02-09 Ettari Giacomo Procédé d'offre d'achat conditionnée et système

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5794207A (en) * 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5950173A (en) * 1996-10-25 1999-09-07 Ipf, Inc. System and method for delivering consumer product related information to consumers within retail environments using internet-based information servers and sales agents
US5794212A (en) * 1996-04-10 1998-08-11 Dominion Resources, Inc. System and method for providing more efficient communications between energy suppliers, energy purchasers and transportation providers as necessary for an efficient and non-discriminatory energy market
US5729594A (en) * 1996-06-07 1998-03-17 Klingman; Edwin E. On-line secured financial transaction system through electronic media
US5950172A (en) * 1996-06-07 1999-09-07 Klingman; Edwin E. Secured electronic rating system
US5862223A (en) * 1996-07-24 1999-01-19 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce
JPH1153184A (ja) * 1997-08-08 1999-02-26 Seta:Kk データ配信方法および装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017021986A1 (fr) * 2015-08-06 2017-02-09 Ettari Giacomo Procédé d'offre d'achat conditionnée et système

Also Published As

Publication number Publication date
WO2000052556A3 (fr) 2001-03-29
AU3866900A (en) 2000-09-21

Similar Documents

Publication Publication Date Title
US6510418B1 (en) Method and apparatus for detecting and deterring the submission of similar offers in a commerce system
US8630896B2 (en) Systems and methods wherein a security deposit facilitates a transaction in which a benefit is applied in exchange for performance of a task
US5710887A (en) Computer system and method for electronic commerce
US6947906B1 (en) Method for conducting a computerized government auction
US20020178069A1 (en) Dynamic quality control conditional purchase offer (cpo) management system
US20110137751A1 (en) Computerized system for facilitating transactions between parties on the internet using e-mail
US20030041014A1 (en) System and method for conducting a sell side auction
US20030041011A1 (en) System and method for conducting a buy-side auction
US20030158782A1 (en) Electronic processing system
WO2000033164A2 (fr) Systeme et procede pour encourager la soumission d'offres d'achat conditionnelles
US9922368B2 (en) System and method for purchasing a prepaid debit account
JP2002041842A (ja) 商品売買のための電子的仲介サービスおよび価格決定
AU2001256518A1 (en) Electronic processing system
WO2007025287A2 (fr) Procede et systeme de fixation de prix optimal
US20040034596A1 (en) Electronic payment management
AU2010273172B2 (en) A method and system for providing a service associated with sale of a product
WO2000052556A2 (fr) Procede et dispositif pour le traitement d'offres recurrentes d'acheteurs dans un systeme commercial de collecte des demandes
KR100422157B1 (ko) 컴퓨터 통신망을 이용한 공동 구매 시스템 및 그 운영 방법
US20250022046A1 (en) Auction system and method
CA2489132A1 (fr) Mise aux encheres inversee par ordinateur
CA2199942C (fr) Systeme de paiement informatise pour l'achat de produits d'information par transfert electronique sur internet
CA2592534C (fr) Systeme de paiement informatise pour l'achat de produits d'information par transfert electronique sur internet
KR20030084863A (ko) 전자상거래시스템 및 그 방법
KR20020004039A (ko) 컴퓨터 통신망을 이용한 경매시스템의 구매신청 처리방법및 장치

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase