Method and system for placing a purchase order via a communications network

The present invention relates to computer methods and systems for placing orders, and more specifically,<u style="single">In the client system for ordering items</u>Method and<u style="single">How in a server system to accept an order for an item</u>Regarding.

The Internet consists of a large number of computers and computer networks, which are interconnected through communication links. The interconnected computers use a variety of services, such as e-mail, Gopher, and the World Wide Web ("WWW"), to exchange information. WWW services allow a server computer system (ie, a web server or website) to send web pages of graphic information (figures, images, etc.) to a remote client computer system. The remote client computer system can then display the web page. Each WWW resource (for example, a computer or a Web page) can be uniquely identified by a URL (Uniform Resource Locator). To display a particular web page, the client computer system requests (for example, Hypertext Transfer Protocol (HTTP:)). Specify the URL of the web page in the Hyper Text Transfer Protocol) request). This request is forwarded to the web server that supports the web page. When the web server receives the request, it sends the web page to the client computer system. When a client computer system receives a Web page, it typically uses a browser to display the Web page. A browser is a special purpose application program that makes web page requests and displays web pages.

Currently, web pages are typically defined using the Hyper Text Markup Language (HTML). HTML is a standard consisting of a collection of tags that define how a web page is displayed. When the user instructs the browser to display the web page, the browser sends a request to the server computer system to forward the HTML document defining the web page to the client computer system. When the requested HTML document is received by the client computer system, the browser displays the web page as defined in the HTML document. HTML documents contain various tags that control the display of text, graphics, controls, and other features. The HTML document can include the URLs of other web pages available on that server computer system or other server computer systems.

World Wide The Web) is especially useful for conducting electronic transactions. Through it, a number of web servers have been developed that allow vendors to promote and sell their products. Some of these products are items that are delivered electronically to buyers over the Internet (eg, music) and items that are delivered through traditional delivery channels (eg, carriers) (eg, books). and so on. The server computer system may have an electronic catalog listing the items offered. A potential purchaser user can use a browser to browse the catalog and select various items to purchase. When the user completes the selection of the item to be purchased, the server computer system requests the user for information to complete the order for that item. The purchaser-specific order information includes the purchaser's name, the purchaser's credit card number, the shipping address of the order, and the like. The server computer system then typically sends a confirmation web page to the client computer system to confirm the order and then schedule the shipment of the item.

Since buyer-specific order information contains sensitive information (eg, credit card numbers), both vendors and buyers want to ensure the security of such information. There is. Security is of concern because information transmitted over the Internet can travel through various intermediate computer systems on the way to its final destination. .. This information can be intercepted by a mindless person in the intermediate system. Various encryption techniques are used when transmitting such information between client computer systems and server computer systems to help ensure the security of sensitive information. Even if such encrypted information is intercepted, it is generally not useful to the interceptor because the information is encrypted. Nevertheless, there is always the possibility that such sensitive information may be deciphered by the interceptor. Therefore, it is desirable to minimize the sensitive information transmitted when placing an order.

<p> Selecting various items from the electronic catalog is a "shopping cart" ) Models are generally the basis. When the buyer selects an item from the electronic catalog, the server computer system metaphorically adds the item to the shopping cart. Once the buyer completes the item selection, all items in the shopping cart are "checked out" (that is, ordered) when the buyer gives information about invoicing and shipping. In some models, when a buyer selects an item, that item is "checked out" by automatically requesting invoicing and shipping information from the user. The shopping cart model is very flexible and intuitive, but it has the drawback of requiring a lot of interaction on the part of the buyer. For example, the purchaser selects various items from the electronic catalog and then indicates that the selection is complete. The buyer is then presented with an ordering web page that requires the buyer to request buyer-specific order information to complete the order. This web page may pre-populate the information that the buyer gave you when you placed another order. This information is validated by the server computer system and the order is completed. Such an ordering model can be problematic for several reasons. When a buyer orders only one item, the overhead of reviewing the various steps in the ordering process, waiting for, displaying, and updating buyer-specific order information is far more than the overhead of selecting that item itself. Can grow to. This overhead makes the purchase of a single item cumbersome. Also, according to this ordering model, sensitive information is transmitted over the Internet each time an order is placed. This sensitive information may be intercepted and decrypted each time it is transmitted over the Internet.</p>

<p> According to an embodiment of the present invention, a method of ordering an item from a client system and a system thereof, specifically, a gift shipping method and a system thereof are provided. The client system is given an ID (identifier) that identifies the customer. The client system displays information that identifies the item and displays actions that the buyer is forced to take to order the identified item (for example, a single action, such as clicking a mouse button). When the displayed action is performed, the client system responds by sending a request to the server system to order the given ID and the identified item. The server system uses that ID to identify the additional information needed to generate the order for the item and then generate the order.</p><p> The server system uses various computer systems to receive and store additional information about the customer so that the server system can generate the order. The server system stores the additional information it receives in association with the customer's ID and provides that ID to the client system. When requested by the client system, the server system provides the requesting client system with information describing the item. When the server system receives a request from the client system, the server system combines the additional information stored in association with the ID contained in the request to place an order for the item.</p><p> The present invention provides a method and system for ordering items in a single action in a client / server environment. The single-action ordering system of the present invention reduces the number of buyer interactions required to place an order and reduces the amount of sensitive information transmitted between the client and server systems. Reduce. In one embodiment of the invention, the server system assigns a unique client ID to each client system. The server system also stores buyer-specific order information for various potential buyers. This buyer-specific order information may have been collected from previous orders placed by the buyer. The server system maps each client ID to potential buyers who may place orders using that client system. The server system can also map these client IDs to the last purchaser who placed the order using that client system. When a buyer needs to place an order, the buyer uses the client system to send a request for information describing the item to be ordered along with the client ID. The server system determines if the client ID of that client system is mapped to the purchaser. If it determines that it is mapped, the server system is enabled for a single action order for that purchaser on that client system. ) To determine if it is. If permitted, the server system sends the requested information (eg, through a web page) to the client computer system along with instructions for a single action to be taken to place an order for the item. When single-action orders are allowed, the buyer can simply perform a single action (for example, click a mouse button) to order an item. When the buyer performs the single action, the client system notifies the server system. The notified server system completes the order by adding the buyer's purchaser-specific order information mapped to its client ID to the item order information (eg, product ID and quantity). Therefore, when the description of an item is displayed, the purchaser can place an order to purchase the item simply by taking a single action. Further, since the purchaser-specific order information already stored on the server system side is specified by the client ID, it is not necessary to transmit such sensitive information via the Internet or other communication medium.</p>

<figref num="1">It is a figure which shows the single action order in one Embodiment of this invention.</figref><figref num="2">It is a figure which shows the single action order in one Embodiment of this invention.</figref><figref num="3">It is a figure which shows the single action order in one Embodiment of this invention.</figref><figref num="4">It is a block diagram which shows the embodiment of this invention.</figref><figref num="5">It is a flow diagram which shows the routine which allows a single action order for a customer.</figref><figref num="6">It is a flow diagram which shows the routine which generates the Web page which allows a single action order.</figref><figref num="7">It is a flow diagram which shows the routine which processes a single action order.</figref><figref num="8">It is a flow diagram which shows the routine which generates a single action order summary Web page.</figref><figref num="9">It is a flow diagram which shows the routine which realizes the promotion order selection algorithm.</figref><figref num="10">It is a figure which shows the hierarchical data input mechanism in one Embodiment of this invention.</figref><figref num="11">It is a figure which shows the hierarchical data input mechanism in one Embodiment of this invention.</figref><figref num="12">It is a figure which shows the hierarchical data input mechanism in one Embodiment of this invention.</figref><figref num="13">It is a figure which shows the method of giving an item as a gift to one or more recipients using a single action.</figref><figref num="14">It is a figure which shows the method of giving an item as a gift to one or more recipients using a single action.</figref><figref num="15">It is a figure which shows the grid for creating a group and inputting the identification information of the recipient associated with the group.</figref><figref num="16">It is a flow chart which shows the overall flow of a gift delivery system.</figref><figref num="17">It is a block diagram which shows the component of a gift shipping system.</figref><figref num="18">It is a state diagram showing various states of a gift order.</figref><figref num="19">It is a flow diagram which shows the routine which controls the reception of a gift order.</figref><figref num="20">FIG. 6 is a block diagram showing a routine that controls an attempt to make an initial contact with a recipient.</figref><figref num="21">It is a flow chart which shows the routine which controls the processing of the first voice telephone contact.</figref><figref num="22">It is a flow chart which shows the routine which controls the processing of the first response.</figref><figref num="23">It is a flow diagram which shows the routine which controls the collection of additional contact information.</figref><figref num="24">It is a flow chart which shows the routine which controls the verification of shipping information.</figref>

1 to 3 are diagrams showing a single action order according to an embodiment of the present invention. FIG. 1 is a diagram showing a display of a Web page describing items that can be ordered. This example web page was sent from the server system to the client system when the buyer requested to review more information about the item. An example of this web page includes a summary description section 101, a shopping cart section 102, a single action order section 103, and a detail description section 104. As those skilled in the art will understand, these various sections can be omitted, sorted and adapted in different ways. In general, it is sufficient for the buyer to know one or more items ordered in a single action or the single action required to place an order. The summary and detail sections contain information that identifies and describes one or more items that can be ordered. The Shoppink Cart section allows you to add the described items to the Shoppink Cart as before. The server system adds summary, detail, and shopping cart sections to each web page for orderable items. However, the server system adds a single-action order section only when the single-action order is allowed to the purchaser on its client system (as will be understood by those skilled in the art). , A single web page on the server system can contain all sections, but a single action order section can be selectively included or excluded before sending the web page to the client system. It is possible.). With this single action order section, the buyer can single-click (1-click) the mouse button. You can order by specifying the item described by just doing). When the buyer clicks the mouse button, the item is ordered if the buyer has not taken any action to change the order at that time. The single action order section contains a single action order button 103a, a buyer ID subsection 103b, and a single action order information subsections 103c and 103d. The Buyer Information subsection displays enough information for the Buyer to verify that the server system correctly recognized the Buyer. To reduce the likelihood that sensitive information will be intercepted, the server system will only send enough information for the purchaser to be confident that the server system has correctly identified the purchaser, and will intercept the person. Do not send information that is convenient for you. The additional information subsection allows the purchaser to get various settings and to get more information about single action orders. If the buyer does not want to verify the shipping address, the buyer can choose the "check shipping address" label. When selected, the server system requires the user to "log in" so that the shipping information is displayed or changed after the purchaser has been verified to be who he or she is. The server system then sends a web page to the client system so that the shipping address can be displayed or changed. In this way, sending sensitive shipping addresses is prevented unless requested by a verified purchaser. ) , And allow the shipping information to be displayed or changed after the purchaser has been verified to be who he or she is. The server system then sends a web page to the client system so that the shipping address can be displayed or changed. In this way, sending sensitive shipping addresses is prevented unless requested by a verified purchaser.

When the buyer selects the single-action order button, the client system sends a message to the server system requesting that the displayed item be ordered. When the server system processes the message, the server system provides the client system with a new web page confirming receipt of the single-action order. FIG. 2 shows a display of a web page confirming a single action order. This confirmation web page contains much the same information as the item description web page (see Figure 1), except that the order confirmation section 105 appears at the top of the web page. The order confirmation section confirms that the order has been placed and gives the buyer the opportunity to review and modify the single action order. Apart from the above, the confirmation web page can be the same as the item description web page (see Figure 1), except that the single action order button is replaced with an order confirmation message.

Single-action orders are not currently allowed on the client system, but if allowed, the server system will replace the single-action order button 103a with a single-action order allow button. , Can generate the same web page as in Figure 1. Such a replace button can include text indicating that a single action order is allowed when the buyer clicks the button. When the buyer clicks this button, the server system will send and display the Web page shown in Figure 1. A single action order can be granted whenever the server system stores sufficient buyer-specific order information for the client system to complete the single action order. If the server system does not have enough information, when the purchaser selects the single action button, the server system can provide a web page to collect the additional information it needs. The server system requires the purchaser to "log in" to allow single-action orders after the purchaser has been verified to be who he or she is.

To minimize shipping costs and buyer confusion, the server system can combine various single-action orders into multi-item orders. For example, if a buyer orders an item using a single action order and then orders another item using a single action order 5 minutes later, these orders are cost-effectively single. It will be combined with the order and shipped. The server system combines single-action orders when the expected shipping dates are similar. For example, if one item can be shipped immediately (in stock) and the other item can be shipped one day later, the two single action orders can be cost-effectively combined. However, if the other item can only be shipped after 2 weeks, the two single item orders will not be combined. Figure 3 shows a display of a web page showing four single-action orders combined into two separate multi-item orders based on whether the item is shipable (in stock) . Order information 106 indicates that item 1 and item 2 are combined into one order because they can be shipped within 3 days. Order information 107 indicates that item 3 and item 4 cannot be shipped within a week and are therefore combined into separate orders. In one embodiment of the invention, the server system can combine single action orders placed within a time period (eg, 90 minutes). The server system can also combine or split orders when the order is due to be shipped, based on whether the ordered item is currently available for shipping. This delay in changing an order is called "expedited order selection" or "express order selection", which will be described in detail below.

FIG. 4 is a block diagram showing an embodiment of the present invention. This embodiment is the World Wide Web. ) Is used to support single action orders over the internet. The server system 210 includes a server engine 211, a client ID / customer table 212, various web pages 213, a customer database 214, an order database 215, and an inventory database 216. The server engine receives an HTTP request to access a web page identified by a URL and serves the web page to various client systems. Such an HTTP request can indicate that the purchaser has performed a single action and placed a single action order. The customer database contains information about various buyers or potential buyers. The customer information includes purchaser-specific order information such as the name of the customer, invoicing information, and shipping information. The order database 215 contains an entry for each order that has not yet been shipped to the buyer. Inventory database 216 contains a description of various items that can be ordered. The client ID / customer table 212 associates each client ID, which is a globally unique identifier that uniquely identifies a client system, with the customer that was last associated with that client system. Contains the mapping. The client system 220 has a browser 221 and an assigned client ID 222. This client ID is stored in a file named "cookie". According to one embodiment, the server system assigns a client ID only once when the client system first interacts with the server system and sends it to the client system. From then on, the client system assigns its client ID to every message sent to the server system, allowing the server system to identify the source of the message. Server system The client system interacts by exchanging information via communication link 230. The communication link also includes transmission using the Internet.

As will be appreciated by those skilled in the art, the single action ordering method can be used in a variety of environments other than the Internet. For example, a single action order can also be used in an email environment, where the item is described in an email message with instructions for the single action to be taken to place the item's order. ing. It is also possible to use a variety of communication channels, such as local area networks, wide area networks, or point-to-point (two-point) dial-up connections. The server system can also consist of any combination of hardware or software that can generate orders in response to a single action being performed. The client system can consist of any combination of hardware or software that can interact with the server system. These systems can also include television-based systems through which orders can be placed, or a variety of other consumer products.

FIG. 5 is a flow diagram showing a routine that allows a single action order for a customer. In order to allow a single action order, the server system must have information about the customer that corresponds to the purchaser-specific order information. The server system can obtain this information in various ways. First, the server system can ask the customer if he wants to allow single-action orders. If desired, the server system can use a web page to request buyer-specific order information from the customer. Second, the server system can also store buyer-specific order information collected when the order is placed in the traditional way. The server system can automatically accept single-action orders or with the consent of the customer. In step 301, the server system looks up the client ID sent by the client system. At step 302, the server system updates the client ID / customer ID table to indicate that the generated client ID is associated with that customer. At step 303, the server system sets a flag indicating that single action orders are allowed with a combination of its client ID and its customer. This flag can be stored in the client ID / customer table. At step 304, the server system provides the confirmation web page to the client system. The next time the buyer attempts to order an item, the client system provides its client ID to the server system. If a single action order is allowed to the purchaser, the server system assumes that the purchaser is the customer associated with that client ID in the client ID / customer table. Therefore, the purchaser should go to the server system if someone else may use the same client system.

FIG. 6 is a flow diagram showing a routine for generating a Web page when a single action order is allowed. When a single-action order is allowed, the server system will continue to generate a web page describing the item and then add a single-action order section. In one embodiment, the server system adds partial purchaser specific order information to this section. This information includes the name of the customer, another name for the shipping address chosen by the buyer (moniker). ) (For example, "at home"), and the last 5 digits of the credit card number or the nickname chosen by the buyer. This partial information should be minimal enough to let the buyer know if the server system is using the correct buyer-specific ordering information. At step 401, the server system generates a standard shopping cart type web page for the item. At step 402, if the single action order flag is set for the client ID / customer combination, the server system proceeds to step 403, otherwise exits. At step 403, the server system adds a single action section to the web page and exits.

FIG. 7 is a flow diagram showing a routine for processing a single action order. When the buyer performs the single action required to place the order, the client system notifies the server system. The server system then completes the order by combining the customer-specific order information associated with the client system with the item order information. Single-action orders can be combined with other single-action orders or, in some cases, with traditionally placed orders to reduce shipping costs. In one embodiment, single action orders can be combined when they are placed against each other within a period of time (eg, 90 minutes). This routine shows how single-action orders are combined into short-term orders (eg, which can be shipped within a week) and long-term orders (eg, which can be shipped after a week). .. As will be appreciated by those skilled in the art, single action orders can be combined in various ways based on other factors such as size of shipment and medium-term availability. At step 501, if the item is scheduled to be shipped in the short term, the server system goes to step 502, otherwise it goes to step 505. At step 502, if the short-term order has already been opened for the purchaser, the server system goes to step 504, otherwise it goes to step 503. At step 503, the server system creates a short-term order for the buyer. At step 504, the server system adds the item to the short-term order and proceeds to step 508. At step 505, if the long-term order has already been opened for the purchaser, the server system goes to step 507, otherwise it goes to step 506. At step 506, the server system creates a long-term order for the buyer. At step 507, the server system adds the item to the long-term order. At step 508, the server system generates a confirmation and then

FIG. 8 is a flow diagram showing a routine that generates a single-action order summary Web page. This web page (eg, Figure 3) gives the user the opportunity to review and modify short-term and long-term single-action orders. At step 601, the server system adds standard single-action order information to the web page. If the short-term order is open in step 602, the server system adds the short-term order to the web page in step 603. If the long-term order is open in step 604, the server system adds the long-term order information to the web page in step 605 and completes.

FIG. 9 is a flow diagram showing a routine that implements the promotion order selection algorithm. The goal of the accelerated order selection algorithm is to minimize the number of orders sent to each destination and reduce shipping costs. The destination can be a combination of a particular shipping address and a particular purchaser's billing statement. Orders sent to the same destination are called "sibling orders". This algorithm consists of two stages. In the first stage, the algorithm schedules the shipment of orders to destinations where all sibling orders are satisfied. An order is when all items in the order are currently in inventory (that is, available). ) When) is satisfied and can be shipped. For each group of sibling orders, the algorithm combines these sibling orders into a single combined order and schedules only one order to be shipped to each destination. In the second stage, the algorithm joins and schedules a group of sibling orders that are either partially unfilled or partially filled. The algorithm can split each partially filled sibling order into a filled sibling order and a completely unfilled sibling order. The algorithm then combines all the filled sibling orders into a single combined order and schedules the shipment of that combined order. If there is only one sibling order in any group and the order is partially satisfied, the algorithm according to one embodiment will place the order to prevent extra shipments to that destination. Do not divide.

In the second stage, the algorithm is the next fulfillment time for an item in the group. ) Can be used to select and schedule groups of sibling orders. The next time a sibling order group is filled is the minimum expected time that items in that sibling order group will be filled. For example, if a sibling order group has some unsatisfied items that are expected to be filled within the range of 3 to 14 days, then the next time for that group to be filled is 3 days. Become. The algorithm starts by first scheduling the sibling order group that will be filled the longest next time. For example, if there are 6 groups and each next time is filled with 3, 5, 7, 10, 11, and 14 days, the algorithm will first fill the next time with 14 days. Select and schedule a sibling order within, then select and schedule a group whose next time to be filled is 11 days, and so on. By delaying the schedule for the next less-filled group, the algorithm increases the chances that additional items will be available for shipment (due to the shorter next fill) and will be combined with the scheduled order. To do.

Steps 701 to 703 show the first stage of the promotion order selection algorithm, and steps 704 to 706 show the second stage of the promotion order selection algorithm. In steps 701-703, the algorithm goes into a loop, selects the group in which all sibling orders are satisfied, and combines the orders. At step 701, the algorithm selects the group with all sibling orders that are then satisfied. If all such groups have already been selected in step 703, the algorithm proceeds to the second stage in step 704. Otherwise the algorithm goes to step 703. At step 703, the algorithm joins the orders in the selected group, schedules them, and then loops back to step 701. At step 704, the algorithm selects the next sibling order group that has the longest time to be filled next time. At step 705, the algorithm completes if all such groups have already been selected, otherwise it proceeds to step 706. At step 706, the algorithm joins the orders in the selected group, schedules them, and then loops back to step 704. New orders and new inventories may be received when the accelerated order selection algorithm is running. When such new orders and new inventories are received, the algorithm restarts, scheduling and combining these new orders in a timely manner.

Although the algorithm has been described as consisting of two stages, it is possible to implement the algorithm in an increment manner so that the first and second stages are evaluated again after each order is scheduled. As will be appreciated by those skilled in the art, there are other possible combinations of these stages, and even then the basic algorithms represented are the same.

10 to 12 are diagrams showing a hierarchical data input mechanism according to an embodiment of the present invention. When collecting information from a user, a web page typically consists of a long set of data entry fields that do not fit all on the display at the same time. Therefore, the user needs to scroll through the web page to enter information. When the data entry fields do not fit on the display at the same time, it is difficult for the user to have an overall picture of the type and organization of the data they are trying to enter. According to the hierarchical data entry mechanism, the user can understand the overall organization of the data to be entered, even if not all data entry fields fit on the display at the same time. FIG. 10 is a diagram showing the overall format of the sample form entered therein. This sample form contains various sections indicated by the letters A, B, C, and D. When the user selects the Start button, Section A is expanded to include data entry fields for the customer name and address. Figure 11 shows an enlargement of Section A. Since only section A is expanded, the user can see the data entry fields of section A and the summary information of other sections at the same time. The user then enters data in the various data entry fields displayed. After completing the input, the user selects either the "Next" or "Back" button. If you select the "Next" button, section A will be reduced and section B will be expanded so that you can enter financial information. Figure 12 shows an enlargement of Section B. When you select the Back button, Section A shrinks and appears as shown in Figure 10. This reduction and expansion is repeated for each section. If an error is detected while you are entering data, a web page will be generated with an error message near the erroneous data entry field (for example, in the line below). This web page is Displayed by the client system to inform the user of the error. In addition, each of the data "input" fields cannot be edited until the user clicks on the data input field or selects the "edit" button associated with the data input field. This will prevent the user from accidentally modifying the content of the edit field. When a user clicks on a data entry field, a new web page is presented to the user so that they can edit the data associated with that field. When editing is complete, the edited data will be displayed in the Data Input field. As mentioned above, the fields of this form cannot be edited directly, so neither the "named-submit" button nor Java is required. Also, this form is compact because various data entry options (eg radio buttons) appear on new web pages only when you try to edit a field.

According to another embodiment of the present invention, a mechanism for giving a gift to a specific recipient (s) using a single action is provided. When the information describing the item is displayed, the system identifies the recipient and then selects the "GIVE" button to display an instruction to give the item to that particular recipient. If the user has only one recipient to give the gift, the user enters the recipient's identification information, such as an email address. When a user gives a gift to two or more recipients, the user can enter the identification information of each recipient, but in another way, the user identifies each member of the group (ie, the recipient). It is also possible to enter the group name associated with the information. The system uses the identification information to identify the shipping address of the gift. As described in detail below, the system can use various databases to find information about the identified recipient.

13 and 14 are diagrams showing how an item can be given as a gift to one or more recipients using a single action. FIG. 13 is a diagram showing a case where a gift is given to one recipient. Sections 101-104 are the same as those described in Figure 1. The gift giving section 901 includes an instruction subsection 901a, an identifying information subsection 901b, and a single action gift subsection 901c. To give a gift to a recipient, the user enters the recipient's email address in the Identification Subsection 901b, then selects the Single Action Gifts subsection 901c. When the system receives an email address, it uses that email address to find the recipient's shipping address. This will be described in detail below. The system issues an item invoice to the user based on the information stored about the user at the time of the single action order and ships the item to the recipient at the shipping address. As described below, according to this system, the user can specify various types of identification information.

FIG. 14 shows a case where a gift is given to a plurality of recipients. The gift gift section 902 includes an instruction subsection 902a, a group name subsection 902b, and a single action gift subsection 902c. To give a gift to multiple recipients, the user enters the name of the group that identifies the recipient in the group name subsection 902b, then selects the single action gift subsection 902c. The system uses a group name to identify the list of recipients associated with that group name. FIG. 15 is a diagram showing a grid for creating a group and inputting identification information of recipients (that is, members) associated with the group. The user enters the group name in the group name section 1001 and then the information about the recipient in each line of the member information section 1002. The user can enter information about each recipient associated with the group as long as the user knows. For example, a user may enter only an email address for one user and a full name, email address, and shipping address for another recipient. When the system is requested to send a gift to each recipient associated with the group, the system uses the information stored for each recipient to identify additional information needed to ship the gift. .. This will be described below. The system can also store specific additional information for each recipient, so that when another item is subsequently given to that recipient, the additional information needed to ship that item is instantly available. You can search. Alternatively, a single address book for the user that contains as much information about the recipient as possible. You can also save the book). The user specifies a group by pointing to some of the recipients whose addresses are in the address book. Address books make it easier to maintain multiple groups with one or more recipients in common. In addition, the user can provide additional information about the recipient at any time, speeding up the search for sufficient information to ship the item.

According to the present invention, a computer-based method and system that receives a gift order, collects additional shipping information not specified in the gift order, and coordinates the gift shipping by shipping the gift based on the additional shipping information. Is also provided. The gift delivery system, which is an embodiment of the present invention, receives a gift order through a Web page prepared on the WWW. The gift order specifies the gift to be shipped to the recipient. The recipient can be identified by information that does not include the recipient's shipping address. For example, the recipient can be identified solely by contact information such as name and email address or telephone number. The gift shipping system attempts to contact the recipient for sufficient shipping information. If the contact fails, the gift shipping system searches various information databases to identify additional contact information. Once sufficient shipping information is available, the gift will be shipped to the recipient and the gift giver will be notified. However, if sufficient shipping information is not available, the gift giver will be notified that the gift could not be shipped.

FIG. 16 is a flow chart showing the overall flow of the gift shipping system. At step 1101, the gift shipping system receives the gift order from the gift giver. In one embodiment, the order is received by accessing it through a web page, but it can also be received in other modes of communication such as voice telephone calls, postal mail, fax, or email. At step 1102, the gift shipping system attempts to contact the gift recipient. Gift orders can specify recipient contact information, such as the recipient's email address or phone number. Based on the contact information given with the gift order, an attempt will be made to contact the recipient for the first time by email or automatic voice phone call to collect sufficient shipping information. Alternatively, the user can attempt to contact the recipient by voice call. At step 1103, if the first contact is successful, the system proceeds to step 1106, otherwise it proceeds to step 1104. At step 1104, the system attempts to collect additional contact information. The system can use the information given with the gift order to obtain additional contact information from various database sources. For example, the system can use the recipient's name or recipient's email address to access an Internet-based database system. At step 1105, if the system has obtained additional contact information from the additional source above, the system loops back to step 1102 and attempts to contact the recipient using the additional contact information, and so on. If not, the system proceeds to step 1111. At step 1106, the system collects shipping information from successful contacts. For example, if the successful contact is a telephone call, it is preferred that the operator making the telephone call enter the shipping information. If the successful contact is an email exchange, the system receives It is preferable to analyze the response message of the taker and collect shipping information. At step 1107, the system verifies that the shipping information is correct. The system can validate addresses using various databases that contain a list of all correct street addresses. If the shipping information is verified at step 1108, the system proceeds to step 1109, otherwise it proceeds to step 1111. At step 1109, the system sends the gift to the recipient. At step 1110, the system sends an email to the gift giver informing them that the gift has been successfully delivered. In step 1111 if sufficient shipping information cannot be collected or verified that the shipping information is correct, the system will send a message informing you that the gift could not be shipped and was put on hold (eg). Send to gift giver (by email).

In another embodiment (not shown), if the attempt to contact the recipient fails in step 1103, the system will refer to the database and other sources similar to those described below with reference to FIGS. 10-12. Attempts to obtain additional shipping information for the recipient from sources other than the recipient, such as. When the system can obtain sufficient shipping information of the recipient by the above method, it is preferable that the system uses the obtained shipping information to send the gift to the recipient.

FIG. 17 is a block diagram showing the components of the gift shipping system. Computer system 1201 is equipped with a central processing unit, memory, and peripheral devices such as disk drive devices and CD-ROMs. The gift shipping system includes an order entry system 1202 and an order shipping system 1203. The order entry system provides a user interface for gift givers to enter gift orders. The order entry system in one embodiment includes a web page that accesses the gift database 1204. Gift givers use the web page provided to choose which gifts should be sent to the recipient. The gift giver also provides information describing the recipient. The order entry system then stores the order information in the order database 1205. The gift shipping system controls the search for additional shipping information to ensure that gifts are shipped correctly to the recipient. The gift shipping system retrieves information from the order database and attempts to contact the recipient based on the information provided with the gift order. If the recipient cannot be contacted based on that information, the gift shipping system will access other database sources, such as Customer Database 1206 or Internet-based database 1208, to collect additional contact information for the recipient. To do.

FIG. 18 is a state diagram showing various stages of gift ordering. Gift orders are in 6 states: received, response pending, verifying delivery information, collecting additional contact information, on hold, and Scheduled for shipping It is placed in one of the delivery). Initially, when an order is received, the system places the order in the received state 1301. When the system attempts to contact the recipient using the information given by the gift giver, the gift order changes to waiting state 1302. The wait-for-response state indicates that a contact attempt is in progress but no response has yet been received from the recipient. If sufficient response is received from the recipient within the allotted time (eg 24 hours), the gift order changes to shipping information validation state 1303. When in the shipping information verification state, the system attempts to verify that the shipping information is correct. If the shipping address is correct, the gift order enters the shipping scheduled state 1304. If the initial response is inadequate or not received within the allotted time, the system places the gift order in additional contact information gathering state 1305. When in the additional contact information collection state, the system searches for additional information sources to determine additional contact information about the recipient. If additional contact information is found, the system attempts additional contacts and places the gift order in waiting state 1302. On the other hand, if no additional contact information is found, the system puts the gift order in pending state 1308.

In yet another preferred embodiment, if the initial response is inadequate, the system places the gift order in the additional shipping information gathering state (not shown). When in the additional shipping information collection state, the system searches for additional shipping information sources to obtain additional shipping information for the recipient. If the system can obtain sufficient shipping information by the above method, the system places the gift order in the shipping information verification state 1303. Otherwise, the system puts the gift order in pending state 1308.

FIG. 19 is a flow chart showing a routine for controlling the receipt of gift orders. The Gift Order Receiving Routine controls the interaction with gift givers, selects gifts from the gift database, receives information about recipients, receives payments, and stores gift orders in the database. This routine processes gift orders received electronically. It is also possible to develop similar routines for handling other forms of gift order receipt, as will be appreciated by those skilled in the art. At step 1401, the routine receives a request from the gift giver to the recipient electronically through a web page. At step 1402, the routine creates a session with the gift giver. This session will be used to track interactions with gift givers and gift shipping systems. Step 1403 So this routine receives gift selection information. Gift selection information can be selected in response to when a shippable gift is displayed from the gift database. At step 1404, the routine receives recipient contact information from the gift giver. Typical examples of recipient contact information are the recipient's name and email address. At step 1405, the routine receives payment information. This payment information can be credit card, debit card, or electronic money (digital) It can be in electronic form such as cash) or in conventional form such as check or exchange. In the traditional form, the gift order can be placed in an additional state waiting for payment to be received. At step 1406, if the payment is approved, the routine proceeds to step 1408, otherwise the routine notifies the gift giver that the payment has been refused. At step 1408, the routine assigns a gift order tracking number to the gift order. This gift order tracking number is used by the system to identify the gift order during its processing period. At step 1409, the routine stores the gift order information in the gift order database. At step 1410, the routine notifies the gift giver that the gift order has been accepted. At step 1411, the routine ends the session with the gift giver.

FIG. 20 is a block diagram showing a routine that controls an attempt to make an initial contact with a recipient. The first contact is made using the contact information provided by the gift giver, such as an email address or phone number. If not even the first attempt to contact the recipient is possible due to insufficient information, the gift shipping system searches various databases to obtain contact information based on the recipient's name. At step 1501a, if the recipient's email address is given to the gift order, the routine goes to step 1501b, otherwise it goes to step 1502a. At step 1501b, the routine sends an email to the given email address. This email contains information indicating that the gift will be sent to the recipient and requests shipping information for the gift. The email contains a tracking number assigned by the system, so when a response email is received, the gift shipping system can determine which gift order it corresponds to. In step 1502a, if the recipient's phone number is given, the routine proceeds to 1502b, otherwise the routine continues various other attempts to contact the recipient. For example, if a fax number is given, the fax message will be sent to that number. At step 1502b, the routine schedules an initial telephone contact with the recipient. When the first phone contact is made through an automated voice phone system, the message can be left to both the person answering the call and the answering machine. Alternatively, a human operator can make the first voice contact. After the initial contact, the gift order is placed in a waiting state.

FIG. 21 is a flow chart showing a routine for controlling the processing of the first voice telephone contact. This routine can display information for human operators or inform automated operators. At step 1601, if there is an answer to the call, the routine proceeds to step 1602, otherwise the routine leaves the gift order scheduled for the first contact. At step 1602, if the message is left on the human or voicemail system, the routine proceeds to step 1603, otherwise the routine leaves the gift order scheduled for the first contact. At step 1603, if sufficient response is received, the routine proceeds to step 1605, otherwise it proceeds to step 1604. At step 1604, the routine schedules a gift order to search for additional contact information about the recipient. At step 1605, the routine updates the order database with additional information about the recipient. At step 1606, the routine schedules a gift order so that its shipping information is validated and changes its state to shipping information validation.

FIG. 22 is a flow chart showing a routine that controls the processing of the initial response. This initial response can be by email, voice call, or fax message. At step 1701, if the tracking number is included in the response, the routine goes to step 1702, otherwise it goes to step 1704. At step 1702, the routine uses the gift order database to validate the tracking number. If the tracking number is verified in step 1703, the routine goes to step 1706, otherwise it goes to step 1704. At step 1704, the routine attempts to find the tracking number based on the information given in the response. If the tracking number is found in step 1705, the routine goes to step 1706, otherwise it goes to step 1707. At step 1706, if the response contains sufficient shipping information and the gift order can be shipped, the routine proceeds to step 1708, otherwise to step 1707. At step 1707, the routine schedules the order to look up additional shipping information. At step 1708, the routine schedules the order so that its shipping information is validated and changes its state to shipping information validation.

FIG. 23 is a flow diagram showing a routine that controls the collection of additional contact information. This routine searches various database sources based on the information given in the gift order. For example, in step 1801, the routine is Switchboard, Search Internet-based phone and email directories, such as Four11, and Accumail. At step 1802, the routine searches various CD-ROM databases of telephone and email information, such as Select Phone. At step 1803, the routine searches a local database of customer information. A local database of personal information contains information on previous recipients and gift givers. At step 1804, the routine searches various Internet-based search engines, such as Digital Equipmento's Alta Vista and Infoseek's Ultraseek. At step 1805, the routine looks up an email address or phone number to determine the recipient's geographic location. Specifically, the routine is InterNIC Registration Services of Network Services. To find out the domain name registration of the recipient's email address. Alternatively, the routine accesses a standard table of area codes and phone number prefixes to determine the recipient's geographic locale (local). The gift shipping system can use each of these sources of information, a subset of these sources of information, or additional sources of information to seek out additional information. At step 1806, the routine analyzes the search information and determines the information closest to the recipient based on geographic or contextual matching. This analysis can be done electronically or in dialogue with a human operator. At step 1807, a routine displays information to a human operator requesting instructions for further processing. At step 1808, this routine displays information to a human operator and requests instructions for further processing. These instructions could include placing an order on hold because sufficient shipping information was not collected, sending an initial contact to the recipient, or continuing to ship the gift.

FIG. 24 is a flow chart showing a routine that controls the verification of shipping information. The gift shipping system verifies the shipping information to make sure that the gift is sent to a shipping address. At step 1901, the routine automatically checks the validity of the shipping information. The routine uses the database of US Postal Service addresses to determine if the shipping address is a valid US Postal Service address. At step 1902, if the address is valid, the routine goes to step 1906, otherwise it goes to step 1903. At step 1903, the routine requires the human operator to verify the address manually. At step 1904, if the operator manually verifies the address is correct, the routine goes to step 1906, otherwise it goes to step 1905. At step 1905, the routine notifies the gift giver that the order is not fulfilled and puts the order on hold. At step 1906, the routine schedules the gift to be shipped and notifies the gift giver to that effect.

Although the present invention has been described above by showing various embodiments, the present invention is not limited to these embodiments. Various modifications and improvements are possible within the spirit of the invention, as will be appreciated by those skilled in the art. For example, a server system can map a client ID to multiple customers who have recently used the client system. A server system can then be used to indicate that the user is himself, preferably by selecting one of these mappings based on the display of partial purchaser-specific order information. You can also place orders using a variety of different single actions. For example, a voice command tells the buyer, a key is pressed by the buyer, a button on the television remote control device is pressed by the buyer, or a selection is made using one of the pointing devices. It is possible for the purchaser to do it. Even if multiple physical movements of the purchaser (for example, moving the mouse so that the mouse pointer is over the button) may be required prior to the single action, the single action here Is generally a single event that directs an order to be placed and is received by the client system. Finally, the purchaser can also be identified by a unique customer ID given by the customer when the customer accesses the server system and sent to the server system with each message. This customer ID can also be permanently stored on the client system side, eliminating the need for the purchaser to re-enter their customer ID each time they access it. The scope of the present invention is determined only based on the description of the claims.

210 server system 211 server engine 212 Client ID / Customer Table 213 web page 214 Castoma Database 215 Order database 216 Inventory database 220 Client system 221 browser 222 Client ID 230 communication link 901 Gift Gifts Section 901a Instruction subsection 901b Identification subsection 901c Single Action Gifts Subsection 902 Gift Gifts Section 902a Instruction subsection 902b Group name subsection 902c Single Action Gifts Subsection 1001 Group name section 1002 Member information section 1201 computer system 1202 Order entry system 1203 Order shipping system 1204 Gift Database 1205 order database 1206 Customer database 1208 Internet-based database 1301 Received state 1302 Response waiting state 1303 Shipping Information Verification State 1304 Shipping Scheduled State 1305 Additional contact information gathering state 1308 Pending state