WO2001020516A9

WO2001020516A9 - Tracking system for customer electronic purchase requests and purchases

Info

Publication number: WO2001020516A9
Application number: PCT/US2000/024857
Authority: WO
Inventors: Tim Walker; Jared Rowe; Jeffrey L Waters; Michelle L Carrillo; Kevin J Wagoner
Original assignee: Autobytel Com Inc
Priority date: 1999-09-16
Filing date: 2000-09-11
Publication date: 2002-09-26
Also published as: AU7367700A; WO2001020516A2; WO2001020516A8

Description

TRACKING SYSTEM FOR CUSTOMER ELECTRONIC PURCHASE REQUESTS AND PURCHASES

Background Field The present invention is related to systems and methods for conducting business transactions. More particularly, this invention relates to a system for collecting consumer data. Description of the Related Art

Modern businesses can employ information regarding consumer purchasing tendencies to modify product designs and make decisions regarding new products. Generally, especially with higher cost items, a customer's vision of a product that the customer would like to purchase is substantially different from the actual product that is eventually purchased by the customer. The product may differ in its eventual price, or the product may differ in its eventual configuration. Therefore, there is a transition from an initial interest in a particular product to the actual product that is purchased by a buyer. Such information may be valuable to a manufacturer in making decisions regarding product designs. In the vehicle dealership setting, a customer may enter a dealership with a preconceived notion of what the customer desires. The customer's desires may be memorialized by a salesperson. During the purchasing process, the customer is likely to alter or modify his or her desires. These modifications are likely to be memorialized by the salesperson while the prior information is discarded.

Summary In accordance with the present invention, a system is provided which allows for generating statistical models and other data models of consumer purchasing behavior. The system of the present invention relates to a method of selling items by receiving purchase requests for such items by a communication link such as an electronic communication link. The seller receives a purchase request and eventually a purchase transaction takes place. The terms of the purchase transaction are generally different from the terms of the purchase request. The transmitted purchase request is saved in a separate storage location from the storage location of the purchase transaction record.

The purchase transaction record is then compared to the stored transmitted purchase request to determine the changes which were initiated by the customer with regards to the particular transaction. Such changes are then analyzed by a statistical analysis module to determine customer tendencies in the aggregate for purchase requests and eventual purchase transactions for a particular dealer, for a particular item, or for a particular industry.

Brief Description of the Drawings These and other aspects, advantages, and novel features of the invention will become apparent upon reading the following detailed description and upon reference to accompanying drawings in which:

Figure 1 is a system block diagram illustrating an embodiment of the overall network architecture of the invention; Figure 2 is a representation of one embodiment of an exclusive dealer regions record of the invention;

Figure 3 is a representation of one embodiment of a dealer record of the invention;

Figure 4 is a representation of one embodiment of a new vehicle record of the invention;

Figure 5 is a representation of one embodiment of a used vehicle record of the invention; Figure 6 is a high level block diagram illustrating one embodiment of a Data Center server system architecture of the invention;

Figure 7 is a representation of one embodiment of a new vehicle purchase request record of the invention;

Figure 8 is a representation of one embodiment of a used vehicle purchase request record of the invention;

Figure 9 is a block diagram illustrating one embodiment of a communication between a buyer, a seller, and components of a Data Center system;

Figure 10 is a representation of one embodiment of a dealer record showing the contents of the record fields;

Figure 11 is a representation of one embodiment of a dealer record showing certain of the fields implemented as pointers;

Figure 12A is a high level block diagram illustrating one embodiment of the selected components contained in the dealer access module;

Figure 12B is a representation of one embodiment of a user record of the invention;

Figure 13A illustrates an HTML page of a manage-customers module; Figure 13B illustrates a transaction worksheet of a purchase request summary module;

Figure 13C illustrates the an HTML page of the manage-customers module when the seller selects a "Stock Number" link;

Figure 14A illustrates the manage-customers module when a status change module is displayed;

Figure 14B illustrates the status change module when the scroll bar is moved down;

Figure 14C illustrates the status change module 1406 when the scroll bar is moved to the bottom of the scrollable area; Figure 15 illustrates a vehicle options detail module;

Figure 16A illustrates a modify options module;

Figure 16B illustrates a lower portion of the modify options module of Figure 16 A;

Figure 16C illustrates a lower portion of the modify option module of Figure 16A;

Figure 16D illustrates the bottom portion of the modify option module; Figure 17A illustrates a purchase request customer module;

Figure 17B illustrates the purchase request customer module when the scrollbar is moved down;

Figure 17C illustrates the purchase request customer module when the scrollbar is moved to the bottom of the scrollable area;

Figure 18A illustrates a purchase request vehicle module; Figure 18B illustrates the purchase request vehicle module when the scrollbar is moved to the bottom of the scrollable area;

Figure 18C illustrates an HTML page of the customer management module when the seller selects a "Standard" link from in the purchase request vehicle module;

Figure 18D illustrates the popup purchase request vehicle standard features screen when the scrollbar of the screen is moved to the bottom;

Figure 19A illustrates a purchase request detail module which is displayed in response to a selection of the "modify existing car" option from the modify vehicle selection box of Figure 18A;

Figure 19B illustrates the bottom portion of the purchase request detail module of Figure 19A; Figure 19C illustrates a color selection box of the purchase request detail form; Figure 20A illustrates a new vehicle selection form;

Figure 20B illustrates a new vehicle model selection box of the new vehicle selection form; Figure 20C illustrates a new vehicle series selection box of the new vehicle selection form; Figure 21 A illustrates a used vehicle selection form;

Figure 21 B illustrates a used vehicle model selection box of the new vehicle selection form; Figure 21 C illustrates a used vehicle series selection box of the new vehicle selection form;

Figure 21 D illustrates a used vehicle purchase request detail form; Figure 22 illustrates a purchase request trade-in form; Figure 23 illustrates a finance information form; Figure 24 illustrates a rewards information form; Figure 25A illustrates an appointment list form;

Figure 25B illustrates an appointment list form when an appointment edit section is displayed; Figure 26A illustrates the purchase request new customer module;

Figure 26B illustrates the purchase request new customer module when the scrollbar to the right of the module has been moved down; Figure 27 illustrates a new/used car selection box;

Figure 28 illustrates the logical progression of the forms of the manage-customers module; and Figure 29 illustrates the arrangement of a customer purchase request tracking system. Throughout the drawings, components which correspond to components shown in previous figures are indicated using the same reference numbers. Detailed Description

In one embodiment of the invention, a computerized purchase request management system is provided which facilitates efficient management and processing of purchase requests while allowing sellers to create new purchase requests. The system includes a plurality of HTML pages accessible over a network. A potential buyer accesses a first

HTML web page over a network such as the World Wide Web (www) using a standard web browser. A participating seller accesses a second HTML page over a network by advantageously utilizing a standard web browser. The system further comprises a web server and other program modules which allow both buyer and seller direct and immediate access into a system database. The seller is advantageously provided with the ability to modify buyer's selections in the purchase request.

As used herein, "immediately" is understood to mean occurring without loss or interval of time other than the nominal delay necessarily caused by computing components such as microprocessors, memory devices, software and firmware program execution times, and the like.

A participating seller is a seller of goods which has entered into an agreement to participate in the computerized purchase request management system of the invention. The seller is identified by a unique seller record stored in the system database. The seller is further assigned an exclusive database region in the system database. The seller directly accesses its exclusive database region over the network utilizing the system's HTML pages.

A potential buyer uses the system's HTML web pages to formulate and submit a purchase request into the system. The purchase request is communicated to an appropriate participating seller upon the system storing a purchase request record into the seller's exclusive database region. The participating seller is initially assigned a group account in the Data Center system. The seller is given a unique login identification and a password to access the group account. A person associated with the seller logs onto the system utilizing one of the plurality of HTML pages comprising the system and providing the login identification and password. Each user created within the seller group is associated with a user profile which filters the information contained in the exclusive database region such that it is efficiently displayed to the user.

All users in a seller group use the same login identification and password to initially log on to the Data Center system. Having logged on, a user identifies himself or herself to the system by selecting his or her user identification from a displayed list.

Having successfully logged onto the system, the seller is able to access the information stored in its exclusive database region. The plurality of HTML pages comprising the system provide direct access into the exclusive database region. The direct access enables the seller to be notified of newly created purchase requests along with any other seller information stored in its exclusive database region. The notification and direct database access enables the seller to efficiently manage its purchase requests.

The seller may use the private seller system to create a purchase request. The purchase request is created by interacting with HTML pages similar to those used by buyers to create purchase requests. The purchase request generated by the seller is stored in the seller's exclusive database region. The seller may then manage the purchase request in the same manner as other purchase requests that are created by buyer.

The seller may manage purchase requests by editing information in the purchase request or assigning tasks to purchase requests. Such tasks include making the initial buyer contact, and calling the potential buyer to provide a haggle- free price quote. The tasks may be assigned to any of the users in the seller group. The tasks may be stored as part of the purchase request record. A summary of each assigned task is preferably displayed along with the purchase request. Furthermore, an HTML page may advantageously inform a user of its assigned tasks. Even though the invention is suitable for providing a uniform purchase request for any product, the purchase request invention will be further disclosed in the context of providing a uniform purchase request for a vehicle.

In one embodiment of the invention, a Data Center system utilizes a database to store dealer information, buyer information, and program logic, for example, to associate the potential buyer to a specific dealer. Additionally, the Data Center system may advantageously include program logic facilitating access between the Data Center system and sources external to the Data Center system over a computer network.

Computer networks suitable for use with the present invention include local area networks (LAN), wide area networks (WAN), Internet, or other connection services and network variations such as the world wide web, the public internet, a private internet, a private computer network, a secure internet, a private network, a public network, a value- added network, and the like. The computers connected to the network may be any microprocessor controlled device that permits access to the network, including terminal devices, such as personal computers, workstations, servers, mini computers, main-frame computers, laptop computers, mobile computers, palm top computers, hand held computers, set top box for a TV, or a combination thereof. The computers may further possess input devices such as a keyboard or a mouse, and output devices such as a computer screen or a speaker. The computer network may include one or more LANs, WANs, Internets, and computers. The computers may serve as servers, clients, or a combination thereof.

One network architecture which may be used with one embodiment of the invention is illustrated by a system 10 in Figure 1. The system 10 includes a network 102, which represents a computer network as previously described, providing access to the Data Center system.

In one embodiment of the invention, the Data Center programs and Data Center databases, comprising the Data Center system, preferably reside on one or more Data Center servers 104 and one or more Data Center storage mediums

106. The Data Center servers 104 and Data Center storage mediums 106 may be interconnected by a LAN 108 and a gateway 110 to the network 102. The gateway 110 facilitates access to the Data Center system from the network 102.

One example of the LAN 108 is a corporate computing network, which may provide access to the Internet, to which computers and computing devices comprising the Data Center system are connected. In one embodiment, the LAN 108 conforms to the Transmission Control Protocol/Internet Protocol (TCP/IP) industry standard. In alternative embodiments, the LAN 108 may conform to other network standards, including the International Standards Organization's

Open Systems Interconnection, IBM's SNA , Novell's Netware , and Banyon VINES .

Those of ordinary skill in the art will recognize that the Data Center programs, the Data Center databases, and gateway functionality may advantageously be implemented on one or more computers. The computers may include a single or multiple processors. Additionally, the computers include an addressable storage medium such as random access memory and a non-volatile storage medium such as a magnetic or an optical disk.

In accordance with one embodiment of the invention, the Data Center server 104 is connected to the Internet and utilizes at least a first user web page remotely accessible by a potential buyer. The user web page permits the potential buyer to enter the necessary buyer and product information into the Data Center system. In another embodiment, the Data Center server 104 utilizes a second HTML page accessible by an authorized dealer. The authorized dealer utilizes the web page to access the Data Center system and employ features as further detailed herein. Those of ordinary skill in the art recognize that a single web page may be used to provide both buyer and dealer access to the Data Center system. Further, access for a buyer could be through an entirely different network than that used for access by the dealer. In one embodiment, the Data Center storage medium 106 may be configured as a database which can store, update, and retrieve information. For example, the database may conform to the Structured Query Language (SQL) standard. In an alternative embodiment, the database may conform to any database standard, or to a non-standard, private, specification. The Data Center programs may provide access to the information stored on the Data Center storage medium 106. The Data Center storage medium 106 may be accessed by devices such as clients, servers, workstations, personal computers, and the like, connected to the network 102, or to the LAN 108.

In one embodiment, the Data Center storage medium 106 comprises exclusive database regions. The Data Center assigns each participating dealer an exclusive database region. In another embodiment, the exclusive database regions may be created by segmenting the storage media into distinct areas, with each area assigned to a dealer. These areas or regions could be dynamically allocated by the computer depending on the amount of data to be stored as the data is entered. In another embodiment, the collection of information associated with a dealer advantageously comprises the exclusive database region for the dealer. The exclusive database region is preferably only accessed by the assigned dealer and the Data Center system programs.

In another embodiment, the Data Center programs transfer the information stored on the Data Center storage medium 106 to sources external to the Data Center system. For example, vehicle inventory information is advantageously transferred to third-party computers connected to the network 102. A potential buyer may then access the third-party computer to view vehicle data. In yet another embodiment, the potential buyer may submit a vehicle purchase request from the third-party computer.

Various other devices may be connected to the LAN 108. For example, a workstation 112 and a personal computer 114 is connected to the LAN 108 to provide access to the Data Center programs and Data Center databases. In one embodiment, a printer 117 is connected to the LAN 108 to provide local and remote printing capabilities.

The network 102 may connect devices, such as a user computer 116 or a user laptop 118, for example, by use of a modem or by use of a network interface card. As illustrated, potential buyers, utilize such devices to remotely access the Data Center system via the network 102. The device used to provide access to the Data Center server is referred to herein as a buyer terminal. Buyer terminals include any device useful for providing access to the Data Center. The Data Center stores the purchase request in a dealer's database region.

A plurality of dealer computers 120 are preferably connected to the network 102 through a modem or other network connection device. A vehicle dealer may advantageously use the dealer computer 120 to remotely access the Data Center system. The device used to provide access to the Data Center server may be referred to herein as a dealer terminal. Dealer terminals include any device useful for providing access to the Data Center. Dealers access the Data Center by logging in through the second HTML page of the Data Center server 104. Upon logging in, the dealer attains direct access to its exclusive database region and the contents thereof. Moreover, because a purchase request is immediately stored upon its creation, or soon thereafter, in a dealer's database region, the dealer is immediately made aware of newly created purchase request.

Although particular computer systems and network components are shown, those of ordinary skill in the art will appreciate that the present invention is applicable to a variety of other networks and components.

Figure 2 illustrates an example of a record of exclusive dealer regions suitable for use with one embodiment of the invention. Advantageously, the record of exclusive dealer regions may be implemented as a two dimensional data matrix. The data matrix may be stored in the Data Center storage medium 106. Zip codes for all the regions correspond to a first index of the data matrix. All the available vehicle makes correspond to a second index of the data matrix. Each matrix cell 202 may contain a dealer identification number uniquely identifying a dealer. In this manner, each region, and each vehicle make for that region, may be assigned to a unique dealer. In an alternative embodiment, each matrix cell 202 may contain one or a plurality of dealer identification numbers.

Figure 3 illustrates an example of a dealer record according to one embodiment of the invention. Each dealer member of the Data Center system is assigned a dealer record. The dealer record is stored in the dealer's exclusive database region in the Data Center storage medium 106. By way of example, six fields are illustrated comprising the dealer identification number 302, dealer information 304, access list 306, product list 308, new vehicle purchase requests 310, and used vehicle purchase requests 312. One of ordinary skill in the art may appreciate that any of the fields of the dealer record of Figure 3 may be broken down into additional sub-fields, or that additional fields could be added.

In one embodiment, the dealer information 302 may be comprised of additional fields such as, for example, a dealer name, dealer address, dealer group, and the like. Figure 10 generally illustrates an example of a dealer record showing the contents of the record fields suitable for use with one embodiment of the invention. Furthermore, any of the dealer record fields may be implemented as pointers to other fields or other data records. For example, the product list may point to a list of new vehicle model records indicating the new vehicle models offered for sale by the dealer. Figure 11 generally illustrates an example of a dealer record depicting certain of the fields implemented as pointers. In one embodiment, each new vehicle model record may in turn point to a list of aftermarket product records.

The aftermarket product records identify additional products offered for sale, by the dealer, for the specific new vehicle model. The aftermarket product record may be comprised of the name of an aftermarket product, a retail price for the product, a discounted price for the product, and possibly a photo showing the product.

In yet another embodiment, each new vehicle model record may further point to a vehicle model specifics record and a vehicle model accessories record. The vehicle model specifics record may identify the vehicle model specifics such as available transmission type, available number of doors, and the like. The vehicle model accessories record may identify the accessories such as leather seats, power windows, and the like, available for the vehicle model. In an alternative embodiment, the vehicle model specifics record contents and the vehicle model accessories record contents may be appropriately displayed in a web page. The buyer may then specify the desired vehicle specifics and the desired vehicle accessories. In one embodiment, a new vehicle database may be comprised of a list of new vehicle records which may be stored in the Data Center storage medium 106. Each new vehicle model available for purchase through the Data Center system is associated with a new vehicle record. Figure 4 illustrates a new vehicle record suitable for use with the invention. By way of example, seven fields are illustrated comprising a vehicle make 402, vehicle model 404, vehicle year 406, vehicle type 408, vehicle estimated price 410, vehicle features 412, and vehicle photo 414. It should be understood that appropriate fields may be added and a field may contain additional sub-fields. For example, the vehicle features field 412 may advantageously be comprised of a standard features field and an optional features field. In one embodiment, the vehicle type field 408 may indicate whether the vehicle is a passenger car, a luxury car, a sports car, or the like.

In another embodiment, the new vehicle record fields may be implemented as pointers to other fields or other records. For example, the vehicle photo field 414 may be implemented as a pointer pointing to a representative photo of the new vehicle. Thus, the representative photo may advantageously be stored in a different region in the Data Center storage medium 106. In yet another embodiment, the vehicle year field 406 may be implemented as a pointer pointing to one or a plurality of records, each record containing, for example, a year field, a type field, an estimated price field, a features field, a photo field, and the like. A used vehicle record identifies a used vehicle, and is created for each used vehicle offered for sale through the

Data Center system. The collection of used vehicle records comprise a used vehicle inventory. The used vehicle records may be stored in the Data Center storage medium 106. For example, the used vehicle inventory may be implemented as a linked list of used vehicle records.

Figure 5 illustrates an example of a used vehicle record suitable for use with one embodiment of the invention. By way of example, six fields are illustrated comprising the dealer identification number 302, a dealer stock number 502, vehicle make 504, vehicle model 506, vehicle information 508, and vehicle photo 510. One of ordinary skill in the art will realize that appropriate fields may be added and any number of the fields may be broken down into additional sub-fields. Furthermore, any of the fields may be implemented as pointers to other fields or other data records. For example, the vehicle photo field 510 may advantageously point to an image of the vehicle stored elsewhere in the Data Center database. Figure 6 illustrates in more detail selected components of the Data Center server 104 of Figure 1 suitable to implement one embodiment of the present invention. The Data Center server 104 includes a buyer access module 602 connected along a virtual communications path 606 to a process purchase request module 604. Also connected to the virtual communications path 606 is a database access module 608, a buyer-dealer association module 610, a dealer access module 612, and a network access module 614. The buyer access module 602 provides a buyer with an interface into the Data Center system. In one embodiment, a purchase request entry system comprises the buyer access module 602 and facilitates the data entry for a purchase request for a vehicle. The buyer access module 602 may be comprised of a "generate new vehicle purchase request" module 616 and "a generate used vehicle purchase request" module 618. The "generate new vehicle purchase request" module 616 and the "generate used vehicle purchase request" module 618 are advantageously implemented as a plurality of web pages. In one embodiment, the web pages are advantageously implemented in hypertext or hypermedia. Thus, the web pages may contain selectable items or links. The links may provide access to other web pages contained in the Data Center system. The plurality of linked web pages guides the user in entering the necessary data to create and submit either a new vehicle purchase request or a used vehicle purchase request. In another embodiment, the links may provide access to any location in the World Wide Web. For example, a link may exist to third-party web sites which advantageously provide additional product information.

The generate new vehicle purchase request module 616 facilitates a new vehicle purchase request creation and submission process. A potential buyer remotely utilizes, over a network such as the World Wide Web, at least a first web page in the "generate new vehicle purchase request" module 616 and provides information from which the process purchase request module 604 creates a new vehicle purchase request. Likewise, the "generate used vehicle purchase request" module 618 facilitates a used vehicle purchase request creation and submission process through its web pages. There may be a one-to-one correlation between a purchase request and a purchase request record.

In one embodiment, a processing system comprises the process purchase request module 604 and may facilitate the creation of a purchase request record. The process purchase request module 604 may create either a new vehicle purchase request record or a used vehicle purchase request record. The new vehicle purchase request record may be created from the information supplied through the plurality of web pages utilized during the new vehicle purchase request creation and submission process. In one embodiment, the buyer information gathered through the plurality of web pages comprising the "generate new vehicle purchase request" module 616 is provided as input to the "process purchase request" module 604. The "process purchase request" module 604 creates a new vehicle purchase request record from the input information. The used vehicle purchase request record may likewise be created from the information supplied through the plurality of web pages utilized during the used vehicle purchase request creation and submission process. In another embodiment, the purchase request information may also be obtained from web pages external to the Data Center system.

Figure 7 illustrates a set of information fields comprising a new vehicle purchase request record according to one embodiment of the invention. By way of example, fifteen fields are illustrated comprising new vehicle purchase request identification number 702, submit time stamp 704, dealer identification number 706, vehicle make 708, vehicle model 710, vehicle model year 712, purchase time frame 714, vehicle specifics 716, requested accessories 718, requested aftermarket products 720, buyer information 722, privacy 724, payment information 726, priority 728, and status 730. It should be understood that some of these fields include several sub-fields. Thus, for example, the buyer information field may include sub-fields for name, address, zip code, e-mail address, phone numbers, and contact preference. The new vehicle purchase request record may advantageously be stored in the Data Center storage medium 106.

In one embodiment, the information fields may be implemented as pointers to other fields or other records containing the information. For example, the buyer information may be implemented as a pointer. The pointer may point to a record comprised of, for example, the name, address, zip code, e-mail address, phone numbers, and contact preference. Those of ordinary skill in the art will realize that any combination of the information fields may be implemented as pointers. In another embodiment, certain information fields may be implemented as encoded fields. For example, the requested accessories field may be implemented as a binary encoded field. Each bit position may coincide with a vehicle accessory such as an AM/FM radio, power windows, tilt wheel, overhead console, and the like. For example, a "1 " in the first bit position may indicate the selection of an AM/FM Radio accessory. Figure 8 illustrates a used vehicle purchase request record suitable for use with one embodiment of the invention.

Thirteen fields are illustrated comprising used vehicle purchase request identification number 802, submit time stamp 804, dealer identification number 806, dealer stock number 808, vehicle make 810, vehicle model 812, vehicle model year 814, purchase time frame 816, buyer information 818, payment information 820, priority 822, privacy 824, and status 826. One of ordinary skill in the art will realize that any number of the fields may be broken down into additional sub-fields. Furthermore, similar to the new vehicle purchase request record, any of the fields may be implemented as pointers, encoded fields, and the like. The used vehicle purchase request record may advantageously be stored in the Data Center storage medium 106.

In one embodiment, purchase request records generated by both buyers and sellers are of the formats illustrated in Figure 7 and Figure 8. The purchase request records are managed by a single interface. The seller may wish to run a search for particular purchase requests. The search may be for purchase requests with a status 730 of "new." Because all purchase requests include a status field 730, the data in the field can be compared to the search criteria (i.e. "new"). If the purchase requests generated by the sellers are of a different format from the purchase requests generated by the buyers, some fields may be unique to purchase requests from a particular source. When purchase requests are not of the same format, certain fields cannot be searched. Thus, providing uniform purchase requests allows for more efficient searching of purchase requests.

In one embodiment, the "process purchase request" module 604 (Figure 6) associates the information entered by the buyer through either the "generate new vehicle purchase request" module 616 or the "generate used vehicle purchase request" module 618 with the appropriate fields in the respective purchase request record. The process purchase request module 604 may utilize the database access module 608 in storing the purchase request record in the Data Center storage medium 106 (Figure 1). The database access module 608 is discussed below.

In one embodiment, the data entry for the purchase request record is completed before data is stored in the Data Center storage medium 106. In another embodiment, the purchase request record fields are stored in the Data Center storage medium 106 as the appropriate information is provided by the buyer.

According to one embodiment of the present invention, the "process purchase request" module 604 may further associate the purchase request record with the appropriate dealer record. For example, a new vehicle purchase request record may, upon creation, or soon thereafter, be logically connected to the dealer record new vehicle purchase requests field 310. The logical connection may be in the form of, for example, a direct entry of the new vehicle purchase request record into the new vehicle purchase requests field, or an entry into a list of new vehicle purchase request records pointed to by the new vehicle purchase requests field. The same association may be made between a used vehicle purchase request record and the dealer record used vehicle purchase requests field 312. As may be appreciated, purchase requests created by a seller are automatically connected to the dealer's records. The dealer may have the option of overriding the automatic connection so as to refer a buyer to another dealer, for example.

Figure 9 is a block diagram illustrating one embodiment of a communication between a buyer 902, a dealer 904, and components of the Data Center system. More particularly, a communication between the buyer 902, the dealer 904, a Data Center server 104, and a Data Center storage medium 106 is illustrated. The buyer 902 may access the Data

Center server 104, through the network 102 and the gateway 110, to create and submit a purchase request in the Data Center system. The Data Center server 104 creates and stores the purchase request, as a purchase request record, in the Data Center storage medium 106. The purchase request is stored such that the dealer 904 may access the purchase request at the time the purchase request record is created, or soon after. In one embodiment, the buyer 902 utilizes the components of the Data Center server 104 to create and store a purchase request record in the dealer's exclusive database region in the Data Center storage medium 106. The purchase request record is stored immediately upon the completion of the purchase request creation and submission process. Also, the dealer utilizes components of the Data Center on the dealer website to create and store a purchase request in its exclusive database region. The components of the Data Center utilized by the dealer may be the same components utilized by the buyer or separate components. The dealer 904 may access its database region to obtain a listing of its purchase requests. Figure 13A generally illustrates a HTML page suitable for use in an embodiment of the invention. A scrollable list of purchase requests, advantageously implemented as links, is displayed generally at 1302. Immediately upon the creation of the purchase request record in the dealer exclusive database region, the list of purchase requests is updated to show the just created purchase request. The dealer 904 may access the Data Center system through the network 102 and the gateway 110. The dealer

904 remotely accesses the Data Center system over the network 102 by providing a URL to identify the Data Center system. Dealers advantageously access the Data Center by providing a URL and preferably not over the world wide web. Thus, access to the Data Center system may advantageously be restricted to those who know the URL and is not as readily reachable by web search engines. Thus, the URL for the buyer to access the system is advantageously HTTP://www.autobγtel.com and the URL for the Dealer site, called Dealer RealTime (or DRT), may advantageously be

HTTP://drt.autobytel.com.

The dealer 904 may access its dealer record and, more particularly, its purchase request records, through the Data Center Server 104. In one embodiment, the appropriate dealer record field contains information from which the purchase request records may be identified and accessed. Alternatively, the purchase request records may contain information identifying the dealer 904. Thus, the purchase request is delivered and communicated to the dealer, upon the creation of the purchase request record, or a short time thereafter.

In one embodiment, a dealer may be notified of a newly created purchase request record upon accessing the Data Center system. The dealer may be notified of a purchase request created while the dealer is concurrently accessing the Data Center system. For example, the dealer may be viewing a screen displaying a list of purchase requests as illustrated in Figure 13A. The appropriate field in the dealer record may be updated to identify the newly created purchase request while the dealer is accessing the Data Center system through a computer 120. The screen is then advantageously refreshed to display a list containing the newly created purchase request immediately upon the creation of the purchase request record, thereby communicating to the dealer the purchase request. In yet another embodiment, the dealer is immediately notified of a new purchase request via communication mechanisms such as e-mail, page, telephone message, or the like, which are triggered in response to the receipt of the purchase request in the dealer record.

The virtual communications path 606 (Figure 6) facilitates communication amongst the modules comprising the Data Center server 104 (Figure 1). The virtual communications path 606 may be implemented as a procedure or a function call interface. In an alternative embodiment, the virtual communications path 606 may be implemented as an interprocess communication method. For example, the modules comprising the Data Center server 104 may be implemented as one or a plurality of software processes. The various software processes may then communicate with one another by means of interprocess communication. Those of ordinary skill in the art will realize that the modules comprising the Data Center server 104 may be distributed amongst a plurality of Data Center servers 104 utilizing well known distributed technology techniques.

The database access module 608 provides an interface to the information stored on the Data Center storage medium 106. The database access module 608 thus enables the Data Center server 104 modules to be implemented independent of the Data Center storage medium 106 specifics. This enables the Data Center storage medium 106 specification to be altered without impacting the various modules, other than the data base access module 608, comprising the Data Center server 104.

In another embodiment, the dealer record advantageously comprises one or a plurality of beeper numbers to be called upon the delivery of a new vehicle purchase request. The process purchase request module 604 may result in the creation of an e-mail message including, for example, beeper number or numbers for the e-mail paging service to call, and address to an e-mail pager service. The e-mail message may then be submitted to the e-mail paging service. The e-mail paging service may then perform the paging, or dialing, function. As is well known in the art, suitable e-mail message paging services are available from companies such as Pagenet, Skγtel, and MCI. The network access module 614 (Figure 6) provides the modules of the Data Center Server 104 (Figure 1) a uniform interface to the LAN 108. In one embodiment, the network access module 614 may be implemented as an application program interface. The network access module 614 enables the Data Center server 104 modules to be implemented independent of the underlying network specifics. Thus, the underlying network specifics may be altered without impacting the various modules, other than the network access module 614, comprising the Data Center server 104.

The dealer access module 612 provides a dealer an interface into the Data Center system. In one embodiment, a dealer management system comprises the dealer access module 612 and may facilitate the dealer's managing its purchase requests. More particularly, a dealer may directly access its exclusive database region, and the information contained therein, by logging into the Data Center system through the dealer access module 612. In one embodiment, the dealer logs into the Data Center system to create a new purchase request. The dealer access module 612 may be implemented as a plurality of HTML pages providing the dealer a mechanism to access its exclusive database region. The Data Center system may advantageously communicate to the dealer its purchase requests through one or a plurality of the HTML pages. An example of one such HTML page is illustrated in Figure 13A. The dealer may also advantageously perform operations, in addition to creating new purchase requests, such as, purchase request management, inventory management, and the like, through the plurality of HTML pages.

Figure 12A illustrates selected components of the dealer access module 612 suitable to implement one embodiment of the invention. The dealer access module 612 may be comprised of a login module 1202, a home module 1204, a manage-customers module 1206, a manage inventory module 1208, an edit request module 1211, a tracking module 1213, and a new request module 1215 as well as other modules. The modules may be comprised of one or a plurality of linked HTML pages which enable the participating dealers to interact with the Data Center system. The modules may further comprise one or more action response modules, such as, by way of example, a purchase request management module, a purchase request listing module, a purchase request detail display module, a status change module, an associate task module, a modify task module, and a list tasks module, which enable a user to efficiently manage purchase requests. In one embodiment, each participating dealer or dealer group is provided with a dealer group login account which the dealer uses to access the Data Center system. Initially, there are ordinarily no users set up in the dealer group login account. Associated with each dealer group login account is a unique dealer group profile record identifying certain characteristics of the dealer group as well as other tuneable characteristics. The dealer logs into the system using a login identification and a password. Upon initially logging into the Data Center system, the dealer creates one or more users with which to access the system. A user may be, for example, a dealer, sales manager, salesperson, or anyone associated with a dealer or dealer group, and who may properly access the exclusive database region and the information contained therein.

A user profile record substantially similar to the group profile record is associated with each user. The user profile record is initially created by the dealer at the time the dealer creates the user. The user profile record comprises one or more filter conditions, and the user profile record is used to filter the information contained in the dealer's exclusive database region. For example, a sales manager may have specified that only purchase requests with "sold" status is to be displayed. Then, for this sales manager, only purchase requests with "sold" status will be displayed. All other information in the exclusive database region will be filtered out. In this and subsequent examples, the use of "user" is not intended to be limiting, but for clarity, examples may also be provided using titles such as, by way of example, sales manager, salesperson A, and salesperson B.

Figure 12B illustrates an example of a user record according to one embodiment of the invention. The Data Center system advantageously stores a user record for each user created by each dealer or dealer group login account. The user record may advantageously be stored in the dealer's exclusive database region. By way of example, five fields are illustrated comprising a user identification 1212, user profile 1214, dealer identification number 1216, purchase request list 1218, and assigned tasks 1220. One of ordinary skill in the art will realize that any number of the fields may be implemented as pointers to other records or fields, may be broken down into additional sub-files, and that additional fields could be added.

Figure 28 illustrates the logical association of screens displayed to a seller by the manage-customers module 1206 when processing purchase requests. The elements of Figure 28 are linked together by arrows which illustrate the logical progression of the seller's interaction with the Data Center system. The figure number notation in an element designated a figure where a screen display corresponding to the element is illustrated. For example, a "(FIGURE 13)" notation is provided within the element with the text entry of "MANAGE CUSTOMERS." Thus a screen display for a "MANAGE CUSTOMERS" portion of the system is illustrated in Figure 13.

Figure 13A illustrates an HTML page 1301 of the manage-customers module 1206. In one embodiment, a scrollable detail display appearing on the right side of the HTML page 1301 does not initially display the details of a purchase request. For example, the seller may select a purchase request from the purchase request listing 1302 by clicking on a customer name link, using a pointing device such as a mouse, or the like. The manage-customers module 1206 displays the contents of the selected purchase request in a purchase request summary form 1304.

The HTML page 1301 includes a purchase request listing form 1302, and a purchase request summary form 1304. A seller employs the manage-customers module 1206 to view and edit purchase requests intended for the seller. The seller can view details of the purchase request from the buyer when discussing the vehicle with the buyer. The seller may also employ the manage-customers module 1206 to review the status of purchase requests that are handled by other users in the seller's groups so as to, for example, critique the performance of such users.

The purchase request listing form 1302 is provided on the left portion of the HTML page 1301. The purchase request summary form 1304 is provided on the right portion of the HTML page 1301. The HTML page 1301 further includes navigational tabs 1309 to navigate between sections of the Data Center system. For example, the navigational tabs 1309 include a tab 1320 to display the initial manage-customers module HTML page 1301. The HTML page 1301 further provides a set of navigational controls 1305 above the purchase request summary form 1304. The navigational controls 1305 include controls to display the purchase request summary form 1304, the purchase request customer form 1704 (Figure 17), the purchase request vehicle form 1804 (Figure 18), the purchase request trade-in form 2004 (Figure 20), the purchase request finance form 2104 (Figure 21), the purchase request rewards form 2204 (Figure 22), the purchase request appointment form 2304 (Figure 23), or the new purchase request form 2404 (Figure 24). Each navigational control is preferably implemented as a link which, when selected, prompts the display of the associated form in the right portion of the HTML page 1301. An exemplary scenario may involve a seller that has just received a telephone call from a buyer who has submitted a purchase request to the seller. The buyer in the illustrated example is Kevin Wagoner whose name is displayed in the "Name" field 1307 of the purchase request summary form 1304. The seller would like, for example, to first retrieve the purchase request that Kevin Wagoner submitted so as to have the information available when discussing the purchase request. The purchase request listing form 1302 is used by the seller to retrieve the purchase request for Kevin Wagoner. Thus, the seller need not request information from Kevin Wagoner which is already provided by the purchase request.

The purchase request listing form 1302 provides a listing of the purchase requests which are directed to the particular seller. In one embodiment, each purchase request is identified by a status such as "new," "could not contact," "quoted," "pending," "sold," or "dead deal." The Data Center system initially assigns the status of "new" to each purchase request submitted to the system. The purchase request listing form 1302 preferably lists the purchase request according to date, status, and customer name. The purchase requests are advantageously displayed with alternating backgrounds to better distinguish purchase requests from one another. In another embodiment, the purchase request may be displayed in varying colors which are dependent on, for example, the status and the date of the purchase request. The information which is displayed in the purchase request listing form 1302 is preferably retrieved from the appropriate fields in the new vehicle purchase request records and the used vehicle purchase request records.

The purchase request listing form 1302 may list the purchase requests according to date, status, and customer name. Also, the purchase requests may advantageously be displayed with alternating backgrounds to better distinguish one purchase request from the next. In another embodiment, the purchase requests may be displayed in differing colors based upon, for example, the status and the date. Thus, for example, new purchase requests that have not been acted on for 48 hours may be displayed in red to indicate that some action should be taken. The displayed information is obtained from the appropriate fields in the new vehicle purchase request records and the used vehicle purchase request records.

The purchase request listing form 1302 includes a customer search tool 1303. The customer search tool 1303 allows the seller to search for a particular purchase request according to, for example, a customer name. The customer search tool 1303 provides the seller with the ability to promptly retrieve purchase requests. In the illustrated example, the seller would search for the name Kevin Wagoner in a purchase request. The customer search tool includes a data entry box 1307 to enter a data string for the search criteria. The field identifier selection box 1309 is used to identify a field of the purchase request records which is compared to the data string in the data entry box 1307. For example, when the "Name" field is selected from the field identifier selection box 1309 the "Name" field in purchase request records is compared to the data string in the data entry box 1307. Thus, the seller selects the "Name" field from the selection box 1309 and enters "Kevin Wagoner" in the data entry box 1307 to search for a "Kevin Wagoner" in the name field of a purchase request. The searching of the purchase request records is preferably undertaken by submitting a query, such as an SQL query, to the database access module 608.

When the search tool 1303 finds the purchase request, the seller may click on the purchase request line in the purchase request listing form 1302 to display further information regarding the purchase request in the purchase request summary form 1304. The seller may want to have the details of the purchase request available for viewing when discussing the purchase with Kevin Wagoner. Thus, the seller selects the purchase request from the purchase request listing form 1302 by clicking the customer name link, "Kevin Wagoner," in the example provided, using a pointing device such as a mouse or the like. The summary information for the selected purchase request is then displayed in the purchase request summary form 1304. The purchase request summary form 1304 provides the seller with background information regarding the buyer, as well as with information regarding the vehicle that the buyer is interested in. For example, the purchase request summary form 1304 provides that Kevin Wagoner is interested in buying a Ford Expedition, and that the status of the purchase request is pending. The purchase request summery form 1304 additionally provides the dealer with a transaction worksheet

1308 which may be used to adjust the transaction price for the purchase. Thus, the purchase request summary form 1304 has a first portion displaying background information regarding the purchase request, and a second portion, namely the transaction worksheet.

The background information portion of the purchase request summery form 1304 allows the seller to determine the model, the body style, the number of cylinders, the exterior color, and the interior color of the vehicle requested. The background information portion also provides the seller with the name of the buyer, the buyer's level of interest, buyer contact information, and whether a trade-in has been offered by the buyer. For example, Kevin

Wagoner wants a Ford Expedition with a green exterior, beige interior, and is not offering a trade-in.

The transaction worksheet 1306 allows the seller to adjust the transaction price by entering values for various costs associated with the vehicle or modifying selections that were earlier made by the buyer when generating the purchase request. For example, Kevin Wagoner may not be willing to pay the price that was quoted in the purchase request. The seller may use the transaction worksheet 1306 to change selections which affect the price of the vehicle.

Figure 13B illustrates the transaction worksheet 1306 of the purchase request summary form 1304. The transaction worksheet 1306 includes a selling price section 1308, a trade equity section 1310, an additional items section 1312, and a transaction price section 1314. The selling price section 1308 is used to adjust the selling price for the vehicle. For example, the price which was made available to Kevin Wagoner may be incorrect. An incorrect price is corrected by entering a value in the MSRP entry box 1316. The seller may additionally enter a value for a discount, which may be offered to the particular buyer. The selling price field 1315 of the selling price section 1308 automatically displays the recalculated selling price, based on the values entered. The trade equity section 1310 allows the seller to adjust the values for a trade-in vehicle, if the buyer is offering one. For example, Kevin Wagoner may be offering a vehicle for a trade-in that the seller believes is worth $1,000. Therefore, the seller enters $ 1,000 in the trade equity section 1310.

The additional items section 1312 allows the seller to designate customer incentives, such as seller discounts that are offered to customers on a time-limited basis, by entering a corresponding value in a customer incentive field 1317. The seller may also enter an amount in a down payment field 1319 to provide an amount that the buyer is willing to pay as down payment for the purchase. A documentation fee may also be entered in the additional item section 1312 of the worksheet 1306.

The seller is provided with the option of modifying vehicle features selected by the buyer by selecting the "Adds" link 1311 from the additional items section 1312. The "Adds" link 1311 is discussed below with preference to Figures 16A-16D. Further, the seller may add charges for miscellaneous items in the miscellaneous item cost field 1321.

A transactional price section 1314 of the worksheet provides the seller with the total price for the particular vehicle. The seller may enter an estimate monthly payment in a monthly payment field. Figure 13C illustrates an HTML page displayed by the manage-customers module 1206 when the seller selects a "Stock Number" link 1315 from the purchase request summary form 1304. The "Stock Number" link 1315 prompts the display of a stock number update form 1318. The stock number update form 1318 is used by the seller to associate the particular vehicle specified in the purchase request with an internal identifier used by the seller. The seller enters a number in the stock number field 1322 of the stock number update form 1318. The seller can then click the "Update Stock Number" button 1324 to update the stock number in the purchase request summary form

1304. The seller may alternatively click the "Reset" button 1326 to discard the stock number entry.

Figure 14A illustrates an HTML page of the manage-customers module 1206 when a status change form 1406 is displayed in response to the selection of the "status" link 1319 from the background information section of the purchase request summary form 1304. The status change form 1406 allows the seller to update the status of the customer purchase request. In one embodiment, the status change form 1304 comprises a status change screen within the scrollable detail display. The seller may advantageously change the status to reflect certain buyer feedback obtained during a communication with the buyer. The communication may, for example, be a phone conversation, an e-mail message, or a face-to-face meeting. For example, after talking to Kevin Wagoner, the seller may want to change the status of the purchase request from "new" to "quoted" because the buyer was provided with a quote price of $10,000. The seller then changes the status of the purchase request from its current status of "new" to a status of "quoted."

The new status may be selected from a status selection box 1410. Selecting the "quoted" status from the status selection box 1410 requires the user to provide an amount quoted in a quote amount field 1412. In the example, the seller enters "10,000" in the quote amount field 1412. When a "dead deal" status is selected from the status selection box 1410 the seller should generally provide a corresponding reason by making a selection from a dead deal reason selection box 1414. A "dead deal" status exists when the buyer no longer wishes to purchase a vehicle from the seller because, for example, the price is not low enough. The dealer then selects "price differences," for example, as the reason for the "dead deal." Fields requiring user input may be indicated, for example, by a flashing red light appearing beside the required field.

Figure 14B illustrates the status change form 1406 when the scroll-bar is moved down. As may be appreciated, the seller may specify a memo in a memo field 1416. For example, the salesperson may provide a memo indicating the reason for the price quote of $10,000. The contents of the memo may be maintained along with the purchase request status and may advantageously be displayed along with the status. The contents of the memo may be displayed using a different font or a different color to better identify the memo's contents. In another embodiment, the memo contents may be maintained in a separate record pointed to by either the status field 730 in the new vehicle purchase request record or the status field 826 in the used vehicle purchase request record. The status change form 1406 further allows the seller to set a time and date for a meeting or other contact with the buyer such as by telephone. The seller can specify a particular salesperson to contact the buyer so as to assign an appointment to particular individuals within the seller's organization. It is understood that the permission to set appointments is generally provided only to management level sellers so as to control the assignment of appointments to salespersons. For example, the seller may wish that a salesperson knowledgeable in Ford Expeditions contact Kevin

Wagoner to discuss the vehicle.

Figure 14C illustrates the status change form 1406 when the scroll bar is moved to the bottom of the scrollable area. Having made the appropriate status selection, the user may click on a "Submit" button 1418. Alternatively, the user may click on a "Reset" button 1420 to discard the changes. Figure 15 illustrates the vehicle options detail form 1502 that is displayed when the seller selects the

"Options" link 1504 from the purchase request summary form 1304. The "Options" link 1504 is provided in the background information section of the purchase request summary form 1304. The vehicle options detail form 1502 provides the seller with a listing of the options which were selected by the buyer for the requested vehicle. The options may include factory installed items such as an automatic transmission, or after-market items such as a CD- changer. The seller may wish to view the buyer selected options when, for example, the seller and the buyer are discussing how the price of the vehicle may be lowered by choosing different options. For example, the seller may offer Kevin Wagoner a different "Tire and Wheel" package which is less costly than the one selected. A modify options form 1602 which is discussed with reference to Figures 16A-16D is employed to modify such selections. The option information in the vehicle option detail form 1502 includes the options title, the manufacturer suggested retail price for the option, and the invoice price for the option. Additionally, the option detail module provides the total

MSRP price and a total invoice price for the vehicle with the selected options.

Figure 16A illustrates a modify options form 1602 that is displayed when the seller selects an "Adds" link 1311 from the additional items section of the transaction worksheet 1306 of the purchase request summary form 1304. The modify options form 1602 provides the seller with a selectable list of options for the particular vehicle. The list of options is preferably generated by the edit request module 121 1 submitting a query, such as an SQL query, to a database which stores a table with records that include options in accordance with vehicle type and vehicle make. Each option listed in the modify options form 1602 is associated with a check box. A check mark in a check box indicates that the option corresponding to the check box is selected for the particular purchase request. The seller can select the check boxes in accordance with either buyer instructions or seller modifications of the purchase request. The seller, in the illustrated examples, may wish to modify the options selected by Kevin Wagoner for the vehicle. For examples, the seller can de-select the "Tire and Wheel" option to remove the option for the vehicle. The ability to modify the option selections made by the buyer in the originally transmitted purchase request adds flexibility to the seller's operation. The ability to modify buyer selected options also increases efficiency by allowing the seller to use the purchase request with the information already contained in the purchase request while modifying only a small portion of the purchase request instead of having to re-enter the information in accordance with a new selection of options.

Figure 16B illustrates a lower portion of the modify options form 1602 of Figure 16A when the scroll bar has been moved further down. As may be appreciated from Figure 16B, certain items are selected while other items are not selected as options for the vehicle in the Kevin Wagoner purchase request. Figure 16C illustrates a lower portion of the modify options form 1602. The bottom portion of the displayed screen includes an "additional charges" box 1604 and an "estimated MSRP" box 1605. The value which appears in the "estimated MSRP" box 1605 is automatically calculated based on the options which are selected by the seller and based on the base MSRP for the particular vehicle. For example, the MSRP for the vehicle in the Kevin Wagoner purchase request is $24,238. Figure 16D illustrates the bottom portion of the modify options form 1602 displaying the "Update Vehicle

Information" button 1606 and the "Reset" button 1608. The seller may click on the "Update Vehicle Information" button to update the options selection for the particular vehicle. The seller preferably confirms the changes to the options before clicking on the "Update Vehicle Information" button. For example, the seller may read the selected options to Kevin Wagoner and ask him to confirm the selections. The seller may click on the "Reset" button to discard the changes to the vehicle options. The total cost of the options is automatically updated in the "Adds" field 1610 of the additional items section 1312 of the transaction worksheet 1304. Furthermore, the total transaction price is automatically updated when the seller selects the "Update Vehicle Information Button 1606 from the modify options form 1602.

Figure 17A illustrates an HTML page of the manage-customer module 1301 when the purchase request customer navigational control is selected. The purchase request customer form 1704 is displayed on the right portion of the HTML page. The purchase request customer form 1704 is used to review and update customer information. For example, if Kevin Wagoner has moved to a new address, the seller may make the appropriate changes to the information. A first section 1706 of the purchase request customer form 1704 provides the activity history for the particular purchase request. The seller may wish to determine what other communications have taken place with regard to the particular purchase request when discussing the purchase request with the buyer. A second section

1708 of the purchase request customer form 1704 displays a status change section 1406. The status change section 1406 is used by the seller in the same manner as that which was described with reference to Figures 14A, 14B, and 14C.

Figure 17B illustrates the purchase request customer form 1704 when the scrollbar is moved down. A customer information section 1708 is displayed below the status change section 1406. The customer information section 1708 allows the seller to change information regarding the customer. The information that the seller can change by using the customer information section 1708 includes address information, the buyer's name, and information regarding customer preferences. The seller may wish to change the buyer information if the customer initially provided erroneous information when providing data for the purchase request. For example, Kevin Wagoner may have expressed an interest in the vehicle on behalf of a friend and has entered his own name in the purchase request instead of the friend's name. The seller would like the correct name entered in the purchase request for the person who is actually buying the vehicle. Thus, the seller is provided with the flexibility of making changes to the buyer information by employing the customer information section 1708.

Figure 17C illustrates the purchase request customer form 1704 when the scrollbar is moved to the bottom of the scrollable area. The customer information section 1708 further includes a payment method field 1710, a contact method field 1712, a referral field 1714, and a best time to contact field 1716. For example, Kevin Wagoner is interested in cash payment and can best be contact in the evening. The customer information module also includes an "Update Customer Information" button 1718 and a "Reset" button 1720. The seller may click the "Update Customer Information" button 1718 to update the information in accordance with the changes that the seller has entered. Preferably, the seller first confirms the correctness of the information with the buyer. The seller may also select to discard the entered changes by clicking the "Reset" button.

Figure 18A illustrates the purchase request vehicle form 1804. The purchase request vehicle form 1804 is displayed when the "purchase request vehicle" navigational control is selected by the seller. The purchase request vehicle form 1804 is employed by the seller to view and edit detail regarding the vehicle in the purchase request. For example, Kevin Wagoner may wish to change certain selections in the vehicle options. The purchase request vehicle form 1804 provides the seller with information regarding the vehicle that was selected in the purchase request. The information provided to the seller includes the vehicle make, the vehicle stock number, the vehicle series, the level of features in the vehicle, and the vehicle's interior and exterior colors. Additionally, the seller is provided with a listing of the options that are currently selected for the particular vehicle. Figure 18B illustrates the purchase request vehicle module 1804 when the scrollbar is moved to the bottom of the scrollable area. As may be appreciated, additional option listings are displayed in the bottom portion of the purchase request vehicle form 1804. The purchase request vehicle form 1804 further displays the total cost for the vehicle based on the selected options.

Figure 18C illustrates an HTML page generated by the customer management module when the seller selects a "Standard" link 1806 from the purchase request vehicle form 1804. The "Standard" link 1806 is associated with a standard features screen 1808 which presents the seller with the standard features for the particular vehicle. The seller may be discussing the vehicle with Kevin Wagoner when the seller is asked for information regarding the features that are included in the vehicle base price. The "standard" link 1806 can be used to display such information. The standard features screen 1808 lists features found in several vehicles. Preferably, features that appear in bold- face type are the features that are standard for the buyer selected vehicle.

Figure 18D further illustrates the standard features screen 1808 when the scrollbar of the screen is moved to the bottom. As may be appreciated, additional features are in bold-face, indicating that the features are standard for the selected vehicle.

Referring back to figure 18A, the seller is provided with a modify vehicle selection box 1802 so as to modify the vehicle that is selected in the purchase request. The seller may wish to modify the vehicle that was selected in the purchase request when, for example, Kevin Wagoner changes the vehicle selection. The seller may also wish to change the vehicle selection so as to offer Kevin Wagoner a lower or higher cost alternative to the original vehicle selected. The modifications to the vehicle selection may take place in three ways. First, the seller may change the details of the particular vehicle selected, such as the vehicle options or engine size. Second, the seller may select a new vehicle. Third, the seller may select a used vehicle. Thus, the modify vehicle selection box 1802 offers three options to the seller.

Figure 19A illustrates a purchase request detail form 1904 which is displayed in response to a selection of the "modify existing car" option 1803 from the modify vehicle selection box 1802 in Figure 18A. In the illustrated example, Kevin Wagoner may only wish to change the selection of options for the vehicle. Thus, the "modify existing car" option is selected. Preferably, the purchase request detail module 1904 is applicable to selecting options for new vehicles only, because used vehicles already have options pre-installed and therefore are not amendable to a change in options selection. The purchase request detail form 1904 is preferably used for both changing options for a vehicle selected in an existing purchase request and for choosing options for a new vehicle when creating a new purchase request, as discussed below with reference to Figures 20A-20E. The purchase request detail form 1904 includes a first section 1906 which displays the vehicle make and model, as well as the features level for the vehicle. A second section of the purchase request vehicle form 1904 includes a color selection box 1908 to allow the seller to select the exterior and interior colors of the vehicle. For example, Kevin Wagoner may wish to change the vehicles colors from a green exterior and a beige interior to a black exterior and a white interior. Figure 19C illustrates the options that are provided when the seller clicks on the color selection box 1 08. The selections provided by the color selection box 1908 are preferably retrieved by the database access module 608 from a record in the database which includes the available colors for particular vehicle models. Referring back to figure 19A, a third section 1910 of the purchase request detail form 1904 displays a listing of options which are available for the vehicle. The bottom portion of the third section 1910 is illustrated in Figure 19B. The third section 1910 provided the seller with the same functionality in changing vehicle options as the modify options form 1602, discussed above with reference to Figure 16A.

Figure 19C illustrates a color selection box 1908 of the purchase request detail form 1904. As may be appreciated, the seller can select from several colors which are available for the selected vehicle. The color combination listing in the color selection box 1908 is preferably retrieved from the new vehicle record (Figure 4) for the selected vehicle. Figure 20A illustrates a new vehicle selection form 2004 which is displayed in response to a selection of the

"select new car" option 1805 from the modify vehicle selection box 1802 in Figure 18A. For example, Kevin Wagoner may have changed his mind and would like to purchase a different new vehicle. The seller thus selects the "select new car" option. The new vehicle selection form 2004 initially displays a new vehicle make selection box 2006. When the seller clicks on the new vehicle make selection box 2006, a listing of vehicle manufacturers is displayed. The vehicle make listing data is preferably retrieved from database records which specify the manufacturers for new vehicles that are available to the seller. Preferably, the seller selects a vehicle manufacturer from the new vehicle make selection box 2006 in accordance with buyer instructions when discussing a potential purchase. For example, Kevin Wagoner may tell the seller that he wants an Acura instead of a Ford. Once the seller selects the vehicle make, the new vehicle selection form 2004 displays a new vehicle model selection box 2008 as illustrates in Figure 20B. The new vehicle model selection box 2008 displays a vehicle model listing when the seller clicks on the box.

The vehicle model listing is preferably generated by submitting a query to the Data Center database to retrieve the vehicle models that are available for the particular manufacturer selected in the new vehicle make selection box 2006. For example, the vehicle models manufactured by "Acura" and are offered by the seller, are displayed in the new vehicle model selection box 2008. The seller may read the available models to the buyer on the telephone. The buyer then selects a model, for example, by instructing the seller. When the seller selects a vehicle model from the new vehicle model selection box 2008, a new vehicle series selection box 2010 is displayed by the new vehicle selection form 2004 as is illustrated in Figure 20C.

The new vehicle series selection box 2010 displays a listing of the vehicle configurations that are offered for the particular vehicle model selected in the new vehicle model selection box 2008. For example, a particular model may be offered in a two door configuration or in a four door configuration. In Figure 20C, the "3.2TL-1999 Acura" is only offered in a single configuration. The seller clicks on a "Submit Vehicle Information" button 2012 to update the purchase request record in the corresponding database. After the seller clicks on the "Submit Vehicle Information" button 2012, the purchase request detail form 1906 is displayed. The purchase request detail form 1906 is used by the seller to select the options for the new vehicle as was discussed above with reference to Figure 19A, 19B, and 19C. Preferably, the seller asks the buyer for the desired options and selects such options from the purchase request detail form 1906.

Figure 21 A illustrates a used vehicle selection form 2104 which is displayed in response to a selection of the "select used car" option 1804 from the modify vehicle selection box 1802 in Figure 18A. In the illustrated example, Kevin Wagoner may be interested in purchasing a used vehicle instead of the 1999 Ford Expedition. The used vehicle selection form 2104 initially displays a used vehicle make selection box 2106. When the seller clicks on the used vehicle make selection box 2106, a listing of vehicle manufacturers is displayed. The vehicle make listing data is preferably retrieved from database records which specify the manufacturers for used vehicle that are available to the seller. The database records are preferably retrieved by submitting a query which searched the used vehicle records for the dealer identifier in the dealer identification field 302. Preferably, the seller selects a vehicle manufacturer from the used vehicle make selection box 2106 in accordance with buyer instructions when discussing a potential purchase.

For example, Kevin Wagoner may want a used Ford. As illustrated in Figure 21 B, once the seller selects the used vehicle make, a used vehicle model selection box 2108 is displayed.

The used vehicle model selection box 2108 displays a used vehicle model listing when the seller clicks on the box. The used vehicle model listing is preferably generated by submitting a query to the Data Center database to retrieve the used vehicle models that are available for the particular manufacturer selected in the used vehicle make selection box 2106. For example, in Figure 21 B the used vehicle models manufactured by "Ford," that are offered by the seller, are displayed in the used vehicle model selection box 2108. The seller provides the available models to Kevin Wagoner to decide on a vehicle model. As illustrated in Figure 21 C, when the seller selects a vehicle model from the used vehicle model selection box 2108, a used vehicle series selection box 2110 is displayed. The used vehicle series selection box 2110 displays a listing of the vehicle configurations that are offered for the used vehicle selected in the vehicle model selection box 2108. In Figure 21 C, the "1997 Ford Expedition" selected by the seller is only offered in a single configuration. After confirming the information the seller clicks on a "Submit Vehicle Information" button to update the purchase request record in the corresponding database. After the seller clicks on the "Submit Vehicle Information" button, the used vehicle selection module 2104 prompts a used vehicle purchase request detail module 2104.

Figure 21 D illustrates the used vehicle purchase request detail form 2103. The used vehicle purchase request detail form 2103 displays the vehicle information for the used vehicle selected by the seller in the used vehicle selection form 2104. The vehicle information includes the make and model, the engine size, the transmission type, the vehicles color, the options installed in the vehicle, the retail price of the vehicle, and the mileage level on the vehicle. The seller, in the illustrated example, reads the information to Kevin Wagoner. If the buyer is satisfied with the information provided, the seller can click on the "Submit Used Vehicle" button 2111 to choose the particular vehicle. For example, the seller may be satisfied with the vehicle information after reading the information to a buyer on the telephone who subsequently decides to purchase the vehicle. A "Select Used Car" link 2112, and a "Select New Car" link 2114 are provided to enable the seller to return directly to either the used car selection module 2104, or to the new car selection module 2004, respectively.

Figure 22 illustrates the purchase request trade-in form 2204 which is presented when the seller selects the purchase request trade-in navigational control from the navigational controls of the manage-customers initial screen 1301. The purchase request trade-in form 2204 allows the seller to enter or modify trade-in information that may be associated with the purchase request. Such information may include, for example, the make, the model, and the mileage level of the vehicle which is offered as a trade-in. For example, Kevin Wagoner may have a 1993 Ford Explorer that he is offering as a trade-in. The seller would enter the information for the 1993 Ford Explorer in the purchase request trade-in in module 2204.

Figure 23 illustrates a finance information form 2304 which is provided when the seller selects the purchase request finance navigational control from the navigational controls 1305. The finance information form 2304 provides the seller with information regarding possible financing that the buyer is interested in. The seller can use the finance information form 2304 to submit a finance application for the buyer. The seller can click on an "Enter Finance Application" link 2306 to prompt a finance application module (not shown). An example of a time when the seller may wish to enter a finance application for the buyer is when the buyer, during a telephone conversation inquires with the seller regarding financing options. For example, Kevin Wagoner may wish to take a loan to pay for the vehicle. The seller can create a loan application by clicking on the "enter finance application" link 2306. Figure 24 illustrates a rewards information form that is displayed when the purchase request rewards navigational control is selected from the navigational controls 1305. The rewards information is used by the seller to provide buyers with reward points that can be later redeemed for services and merchandise.

Figure 25A illustrates an appointment list form 2504 which is displayed when the purchase request appointment navigational control is selected from the navigational controls 1305. The appointment list form 2504 provides the seller with the appointments that are scheduled for the particular seller that is using the Data Center system. An "Edit" link 2506 is provided next to the listed appointments to allow the seller to edit the appointment data. Figure 25B illustrates the appointment edit form 2508 which is displayed when the "edit" link 2506 is selected from the appointment list form 2504. The seller can change the date of the appointment, the time of the appointment, the status of the appointment, the action to be taken during the appointment, the particular seller assigned to the appointment, and enter notes regarding the appointment in a memo section. For example, an appointment may have already been set for Kevin Wagoner, which the seller wants to change or reschedule. The seller can then click on a "Submit" button 2510 to submit the changes made to the appointment data. A "Reset" button 2512 allows the seller to discard the changes. Figure 26A illustrates the purchase request new customer form 2604 that is presented on the right side of the HTML page when the user selects the purchase request new navigational control from the navigational controls 1303. The purchase request new customer form 2604 enables the seller to enter information for a new purchase request. As a second illustrated example, a walk-in customer may wish to submit a purchase request to the seller. The walk-in customer is at the dealership and is discussing a possible vehicle purchase with a seller. The seller can employ the same system used to manage and edit purchase requests generated by the public buyer site to create a new purchase request. The seller can employ the purchase request new customer form 2604 to submit purchase requests for customers that have not created purchase requests by using the dedicated customer web-site.

Because the seller system allows a new purchase request to be entered and stored by the system, the seller does not need to employ a separate system to track buyer interest for walk-in customers, for example. Thus, the seller can use a single system to track all customer purchase requests. The purchase request new customer feature simplifies the management of purchase requests for a dealer and encourages dealers to use the Data Center system to manage purchase requests. The dealer does not have to go from one system to another when dealing with customers that have contacted the dealer by submitting a purchase request or by arriving physically at the dealership. Therefore, the dealer is able to provide better service to customers and more efficiently use dealership resources by not having to use a separate system for walk-in customers, for example.

Generally, the purchase request new customer form 2604 would include fields similar to those presented to buyers when creating a purchase requests by using the dedicated customer web-site. The seller can enter buyer background information such as the buyer's name, address, telephone number, and contact information. Preferably, the seller asks the walk-in customer for information that is requested by the system. For example, the seller asks the walk-in customer for a home address, and telephone number. Figure 26B illustrates the purchase request new customer form 2604 when the scrollbar to the right of the module has been moved down. A "Submit" button 2606 is available for submitting the buyer information to the Data

Center system. The seller preferably confirms the information with the walk-in customer. The seller clicks on the

"Submit" button 2606 to proceed with the generation of the new purchase request. The seller can alternatively click a "Reset" button 2608 to discard the data that was entered.

In one embodiment, the new purchase requests that are entered by the seller are stored in the same database as the purchase requests generated by customers. Thus, the new purchase request are managed in the same manner as the purchase requests that are generated by the customer public website.

Figure 27 illustrates an HTML page that is displayed in response to the seller clicking the "Submit" button 2606 in the purchase request new vehicle form 2604 that is illustrated in Figure 26B. The screen includes a selection box 2702 to choose a new car or to choose a used car. The seller, for example, asks the walk-in customer if they are interested in a new car or a used car. When the seller selects the new car option, the new vehicle selection form 2004 is prompted and is employed by the seller to select a new vehicle as discussed with reference to Figures 20A, 20B, and 20C. The seller asks the walk-in customer for information regarding the vehicle such as make, model, color, and options. When the seller selects the used car option, the used vehicle selection form 2104 is prompted and is employed by the seller to select a used vehicle as discussed with reference to Figures 21 A, 21 B, 21 C, and 21 D. Thus, the purchase request new customer form 2604 can be used for both entering purchase requests for new vehicles and for entering purchase requests for used vehicles.

Figure 29 illustrates the tracking module 1213 of the Data Center system. In one embodiment, The seller exclusive database region comprises an original purchase request table 2904, and with a modified purchase request table 2906. The original purchase request table 2904 stores purchase requests that are directed to the seller exclusive database region from either the public buyer website or from the seller website. The purchase request records in the original purchase request table 2904 are preferably of the format provided in Figure 7 and in Figure 8. For example, a purchase request was stored in the original purchase request table 2904 when Kevin Wagoner first created a purchase request by using the buyer website.

A modified purchase request table 2906 is used to store any modified versions of a purchase request. In one embodiment, all purchase request records directed to the seller exclusive database region are automatically stored in both the original purchase request table 2904 and in the modified purchase request table 2906. In another embodiment, a copy of an original purchase request record is first stored in the modified purchase request table 2906 only after the first modification to the purchase request is submitted to the system by, for example, clicking the

"Submit Changes" button. When the seller makes modifications to the purchase request information, the modified purchase request, containing the modified information, is stored in the modified purchase request table 2906. Any subsequent changes to the purchase request information is reflected by overwriting the corresponding purchase request record in the modified purchase request table 2906 with a purchase request record containing the up-to-date information. In the illustrated example, a purchase request record for Kevin Wagoner is stored in the original purchase record table 2904 and in the modified purchase request table 2906 because modifications have been made to the purchase request. The information that is presented to the seller when reviewing purchase request information for Kevin Wagoner is retrieved from the up-to-date purchase request record, which is the purchase request record in the modified purchase request table 2906. Thus, a change to the vehicle options in the purchase request for Kevin

Wagoner, for example, is reflected by overwriting the stored purchase request record in the modified purchase request table 2906 with a purchase request record containing the changes to the vehicle options.

Modifications to a purchase request are made on a copy of the original purchase request. In one embodiment, the information in the original purchase request is preserved by making a copy of the data in the original purchase request before changing any information. For example, in the illustrated example, Kevin Wagoner may have changed the option selection for the vehicle. The seller has entered the changes to the purchase request for Kevin Wagoner. Thus, the current information in the purchase request is different from the information in the original purchase request. Kevin Wagoner may have selected a black and white vehicle instead of a green and beige vehicle. Thus, because the modifications to the purchase request were made on a copy of the purchase request, the selections in the original purchase request are still available to the modules of the system. Particularly, a tracking module 1213 can be employed to track consumer purchasing tendencies.

Preferably, the same purchase request identification number is associated with both the original purchase request in the original purchase request table 2904 and the modified purchase request in the modified purchase request table 2906. In an alternative embodiment, several versions of the purchase request may be stored to provide additional information regarding the progression of the purchase transaction, as discussed below.

The tracking module 1213 retrieves purchase request data from purchase request records in the original purchase request table 2904, and in the modified purchase request table 2906 to extract data relevant to consumer purchasing tendencies. The tracking module 1213, in one embodiment, compares purchase request records which have the same purchase request identification number. Specifically, the tracking module 1213 may compare the vehicle make, and model. If the vehicle make and model are identical, the tracking module may proceed further and compare the options selected for the vehicle. Furthermore, if the options selected for the vehicle are also identical, the tracking module 1312 may proceed further to other data in the purchase request records to ascertain the differences between the two purchase request records. In the illustrated example, because Kevin Wagoner selected a different color for the vehicle, the tracking module 1213 will determine that the color selection for a Ford Expedition has been changed from a green/beige to a black/white. The tracking module 1213 may process in such fashion several purchase request records so as to ascertain the changes which were made to the purchase requests. In another embodiment, the seller can control the tracking module to specify particular fields of purchase request records which are to be compared.

The comparison of the modified purchase request record and the original purchase request record, may be indicative of the decisions made by the customer, or seller. For example, a comparison of the two records may reveal that the vehicle's color was changed from white to black and that the price was reduced by $2000. The tracking module 1213 can employ the results of a comparison for several purchase request to detect patterns that may be indicative of buyer tendencies or seller performance. For example, several purchase requests may indicate that the buyer has changed from an initial interest in a Ford Explorer to a Toyota 4-Runπer. Thus a pattern may be determined by the tracking module 1213 which indicates that consumers tend to change from Ford Explorer to Toyota 4-Runner.

In a second example, the manager of the seller's organization may want to determine how vehicle prices are changed by its seller employees. The change in total vehicle cost from the original purchase request record to the modifier purchase request record can be ascertained. Other patterns within the data may be determined in a similar fashion. The tracking module 1213 may be implemented by a data pattern recognition engine such as a data mining engine or a Neural Network arrangement as is generally known to those of ordinary skill in the art. Alternatively, a simple pattern detection algorithm with predefined patterns may be employed.

This invention may be embodied in other specific forms without departing from the essential characteristics as described herein. The embodiments described above are to be considered in all respects as illustrative only and not restrictive in any manner. The scope of the invention is indicated by the following claims rather than by the foregoing description.

Claims

WHAT IS CLAIMED IS:

1. In a computer system used to process purchase requests that are electronically transmitted from buyers to sellers, a method of tracking buyer purchase requests and purchases, comprising: electronically storing transmitted purchase requests in first storage locations, each purchase request associated with an identifier; electronically storing purchase records in a second storage location, the purchase records generated by electronically editing the information of a transmitted purchase request, wherein the identifier of the edited transmitted purchase request is stored with said purchase record; comparing a transmitted purchase request to a purchase record that is associated with the same identifier; and observing at least one buyer purchasing tendency based on said comparison.

2. The method of Claim 1, wherein the purchase requests are generated by buyers interacting with an Internet website.

3. The method of Claim 1, wherein the purchase requests are for vehicles.

4. A method of ascertaining information regarding customer purchasing tendencies, comprising: storing an original purchase request that is transmitted to a seller by an electronic communication link in a first data location; storing a modified version of said original purchase request in a second data location; and comparing a first plurality of said original purchase requests to a second plurality of corresponding modified versions of said original purchase requests of said first plurality to ascertain information regarding customer purchasing tendencies.

5. The method of Claim 4, wherein the purchase requests are generated by buyers interacting with an Internet website.

6. The method of Claim 4, wherein the purchase requests are for vehicle purchases.

7. The method of Claim 4, wherein the purchase requests are received by an electronic communication link.

8. A system for tracking customer purchase requests and purchases, comprising: means for receiving purchase requests that are generated by customers at a remote location; means for creating a purchase record using at least one item of information from one of said purchase requests; means for storing said purchase requests and said purchase records; means for extracting data regarding customer purchase requests and purchases by using said purchase requests and said purchase records.

9. A purchase request management system comprising: a first purchase request stored in said management system, said first purchase request includes one or more fields, said first purchase request belonging to a buyer; a second purchase request stored in said management system wherein said second purchase request includes one or more fields which are different from the respective fields in said first purchase request, said second purchase request belonging to said buyer; a request to compare at least one field in said first purchase request to the respective field in said second purchase request; and a statistical chart elected from one of the following types of charts: bar chart, line chart, pie chart, reflecting the results of said request to compare.

10. The system as defined in Claim 1 , wherein said first purchase request is created over the Internet.

11. A purchase request management system comprising: a first purchase request stored in said management system, said first purchase request includes one or more fields, said first purchase request created by a buyer; a request to modify one or more fields in said first purchase request received from said buyer wherein said modifications are made by a seller; and a second purchase request stored in said management system wherein said second purchase request is a copy of said first purchase request including said one or more modifications requested by said buyer.

12. The system as defined in Claim 3, wherein said first purchase request is created by said buyer over the Internet.

13. The system as defined in Claim 3, wherein said first purchase request is created by said buyer using a first interface.

14. The system as defined in Claim 3, wherein said first purchase request is created by said buyer using a first interface and said modifications are made by said seller through a second interface.

15. A purchase request management system comprising: a first purchase request stored in said management system, said first purchase request includes one or more fields, said first purchase request created by a buyer; a second purchase request stored in said management system wherein said second purchase request is a copy of said first purchase request including one or more modifications requested by said buyer; and a third purchase request stored in said management system wherein said third purchase request is a copy of said first purchase request including one or more modifications requested by said buyer, said third purchase request contains at least one field which is different from said second purchase request.

16. A purchase request management system comprising: a first purchase request stored in said management system, said first purchase request includes one or more fields, said first purchase request belonging to a buyer; a second purchase request stored in said management system wherein said second purchase request is a copy of said first purchase request including one or more fields different from the respective fields in said first purchase request, said differences reflect one or more modifications requested by said buyer; and a request to compare at least one field in said first purchase request to the respective fields in said second purchase request.

17. A method of managing purchase requests, comprising the acts of: storing a first purchase request, said first purchase request includes one or more fields, said first purchase request belonging to a buyer; storing a second purchase request, said second purchase request is a copy of said first purchase request including one or more fields which have been changed to reflect modifications requested by said buyer; comparing said one or more fields in said first purchase request to the respective fields in said second purchase request; and observing the result of said comparison.

18. The method as defined in Claim 9 wherein said first purchase request is created by said buyer over the Internet.

19. A method of managing purchase requests, comprising the acts of: storing a first purchase request wherein said first purchase request includes one or more fields, said first purchase request belonging to as buyer; creating a second purchase request wherein said second purchase request is a copy of said first purchase request; and modifying one or more fields in said second purchase request in response to a modification request from said buyer, said modifications are performed by a seller.

20. A purchase request management system comprising: a first purchase request stored in said management system, said first purchase request includes one or more fields, said first purchase request submitted a buyer; a request to modify one or more fields in said first purchase request received from said buyer wherein said modifications are made by a seller; and a second purchase request stored in said management system wherein said second purchase request is a copy of said first purchase request including said one or more modifications requested by said buyer.

21. A purchase request management system comprising: a first purchase request stored in said management system, said first purchase request includes one or more fields, said first purchase request requested by a buyer and created by a seller; a request to modify one or more fields in said first purchase request received from said buyer wherein said modifications are made by said seller; and a second purchase request stored in said management system wherein said second purchase request is a copy of said first purchase request including said one or more modifications requested by said buyer.

22. A method of managing purchase requests, comprising the acts of: storing a first purchase request, said first purchase request includes one or more fields, said first purchase request created by a buyer; storing a second purchase request, said second purchase request is a copy of said first purchase request including one or more fields which have been changed to reflect modifications requested by said buyer; comparing said one or more fields in said first purchase request to the respective fields in said second purchase request; and creating a statistical chart reflecting the result of said comparison.

23. The method as defined in Claim 14, wherein said statistical chart reflects changes made to one or more fields in one or more purchase requests.

24. The method as defined in Claim 14, wherein said statistical chart is a bar graph.

25. The method as defined in Claim 14, wherein said statistical chart reflects one or more buyers' tendencies.