PERSONALIZING DELIVERY CHOICES

Systems and methods to personalize delivery choices are described. A buyer may make a delivery request; the delivery request may include transaction information. Available delivery choices may be identified based on the transaction information. Delivery analytics data associated with the transaction information may be retrieved from at least one application server. Personalized delivery choices from the identified available delivery choices may be determined based on an analysis of the delivery analytics data. The buyer may be recommended the personalized delivery choices.

TECHNICAL FIELD

Embodiments of the present invention relate generally to systems and methods for personalizing delivery choices based on information from various sources.

BACKGROUND

Modern delivery services offer a plethora of delivery choices. For example, same day delivery, locker-based pickup, air, ground, charter, hand-carry, dedicated courier, alternative delivery services, and many others. The distinction between these choices can be difficult to discern for a typical consumer. As the number of choices increases, the difficulty of making a choice often increases. Effective commercial enterprises try to avoid confusing or overloading consumers. Accordingly, it would be advantageous to develop a system and methods for providing personalized delivery choices from amongst a wide range of delivery choices.

DETAILED DESCRIPTION

Example methods and systems for personalizing delivery choices are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of example embodiments. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details.

Embodiments described herein may include personalizing delivery choices based on information from various sources. Given a wide range of delivery choices, delivery choices that are personalized to a buyer are determined based on information from various sources. The sources may include third party servers, for example. The information used to determine the personalized delivery choices may include, for example, buyer information, seller information, item information, and other information. For example, if the buyer has favored faster delivery choices in the past, the personalized delivery choices may include speedier delivery choices. Example information that may be used in determining the personalized delivery choices may include age, region, shipping origin, shipping destination, socioeconomic status, prior delivery choice selections, information from the buyer's social network presence, seller location, buyer location, delivery routes, item origination location, multiple item origination locations (e.g., seller may have the item in multiple locations), shipping cost, whether the item to be delivered is perishable, whether the delivery is time sensitive, weather conditions, current closures, current shipping volumes, shipping delays, power outages, geopolitical events, fuel shortages, strikes, other buyer delivery preferences from the same region as the buyer, and other information. This information may be referred to as delivery analytics data and includes a wide range of information from various sources. The delivery analytics data may be analyzed and used in a number of different schemes to determine personalized delivery choices.

In some embodiments, an item may have multiple origination locations. For example, a seller may have a particular item in more than one location, or multiple sellers may have the particular item. In this example, the personalized delivery choices may be determined based multiple item origination locations that may include multiple sellers.

With reference toFIG. 1, an example embodiment of a high-level client-server-based network architecture100to enable personalizing delivery choices is shown. A networked system102, in the example forms of a network-based marketplace or publication system, provides server-side functionality, via a network104(e.g., the Internet or Wide Area Network (WAN)) to one or more client devices110and112.FIG. 1illustrates, for example, a web client106(e.g., a browser, such as the Internet Explorer browser developed by Microsoft Corporation of Redmond, Wash. State), and a programmatic client108executing on respective client devices110and112.

The client devices110and112may comprise a mobile phone, desktop computer, laptop, or any other communication device that a user may utilize to access the networked system102. In some embodiments, the client device110may comprise a display module (not shown) to display information (e.g., in the form of user interfaces). In further embodiments, the client device110may comprise one or more of a touch screen, accelerometer, gyroscope, camera, microphone, and GPS device. The client devices110and112may be a device of a user, which is used to perform a transaction involving digital goods within the networked system102. In one embodiment, the networked system102is a network-based marketplace that manages digital goods, publishes publications comprising item listings of products available on the network-based marketplace, and manages payments for these marketplace transactions.

An Application Program Interface (API) server114and a web server116are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers118. The application servers118may host one or more marketplace systems120, payment systems122, and delivery personalization systems123each of which may comprise one or more modules or applications and each of which may be embodied as hardware, software, firmware, or any combination thereof. The application servers118are, in turn, shown to be coupled to one or more databases servers124that facilitate access to one or more to one or more information storage repositories or database(s)126. In one embodiment, the databases126are storage devices that store information to be posted (e.g., publications or listings) to the publication system120. The databases126may also store digital goods information in accordance with example embodiments.

In an example embodiment, the application servers118are coupled to one or more delivery analytics database(s)127. The delivery analytics databases127may store delivery analytic information used to personalize delivery choices. For example, past delivery choice selections and information associated with the past delivery choice selections may be stored and retrieved from delivery analytics databases127.

The marketplace system120may provide a number of marketplace functions and services to users that access the networked system102. The payment system122may likewise provide a number of payment services and functions to users. The payment system122may allow users to accumulate value (e.g., in a commercial currency, such as the U.S. dollar, or a proprietary currency, such as “points”) in accounts, and then later to redeem the accumulated value for products (e.g., goods or services) that are made available via the marketplace system120. The delivery personalization system123may provide functionality for personalizing delivery choices using information from various sources. While the marketplace, payment, and delivery personalization systems120,122, and123are shown inFIG. 1to both form part of the networked system102, it will be appreciated that, in alternative embodiments, the payment system122may form part of a payment service that is separate and distinct from the networked system102. Similarly, it is to be appreciated that delivery personalization system123may also be separate and distinct from the networked system102.

Further, while the system100shown inFIG. 1employs a client-server architecture, the present invention is of course not limited to such an architecture, and could equally well find application in a distributed, or peer-to-peer, architecture system, for example. The various marketplace, payment, and delivery personalization systems120,122, and123could also be implemented as standalone software programs, which do not necessarily have networking capabilities.

The web client106accesses the various marketplace, payment, and delivery personalization systems120,122, and123via the web interface supported by the web server116. Similarly, the programmatic client108accesses the various services and functions provided by the marketplace, payment, and delivery personalization systems120,122, and123via the programmatic interface provided by the API server114. The programmatic client108may, for example, be a seller application (e.g., the TurboLister application developed by eBay Inc., of San Jose, Calif.) to enable sellers to author and manage listings on the networked system102in an off-line manner, and to perform batch-mode communications between the programmatic client108and the networked system102.

FIG. 1also illustrates a third party application128, executing on a third party server machine130, as having programmatic access to the networked system102via the programmatic interface provided by the API server114. For example, the third party application128may, utilizing information retrieved from the networked system102, support one or more features or functions on a website hosted by the third party. The third party website may, for example, provide one or more promotional, marketplace or payment functions that are supported by the relevant applications of the networked system102.

Delivery service server(s)140may be coupled to network104in an example embodiment. The delivery service servers140may provide delivery service information and may receive requests to initiate delivery of one or more items. For example, the delivery personalization system123may communicate with the delivery service servers140via network104to retrieve delivery information or request delivery of items.

FIG. 2is a block diagram illustrating multiple applications120and122that, in one example embodiment, are provided as part of the networked system102. The applications120may be hosted on dedicated or shared server machines (not shown) that are communicatively coupled to enable communications between server machines. The applications themselves are communicatively coupled (e.g., via appropriate interfaces) to each other and to various data sources, so as to allow information to be passed between the applications or so as to allow the applications to share and access common data. The applications may furthermore access server one or more databases126via the database servers128.

The networked system102may provide a number of publishing, listing and price-setting mechanisms whereby a seller may list (or publish information concerning) goods or services for sale, a buyer can express interest in or indicate a desire to purchase such goods or services, and a price can be set for a transaction pertaining to the goods or services. To this end, the marketplace system120is shown to include at least one publication application200and one or more auction applications202which support auction-format listing and price setting mechanisms (e.g., English, Dutch, Vickrey, Chinese, Double, Reverse auctions etc.). The various auction applications202may also provide a number of features in support of such auction-format listings, such as a reserve price feature whereby a seller may specify a reserve price in connection with a listing and a proxy-bidding feature whereby a bidder may invoke automated proxy bidding.

A number of fixed-price applications204support fixed-price listing formats (e.g., the traditional classified advertisement-type listing or a catalogue listing) and buyout-type listings. Specifically, buyout-type listings (e.g., including the Buy-It-Now (BIN) technology developed by eBay Inc., of San Jose, California) may be offered in conjunction with auction-format listings, and allow a buyer to purchase goods or services, which are also being offered for sale via an auction, for a fixed-price that is typically higher than the starting price of the auction.

Store applications206allow a seller to group listings within a “virtual” store, which may be branded and otherwise personalized by and for the seller. Such a virtual store may also offer promotions, incentives and features that are specific and personalized to a relevant seller.

Reputation applications208allow users that transact, utilizing the networked system102, to establish, build and maintain reputations, which may be made available and published to potential trading partners. Consider that where, for example, the networked system102supports person-to-person trading, users may otherwise have no history or other reference information whereby the trustworthiness and credibility of potential trading partners may be assessed. The reputation applications208allow a user, for example through feedback provided by other transaction partners, to establish a reputation within the networked system102over time. Other potential trading partners may then reference such a reputation for the purposes of assessing credibility and trustworthiness.

Personalization applications210allow users of the networked system102to personalize various aspects of their interactions with the networked system102. For example a user may, utilizing an appropriate personalization application210, create a personalized reference page at which information regarding transactions to which the user is (or has been) a party may be viewed. Further, a personalization application210may enable a user to personalize listings and other aspects of their interactions with the networked system102and other parties.

The networked system102may support a number of marketplaces that are customized, for example, for specific geographic regions. A version of the networked system102may be customized for the United Kingdom, whereas another version of the networked system102may be customized for the United States. Each of these versions may operate as an independent marketplace, or may be customized (or internationalized) presentations of a common underlying marketplace. The networked system102may accordingly include a number of internationalization applications212that customize information (and/or the presentation of information) by the networked system102according to predetermined criteria (e.g., geographic, demographic or marketplace criteria). For example, the internationalization applications212may be used to support the customization of information for a number of regional websites that are operated by the networked system102and that are accessible via respective web servers116.

Navigation of the networked system102may be facilitated by one or more navigation applications214. For example, a search application (as an example of a navigation application) may enable key word searches of listings published via the networked system102. A browser application may allow users to browse various category, catalogue, or inventory data structures according to which listings may be classified within the networked system102. Various other navigation applications may be provided to supplement the search and browsing applications.

In order to make listings, available via the networked system102, as visually informing and attractive as possible, the marketplace system120may include one or more imaging applications216utilizing which users may upload images for inclusion within listings. An imaging application216also operates to incorporate images within viewed listings. The imaging applications216may also support one or more promotional features, such as image galleries that are presented to potential buyers. For example, sellers may pay an additional fee to have an image included within a gallery of images for promoted items.

Listing creation applications218allow sellers conveniently to author listings pertaining to goods or services that they wish to transact via the networked system102, and listing management applications220allow sellers to manage such listings. Specifically, where a particular seller has authored and/or published a large number of listings, the management of such listings may present a challenge. The listing management applications220provide a number of features (e.g., auto-relisting, inventory level monitors, etc.) to assist the seller in managing such listings. One or more post-listing management applications222also assist sellers with a number of activities that typically occur post-listing. For example, upon completion of an auction facilitated by one or more auction applications202, a seller may wish to leave feedback regarding a particular buyer. To this end, a post-listing management application222may provide an interface to one or more reputation applications208, so as to allow the seller conveniently to provide feedback regarding multiple buyers to the reputation applications208.

Dispute resolution applications224provide mechanisms whereby disputes arising between transacting parties may be resolved. For example, the dispute resolution applications224may provide guided procedures whereby the parties are guided through a number of steps in an attempt to settle a dispute. In the event that the dispute cannot be settled via the guided procedures, the dispute may be escalated to a third party mediator or arbitrator.

A number of fraud prevention applications226implement fraud detection and prevention mechanisms to reduce the occurrence of fraud within the networked system102.

Messaging applications228are responsible for the generation and delivery of messages to users of the networked system102, such messages for example advising users regarding the status of listings at the networked system102(e.g., providing “outbid” notices to bidders during an auction process or to provide promotional and merchandising information to users). Respective messaging applications228may utilize any one of a number of message delivery networks and platforms to deliver messages to users. For example, messaging applications228may deliver electronic mail (e-mail), instant message (IM), Short Message Service (SMS), text, facsimile, or voice (e.g., Voice over IP (VoIP)) messages via the wired (e.g., the Internet), Plain Old Telephone Service (POTS), or wireless (e.g., mobile, cellular, WiFi, WiMAX) networks.

Merchandising applications230support various merchandising functions that are made available to sellers to enable sellers to increase sales via the networked system102. The merchandising applications230also operate the various merchandising features that may be invoked by sellers, and may monitor and track the success of merchandising strategies employed by sellers.

Social networking applications260may support various social networking functions that are made available in various embodiments. The social networking functions may include the retrieval or submission of data to and from social networking servers.

The networked system102itself, or one or more parties that transact via the networked system102, may operate loyalty programs that are supported by one or more loyalty/promotions applications232. For example, a buyer may earn loyalty or promotions points for each transaction established and/or concluded with a particular seller, and be offered a reward for which accumulated loyalty points can be redeemed.

FIG. 3is a block diagram illustrating social network information261that may be used by social network applications260ofFIG. 2, according to an embodiment, at the network-based social publisher102ofFIG. 1. The social network application(s)260is shown to include social platform user profile information261that stores user profile information262for users of the network-based publisher102. The user profile information262may include information related to the user and specifically may include relationship information265and block information266. The relationship information265may store a predetermined relationship between the user associated with the user profile information262and other users on the network-based publisher102. For example, a first user may be designated a “friend,” or “favorite friend,” etc. with a second user, the first user associated with the user profile information262and the respective designations associated with increasing levels of disclosure between the first user and second user. The block information266may store a configured preference of the user to block the addition of an item by other users to a watch list associated with the user.

FIG. 4is a block diagram illustrating a mobile device400, according to an example embodiment. The mobile device400may include a processor410. The processor410may be any of a variety of different types of commercially available processors suitable for mobile devices (e.g., an XScale architecture microprocessor, a Microprocessor without Interlocked Pipeline Stages (MIPS) architecture processor, or another type of processor). A memory420, such as a Random Access Memory (RAM), a Flash memory, or other type of memory, is typically accessible to the processor. The memory420may be adapted to store an operating system (OS)430, as well as application programs440, such as a mobile location enabled application that may provide LBSs to a user. The processor410may be coupled, either directly or via appropriate intermediary hardware, to a display450and to one or more input/output (I/O) devices460, such as a keypad, a touch panel sensor, a microphone, and the like. Similarly, in some embodiments, the processor410may be coupled to a transceiver470that interfaces with an antenna490. The transceiver470may be configured to both transmit and receive cellular network signals, wireless data signals, or other types of signals via the antenna490, depending on the nature of the mobile device400. In this manner, a connection with a network such as network104ofFIG. 1may be established. Further, in some configurations, a GPS receiver480may also make use of the antenna490to receive GPS signals. Additional details regarding providing and receiving location-based goods and services using a GPS system can be found in U.S. patent application Ser. No. 13/340,626 entitled “Methods and Systems for Using a Co-Located Group as an Authorization Mechanisms,” assigned to the assignee of the instant application, which application is hereby incorporated by reference in its entirety.

FIG. 5is a block diagram of the delivery personalization system123, which may determine personalized delivery choices for a buyer using information from various sources. In one embodiment, the delivery personalization system123includes a user interface module510, a network communication module520, a transaction module530, a buyer preferences module540, a delivery analytics data module550, and a delivery analysis module560. In further embodiments, the delivery analytics data module550may include a web services module552, a database module554, and a location module556. Other modules not pertinent to example embodiments may also be included, but are not shown.

The user interface module510may provide various user interface functionality that may present and receive information from the buyer. For example, the user interface module510may present a delivery choice interface to the buyer that displays various delivery choices and may receive a delivery choice selection from the buyer. The user interface module510may also provide a buyer preferences user interface that may receive preferences from the buyer. Information may be presented by a number of means including displaying information (e.g., such as on display450), other visual means, or other device output (e.g., audio, tactile, and so forth). Similarly, information may be received by a number of means including alphanumeric input on a keyboard or other device input (e.g., one or more touch screen, camera, tactile sensors, light sensors, infrared sensors, biometric sensors, microphone, gyroscope, accelerometer, other sensors, and so forth). The user interface module510may provide many other user interfaces to facilitate functionality described herein.

The network communication module520may perform various network communication functions such as communicating with the client devices110and112and servers such as the delivery service servers140, the database servers124and the third party servers130. Network communication may operate over WiFi, Bluetooth, or other means of wired or wireless data transmission.

The transaction module530may receive transaction information and delivery requests from application servers118or client devices110and112, in an example embodiment. In embodiments, the transaction module530may receive a delivery choice selection from the buyer. Furthermore, the transaction module530may communicate with the delivery service servers140to determine available delivery choices based on the transaction information, retrieve delivery choice information, and initiate delivery. The transaction information may comprise seller information, buyer information, item information, and other transaction information. For example, the transaction information may include a time of transaction, a shipping origin, a shipping destination, a buyer identifier, a seller identifier, an item identifier, an item name, a seller name, a buyer name an item model, an item price, an item weight, item dimensions, and so forth. The delivery choice information may include carrier, cost, pickup times, estimated arrival times, packaging information, whether delivery is temperature controlled regions where delivery is available, delivery drop off type, and so forth.

The buyer preferences module540may provide functionality to receive and store buyer delivery preferences. The buyer preferences module540may receive the buyer delivery preferences from the buyer to be stored in delivery analytics databases127, in an example embodiment. For example, the buyer may specify that a low cost delivery choice is preferable for certain items, item types, or all items. In further embodiments, the buyer may specify the buyer delivery preferences for certain items, item types, or all items including the location for delivery, the carrier, faster delivery choices, lower cost delivery choices, safer handling delivery choices, temperature controlled delivery choices, a schedule of available delivery times, a party or parties who may receive the delivery, a pickup location for the delivery, and so forth. In some embodiments, the buyer delivery preferences from other buyers may also be retrieved. For example, all the buyer delivery preferences for other buyers in a particular region may be used to determine a preferable delivery method for the buyer given the buyer's location.

The delivery analytics data module550may retrieve delivery analytics data associated with the transaction information. The delivery analytics data may be retrieved from a plurality sources. For example, the delivery analytics data may be retrieved from the client device110and112, the database servers124, the application servers118, the third party servers130(e.g., social network servers, government servers, commercial servers, or other third party servers), or other sources. The delivery analytics data module550may also store information in delivery analytics databases127. For example, information associate with the transaction, such as the delivery choice selection for a particular item, may be stored in one or more databases such as the delivery analytics databases127.

The delivery analytics data module550may retrieve a buyer profile that is associated with the transaction information, in an example embodiment. The buyer profile may include, for example, age, gender, location, region, employment status, marital status, real-time location, income level, socioeconomic status, prior delivery choice selections, information from the buyer's social network profiles, and so forth. In embodiments, the buyer location may include a plurality of locations. In further embodiments, the buyer location may be a dynamic location (e.g., a location currently being updated by GPS, IP address geolocation, and other geographic services).

In a further embodiment, the delivery analytics data module550may retrieve a seller profile that is associated with the transaction information for the one or more sellers included in the transaction information. The seller profile may include, for example, location, region, packaging type, on-time delivery statistics, other seller statistics, and so forth. In some embodiments, the seller profile information may be associated with one or more sellers (e.g., multiple sellers that are currently selling a particular item). For example, the delivery analytics data may include item locations, delivery route, delivery dates, and shipping cost for items associated with multiple sellers. In this example, the personalized delivery choices may be determined based on the information from multiple sellers (e.g., delivery choices with the fastest delivery across multiple sellers or lowest cost delivery across multiple sellers).

The delivery analytics data module550may retrieve an item profile that is associated with the transaction information for items included in the transaction data, in some embodiments. The item profile may include for example, price, weight, dimensions, whether the item is perishable, whether the item requires time sensitive delivery, whether the item needs to be in a temperature controlled environment, whether the item is sensitive to direct sunlight, packaging material requirements, item origination location, multiple item origination locations (e.g., seller may have the item in multiple locations) and so forth.

In yet another embodiment, the delivery analytics data module550may retrieve a transaction profile that is associated with the transaction information. The transaction profile may include, for example, weather conditions at various locations, current road closures, power outages, shipping delays, current shipping volumes, fuel shortages, strikes, shipping costs, delivery routes and so forth. The information in the transaction profile may be based on the transaction information. For example, the location of the buyer may be used to determine weather conditions at the buyer's location at potential delivery times. In another example, the transaction time may be used as a basis for determining whether current shipping volume is high (e.g., during holiday seasons).

The web services module552may perform various web services functions such as retrieving information from third party servers130and application servers118. Information retrieved by the web services module552may include information in the buyer profile, the seller profile, the item profile, the transaction profile, or other information.

The database module554may communicate with the delivery analytics databases127and other databases to retrieve and store information. For example, the delivery choice selection made by the buyer may be stored in the delivery analytics databases127. Further, other information associated with the delivery choice selection may be stored in the delivery analytics databases127, such as, item, delivery service, time of day, time of week, time of year, and so forth. In further embodiments, other information associated with the buyer, the seller, the item, or other information may be stored or retrieved in the delivery analytics databases127.

The location module556may retrieve various location information associated with the transaction information. Location information of the buyer may be retrieved, for example, using IP address geolocation or from other geographic services. In further embodiments, real-time location information may be retrieved from a buyer device using GPS (e.g., from GPS receiver480) or another location service. Item location (e.g., current location of the item in transit or shipping origin) information may be retrieved from third party servers130, delivery service servers140, or from another source. Similarly, seller location may be retrieved from third party servers130or from another source.

The delivery analysis module560may receive information from various sources and analyze the information to determine personalized delivery choices. The analysis to determine personalized delivery choices may be performed in a variety of ways and using many different pieces of information. Different weights may be given to information in performing the analysis. Various schemes may be employed during the analysis to determine personalized delivery choices.

FIG. 6depicts an example embodiment of coupling between various modules of the delivery personalization system123. The delivery analysis module560may be coupled to the transaction module530, the buyer preferences module540, and the delivery analytics data module550. In an example embodiment, the delivery analysis module560may receive transaction information and available delivery choices from transaction module530, the buyer delivery preferences from the buyer preferences module540, and the delivery analytics data from the delivery analytics data module550.

FIG. 7is a flow diagram illustrating an example method700of personalizing delivery choices. At operation710, the delivery personalization system123may receive the delivery request and the transaction information. In some embodiments, the delivery request may be received from the buyer, the buyer initiating the request from client device110and112or from application servers118.

At operation720, the delivery personalization system123may identify available delivery choices based the transaction information received at operation710. For example, the transaction information may contain the delivery origin and the delivery destination and based on the delivery origin and the delivery destination the available delivery choices may be determined (e.g., a particular origin or destination may not have certain delivery services). In another example, the transaction information may contain item information, which may be used to determine available delivery choices (e.g., same-day delivery may not be available for very large items).

Once the available delivery choices are identified at operation720, the delivery personalization system123may retrieve the delivery analytics data associated with the transaction information from at least one application server at operation730. As detailed above, the delivery analytics data may encompass a wide range of information from a wide range of sources. In one embodiment, prior delivery choice selections may be retrieved for the buyer at operation730.

At operation740, the delivery personalization system123may determine personalized delivery choices by analyzing the delivery analytics data retrieved at operation730as further described inFIGS. 8-11. In an example embodiment, prior delivery choices for the buyer may be used to determine a preferable delivery choice among the available delivery choices for the buyer.

After the personalized delivery choices are determined at operation740, the delivery personalization system123may recommend the personalized delivery choices to the buyer at operation750. The buyer may be recommended fewer choices than all of the available delivery choices. In an embodiment, the personalized delivery choices are ranked by most preferable to least preferable and the buyer may be recommended the delivery choices in a way that emphasizes the more preferable delivery choices. In some embodiments, the remaining available delivery choices may be presented to the buyer in addition to the recommended delivery choices.

At operation760, the delivery personalization system123may receive a delivery choice selection from the buyer. In further embodiments, the delivery choice selection may be store in delivery analytics database127. The delivery choice may be associated with the buyer, the transaction information, and other information.

FIG. 8is an example embodiment of operation740that may analyze the delivery analytics data by evaluating the data against criteria. At operation810, the delivery personalization system123may determine if the information is included in the delivery analytics data. If the information is not in the delivery analytics data, then the delivery choice may simply be included as though no criteria were evaluated. In other embodiments, the delivery choice may not be included. At operation820, the delivery personalization system123may determine if the information meets criteria. Many criterions may be evaluated at operation820. In an example embodiment, if the information meets the criteria, then the delivery choice is included at operation840. Conversely, if the criteria are not met, then the delivery choice is not included at operation830. At operation850, the delivery personalization system123may provide the personalized delivery choices.

In an example embodiment, the information at operation820may be whether the item is temperature sensitive (e.g., some types of perishable items such as fine chocolate) and whether the delivery choice is temperature controlled. In this example, one criterion may be to require a temperature controlled delivery choice for a temperature sensitive item. Information regarding whether the item is temperature sensitive may be contained in the item profile information discussed herein. Information regarding whether the delivery choice may be temperature controlled may be contained in the delivery choice information described herein. In another example embodiment, the information at820may be whether the item to be delivered is time sensitive (e.g., concert tickets that have no value after the concert date). In this example, the one criterion at operation820may require that the delivery choice can complete delivery within a requisite time. Many other criteria and information may be evaluated at operation820to personalize the delivery choices.

In a further example embodiment, the delivery analytics data may include one or more item locations of the item for one or more sellers (e.g., a seller may have a particular item in more than one location). The delivery analytics data may also include delivery route information for each of the item locations. In an embodiment, the personalized delivery choices may be determined based on the item locations and delivery route information. For example, the delivery choices for items that are geographically closer to the buyer location may be preferable or delivery choices associated with items with the shortest delivery route.

In some embodiments, operation740may employ a scheme that incorporates many pieces of information. For example, it may be determined that delivery cost is not important to the buyer and delivery speed and delivery reliability are very important to the buyer. A scheme may be employed that assigns a numerical value to each delivery characteristic of the delivery choice such as speed, reliability, cost, and so forth. Furthermore, a numerical value may be assigned to the importance of the delivery characteristic to the buyer. In this example, delivery speed and delivery reliability may have a higher numerical value than delivery cost. Operation820may then determine if a delivery choice meets the criteria by analyzing the numerical value assigned the delivery choice characteristic and the numerical value assigned to the importance of the delivery characteristic to the buyer. Delivery choices with delivery characteristics that correspond well to important delivery characteristics of the buyer may meet the criteria at operation820. Many other schemes may be employed.

FIG. 9is an example embodiment of operation740that may perform analysis of the delivery analytics data based on prior delivery choice selections of the buyer. At operation910, the delivery personalization system123may receive the transaction information including a buyer (e.g., a buyer name or buyer identifier). As described herein, the transaction information may include item information and buyer information. This information may be utilized in subsequent operations.

At operation920, the delivery personalization system123may retrieve prior delivery choice selections associated with the buyer. For example, the buyer information may be used to retrieve delivery choice selections that were previously stored in delivery analytics databases127. As described herein, the delivery choice selections stored in the delivery analytics databases127may be associated with the transaction information. Thus, the delivery choice selections may be retrieved from the delivery analytics databases127that correspond to the buyer.

At operation930, the delivery personalization system123may provide the personalized delivery choices based on the transaction information and the prior delivery choice selections associated with the buyer. For example, the prior transaction data associated with the delivery choice selections retrieved may be used to determine a preferable delivery choice for the transaction data received at operation910. For instance, the item information in the transaction data may be compared to the item information from the prior transaction data and a preferable delivery choice determined for a particular item. For a concrete example, if a buyer has in the past purchased video games and has frequency chosen the fastest delivery choice when purchasing video games, the buyer may prefer a fast delivery choice when buying a video game. In yet another example, if the buyer has in the past purchased office supplies and frequency chose the least expensive delivery choice, the buyer may prefer less expensive delivery choices when purchasing office supplies.

FIG. 10is an example embodiment that may perform analysis of the delivery analytics data based on delivery choice selections of other buyers. At operation1010, the delivery personalization system123may receive the transaction information. At operation1020, the delivery personalization system123may retrieve the delivery choice selections that are associated with other buyers from, for example, the delivery analytics databases127.

At operation1030, the delivery personalization system123may provide the personalized delivery choices based on the transaction information and the prior delivery choice selections associated with other buyers. For example, the transaction information may contain buyer location as previously described. The buyer location may be used to determine a delivery choice preference for a particular location or region. For instance, if many buyers in a particular region use a particular delivery choice, then that delivery choice may be preferable for the current transaction. For a concrete example, buyers who live in a very rainy region, such as Seattle, may prefer a delivery choice that is door-to-door.

FIG. 11is an example embodiment of operation740that may perform analysis of the delivery analytics data based on the buyer profile. At operation1110, the delivery personalization system123may receive the transaction information and the buyer profile. As described herein, the buyer profile may include information about the buyer such as age, location, prior delivery choice selections, socioeconomic status, income level, and so forth. At operation1130, the delivery personalization system123may provide the personalized delivery choices based on the transaction information and the buyer profile. For example, low-income buyers may prefer less expensive delivery choices compared to high-income buyers.

FIG. 12depicts an example user interface1200displaying example delivery choices to the buyer. The user interface module510may be configured to display the example user interface1200. User interface (UI) element1210may contain a variety of delivery choices. In the example user interface1200, the available delivery choices are displayed. The available delivery choices may be identified at operation720, in an example embodiment. UI element1220depicts a single delivery choice that is not selected. UI element1230depicts a delivery choice that is selected. The buyer may make the delivery choice selection by selecting one of the displayed delivery choices contained in the UI element1210. Many other user interfaces may be employed to display the delivery choices.

FIG. 13depicts an example user interface1300displaying example personalized delivery choices to the buyer. UI element1310may contain the personalized delivery choices. The personalized delivery choices may be determine at operation740from the available delivery choices, in an example embodiment. UI element1320depicts a single personalized delivery choice. UI element1330depicts a personalized delivery choice that is selected. UI element1340may be used to display other available delivery choices. By activating the UI element1340, the UI element1310may contain all available delivery choices or simply a few additional personalized delivery choices. In some embodiments, activating UI element1340may display a user interface similar toFIG. 12, where the available delivery choices are displayed to the buyer. In this example, the buyer may prefer a fast delivery and the delivery choices are personalized to the buyer's preference for speed. Here, faster delivery choices are contained in the UI element1310. Many other user interfaces may be employed to display the personalized delivery choices.

The machine1400includes a processor1402(e.g., a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), or any suitable combination thereof), a main memory1404, and a static memory1406, which are configured to communicate with each other via a bus1408. The machine1400may further include a graphics display1410(e.g., a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)). The machine1400may also include an alphanumeric input device1412(e.g., a keyboard), a cursor control device1414(e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), a storage unit1416, a signal generation device1418(e.g., a speaker), and a network interface device1420.

The storage unit1416includes a machine-readable medium1422on which is stored the instructions1424embodying any one or more of the methodologies or functions described herein. The instructions1424may also reside, completely or at least partially, within the main memory1404, within the processor1402(e.g., within the processor's cache memory), or both, during execution thereof by the machine1400. Accordingly, the main memory1404and the processor1402may be considered as machine-readable media. The instructions1424may be transmitted or received over a network1426via the network interface device1420.