Methods, systems, and computer-readable media for placing orders

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. utility application entitled, “Methods, Systems, and Computer-Readable Media for Placing Orders,” having Ser. No. 11/781,579, filed Jul. 23, 2007, and issued as U.S. Pat. No. 8,103,558, which is entirely incorporated herein by reference.

BACKGROUND

In ordering products and services from vendors, users often are provided with a plurality of options to customize the order. As such, if a user is ordering the products and/or services online, a plurality of web pages may be presented to the user before the order is complete. Similarly, if a user is placing a telephone order, the user may be presented with an Interactive Voice Response (IVR) system with a plurality of options and/or may discuss the order with a representative before placing the order. While these techniques of placing an order may provide convenience in that a user need not drive to a vendor site, place the order, and wait for the goods and/or services, oftentimes the user repeatedly places the same order with a particular vendor. Regardless, oftentimes, the user must still navigate the same web pages, IVR prompts, and/or representative questions. Such a configuration may slow the ordering process, as well as incorporate an unnecessary risk of error in the order.

Thus, a heretofore unaddressed need exists in the industry to address the aforementioned deficiencies and inadequacies.

SUMMARY

Included are embodiments for customized ordering. At least one embodiment of a method includes receiving an indication to send a previously created customized order to a vendor and retrieving at least one component of the customized order according to the indication. Some embodiments include determining the vendor associated with the customized order and sending the at least one component of the customized order to the vendor in a first manner, the vendor being configured to receive the customized order.

Also included are embodiments of a computer readable medium for customized ordering. At least one embodiment includes first receiving logic configured to receive an indication to send a previously created customized order to a vendor and retrieving logic configured to retrieve at least one component of the customized order according to the indication. Some embodiments include first determining logic configured to determine the vendor associated with the customized order and first sending logic configured to send the customized order to the vendor in a first manner, the vendor being configured to receive the customized order.

Also included are embodiments of a server for customized ordering. At least one embodiment includes a first receiving component configured to receive an indication to send a previously created customized order to a vendor and a retrieving component configured to retrieve at least one component of the customized order according to the indication. Some embodiments include a first determining component configured to determine the vendor associated with the customized order and a first sending component configured to send the customized order to the vendor in a first manner, the vendor being configured to receive the customized order.

Other systems, methods, features, and advantages of this disclosure will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present disclosure.

BRIEF DESCRIPTION

Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views. While several embodiments are described in connection with these drawings, there is no intent to limit the disclosure to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.

<figref idref="DRAWINGS">FIG. 1</figref> is a network diagram illustrating an exemplary embodiment of components that may be utilized in placing an order with a vendor.

<figref idref="DRAWINGS">FIG. 2</figref> is a diagram illustrating an exemplary embodiment of components that may be present in a customized order server, such as the customized order server from <figref idref="DRAWINGS">FIG. 1</figref>.

<figref idref="DRAWINGS">FIG. 3</figref> is an exemplary embodiment of a user interface that may be presented to a user from a vendor's website, such as may be provided by a server from <figref idref="DRAWINGS">FIG. 1</figref>.

<figref idref="DRAWINGS">FIG. 4</figref> is an exemplary embodiment of a user interface that may be presented to a user in response to selection of the place order option from <figref idref="DRAWINGS">FIG. 3</figref>.

<figref idref="DRAWINGS">FIG. 5</figref> is an exemplary embodiment of a user interface that may be presented to a user in response to selection of the continue option from <figref idref="DRAWINGS">FIG. 4</figref>.

<figref idref="DRAWINGS">FIG. 6</figref> is an exemplary embodiment of a user interface that may be presented to a user in response to selection of the continue option from <figref idref="DRAWINGS">FIG. 5</figref>.

<figref idref="DRAWINGS">FIG. 7</figref> is an exemplary embodiment of a user interface that may be presented to a user in response to selection of the continue option from <figref idref="DRAWINGS">FIG. 6</figref>.

<figref idref="DRAWINGS">FIG. 8</figref> is an exemplary embodiment of a user interface that may be presented to a user in response to selection of the place order option from <figref idref="DRAWINGS">FIG. 7</figref>.

<figref idref="DRAWINGS">FIG. 9</figref> is an exemplary embodiment of a user interface that may be presented to a user in response to selection of a view account option from <figref idref="DRAWINGS">FIG. 3</figref>.

<figref idref="DRAWINGS">FIG. 10</figref> is an exemplary embodiment of a user interface that may be presented to a user for customized ordering, such as from a user device from <figref idref="DRAWINGS">FIG. 1</figref>.

<figref idref="DRAWINGS">FIG. 11</figref> is an exemplary embodiment of a user interface that may be presented to a user in response to receipt of a customized order, similar to the interface from <figref idref="DRAWINGS">FIG. 10</figref>.

<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for initializing a customized feature, such as in the network of <figref idref="DRAWINGS">FIG. 1</figref>.

<figref idref="DRAWINGS">FIG. 13</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for placing a customized order, similar to the flowchart from <figref idref="DRAWINGS">FIG. 12</figref>.

<figref idref="DRAWINGS">FIG. 14</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for capturing data for customized ordering, similar to the flowchart from <figref idref="DRAWINGS">FIG. 13</figref>.

<figref idref="DRAWINGS">FIG. 15</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for placing a customized order, similar to the flowchart from <figref idref="DRAWINGS">FIG. 14</figref>.

<figref idref="DRAWINGS">FIG. 16</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for sending a customized order in a plurality of formats, similar to the flowchart from <figref idref="DRAWINGS">FIG. 15</figref>.

<figref idref="DRAWINGS">FIG. 17</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for initiating customized ordering, similar to the flowchart from <figref idref="DRAWINGS">FIG. 16</figref>.

DETAILED DESCRIPTION

<figref idref="DRAWINGS">FIG. 1</figref> is a network diagram illustrating an exemplary embodiment of components that may be utilized in placing an order with a vendor. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 1</figref>, a user can place an order for products and/or services via a network <b>100</b>. More specifically, in at least one exemplary embodiment, a user communicating on a user device <b>102</b><i>a </i>may place a call to a vendor at a communications device <b>110</b>. In this nonlimiting example, the user can place an order with an employee at a pizza vendor. Generally speaking, the employee may ask a series of questions related to the pizza order before the order is complete.

Additionally, embodiments of this disclosure also include a user on a user device <b>102</b><i>b </i>placing an order with an online vendor via network <b>100</b>. More specifically, the user may access a website that is provided by a computing device <b>112</b>, such as a web server. The user can navigate a plurality of web pages provided by the computing device <b>112</b> until the order has been submitted. As indicated above, the user may be asked to navigate a plurality of web pages each time the user visits the website being provided by the computing device <b>112</b>. Similarly, a user device <b>102</b><i>b </i>may be configured to send a facsimile message to a facsimile machine <b>114</b> for ordering products and/or services. Similarly, user device <b>102</b><i>c </i>may be configured to perform one or more of the functions described above in a wireless fashion, via communication with an access point <b>104</b>, cellular tower (not shown) and/or other wireless communication medium.

Additionally included in the nonlimiting example of <figref idref="DRAWINGS">FIG. 1</figref> are a customized order server <b>106</b> and a data storage component <b>108</b>. As discussed in more detail below, customized order server <b>106</b> may be configured to facilitate customized ordering of goods and/or services with the devices <b>110</b>, <b>112</b>, <b>114</b>. More specifically, in at least one exemplary embodiment, one or more of the user devices <b>102</b><i>a</i>-<b>102</b><i>c </i>may be configured with customized order options for ordering goods and/or services from a vendor. As a nonlimiting example, the user device <b>102</b><i>a </i>may be configured to display one or more customized vendors, which may be defined by the user, the vendor, and/or a provider of the customized service. Additionally, some embodiments may be configured to utilize customized ordering without utilization of the customized order server <b>106</b> for at least a portion of the ordering process.

<figref idref="DRAWINGS">FIG. 2</figref> is a diagram illustrating an exemplary embodiment of components that may be present in a customized order server <b>106</b>, such as the customized order server from <figref idref="DRAWINGS">FIG. 1</figref>. Although a wire-line communications device is illustrated, this discussion can be applied to wireless devices, as well. Generally, in terms of hardware architecture, as shown in <figref idref="DRAWINGS">FIG. 2</figref>, the customized order server <b>106</b> includes a processor <b>282</b>, volatile and nonvolatile memory <b>284</b>, a display interface <b>294</b>, data storage <b>295</b>, one or more input and/or output (I/O) device interface(s) <b>296</b>, and/or one or more network interfaces <b>298</b> that are communicatively coupled via a local interface <b>292</b>. The local interface <b>292</b> can include, for example but not limited to, one or more buses and/or other wired or wireless connections. The local interface <b>292</b> may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface <b>292</b> may include address, control, and/or data connections to enable appropriate communications among the aforementioned components. The processor <b>282</b> may be a device for executing software, particularly software stored in volatile and nonvolatile memory <b>284</b>. The processor <b>282</b> can include any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the communications device <b>106</b>, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, and/or generally any device for executing software instructions.

The volatile and nonvolatile memory <b>284</b> can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory <b>284</b> may incorporate electronic, magnetic, optical, and/or other types of storage media. One should note that the memory <b>284</b> can have a distributed architecture (where various components are situated remote from one another), but can be accessed by the processor <b>282</b>.

The software in the memory <b>284</b> may include one or more separate programs, which may include an ordered listing of executable instructions for implementing logical functions. In the example of <figref idref="DRAWINGS">FIG. 2</figref>, the software in the volatile and nonvolatile memory <b>284</b> may include customized order logic <b>299</b>, as well as an operating system <b>286</b>. The operating system <b>286</b> may be configured to control the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.

A system component and/or module embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the volatile and nonvolatile memory <b>284</b>, so as to operate properly in connection with the operating system <b>286</b>.

The Input/Output devices that may be coupled to system I/O Interface(s) <b>296</b> may include input devices, for example but not limited to, a keyboard, mouse, scanner, touch screen, microphone, etc. Further, the Input/Output devices may also include output devices, for example but not limited to, a printer, display, speaker, etc. Finally, the Input/Output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, etc.

According to exemplary embodiments, the server <b>106</b> includes one or more network interfaces <b>298</b> for facilitating communication with one or more other devices. More specifically, the network interface <b>298</b> may include any component configured to facilitate a connection with another device. While in some embodiments, among others, the customized order server <b>106</b> can include a network interface <b>298</b> that includes a Personal Computer Memory Card International Association (PCMCIA) card (also abbreviated as “PC card”) for receiving a wireless network card, other configurations can include the communications hardware within the customized order server <b>106</b>, such that a wireless network card is unnecessary for communicating wirelessly. Similarly, other embodiments include network interfaces <b>298</b> for communicating via a wired connection. Such interfaces may be configured with Universal Serial Bus (USB) interfaces, serial ports, and/or other interfaces.

If customized order server <b>106</b> includes a personal computer, workstation, or the like, the software in the volatile and nonvolatile memory <b>284</b> may further include a basic input output system (BIOS) (omitted for simplicity). The BIOS is a set of software routines that initialize and test hardware at startup, start the operating system <b>286</b>, and support the transfer of data among the hardware devices. The BIOS is stored in ROM so that the BIOS can be executed when the customized order server <b>106</b> is activated.

When the customized order server <b>106</b> is in operation, the processor <b>282</b> may be configured to execute software stored within the memory <b>284</b>, to communicate data to and from the memory <b>284</b>, and to generally control operations of the customized order server <b>106</b> pursuant to the software. Software in the memory <b>284</b>, in whole or in part, may be read by the processor <b>282</b>, perhaps buffered within the processor <b>282</b>, and then executed.

One should note that while the description with respect to <figref idref="DRAWINGS">FIG. 2</figref> includes a customized order server <b>106</b> as a single component, this is a nonlimiting example. More specifically, in at least one embodiment, customized order server <b>106</b> can include a plurality of servers, personal computers, and/or other devices. Similarly, while the description of <figref idref="DRAWINGS">FIG. 2</figref> describes a customized order server <b>106</b>, this is also a nonlimiting example, as other components, such as the user device <b>102</b><i>a </i>and/or other components may also be included in this description.

Additionally, while customized order logic <b>299</b> is illustrated in <figref idref="DRAWINGS">FIG. 2</figref> as a single software component, this is also a nonlimiting example. In at least one embodiment, the customized order logic <b>299</b> may include one or more components, embodied in software, hardware, and/or firmware. Additionally, while customized order logic <b>299</b> is depicted as residing on a single computing device, such as customized order server <b>106</b>, customized order logic <b>299</b> may include one or more components residing on one or more different devices.

The embodiments disclosed herein can be implemented in hardware, software, firmware, or a combination thereof. At least one embodiment disclosed herein is implemented in software and/or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, as in an alternative embodiment, embodiments disclosed herein can be implemented with any or a combination of the following technologies: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.

<figref idref="DRAWINGS">FIG. 3</figref> is an exemplary embodiment of a user interface <b>320</b> that may be presented to a user from a vendor's website, such as may be provided by a server, such as the computing device <b>112</b> from <figref idref="DRAWINGS">FIG. 1</figref>. More specifically, the user device, such as the user device <b>102</b><i>b </i>may include browser logic for presenting a browser display <b>300</b> to the user. In response to instantiating the browser logic (which may be part of the customized order logic <b>299</b> and/or included as a separate logical component) and requesting the “Your Pizza Shack” website, the browser logic may display the browser display <b>300</b> and the user interface <b>320</b>. The user interface <b>320</b> can include a place order option <b>328</b>, a view order option <b>330</b>, and a view account option <b>332</b>. The place order option <b>328</b> may be configured to facilitate a user placing an order with the vendor “Your Pizza Shack.” The view order option <b>330</b> may be configured to facilitate presentation of one or more previously placed orders. The view account option <b>332</b> may be configured to facilitate presentation and amendment of the user's account settings.

According to exemplary embodiments, also included in the browser display <b>300</b> is a customized toolbar <b>322</b>. The customized toolbar <b>322</b> may be associated with the customized order logic <b>299</b> and may be configured to facilitate capture of data for customized ordering. More specifically, upon instantiating the “Your Pizza Shack” web page, the customized order logic <b>299</b> can determine whether the vendor Your Pizza Shack is registered with the customized service. If Your Pizza Shack is not registered with the customized service, options <b>326</b> and <b>327</b> may be presented to the user for starting and stopping data capture for the customized service. If Your Pizza Shack is registered with the customized service, the options <b>324</b> and <b>326</b> may be deactivated and the user can select option <b>324</b>.

In operation, a vendor may register with the customized order service by reaching an agreement to provide information to the customized order service provider for ordering products and/or services. Upon receiving this data, the customized order service provider may configure the customized order server <b>106</b> and/or the user device <b>102</b> such that the user's account may be configured for future ordering based on the structure of Your Pizza Shack's business and/or website model. If, Your Pizza Shack is not registered with the customized service, the user may still utilize the customized capabilities, however the user may select the start data capture option <b>326</b> to begin a data scrape associated with the present order. When the user is finished ordering, the user may select the stop data capture option <b>327</b>. Upon receipt of the scraped data, the user device <b>102</b> and/or the customized order server <b>106</b> may be configured to determine a technique for facilitating future customized ordering with Your Pizza Shack.

Additionally, if Your Pizza Shack is registered with the customized service, the user may select the option <b>324</b> to use this order for future customized ordering (thus overriding default and/or previously stored customized settings). While in some embodiments options <b>326</b>, <b>327</b> may be utilized at the beginning of the ordering process, option <b>324</b> may be utilized at any time during the ordering process.

<figref idref="DRAWINGS">FIG. 4</figref> is an exemplary embodiment of a user interface <b>420</b> that may be presented to a user in response to selection of the place order option <b>328</b> from <figref idref="DRAWINGS">FIG. 3</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 4</figref>, the browser display <b>300</b> can present the user with the user interface <b>420</b> for placing an order with the vendor Your Pizza Shack. More specifically, the vendor Your Pizza Shack may provide the user with a plurality of options for ordering a pizza. Upon selection of the desired pizza options, the user can select a continue option <b>422</b>.

<figref idref="DRAWINGS">FIG. 5</figref> is an exemplary embodiment of a user interface <b>520</b> that may be presented to a user in response to selection of the continue option <b>422</b> from <figref idref="DRAWINGS">FIG. 4</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 5</figref>, the user may further be presented with a plurality of options for ordering other items, such as drinks and sides. Upon selection of the desired drinks and sides, the user may select a continue option <b>522</b>.

<figref idref="DRAWINGS">FIG. 6</figref> is an exemplary embodiment of a user interface <b>620</b> that may be presented to a user in response to selection of the continue option <b>522</b> from <figref idref="DRAWINGS">FIG. 5</figref>. More specifically, as illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 6</figref>, the user is prompted to input his or her delivery information, billing information, and payment information. Upon inputting the requested data, the user can select a continue option <b>622</b> to proceed with the order.

<figref idref="DRAWINGS">FIG. 7</figref> is an exemplary embodiment of a user interface <b>720</b> that may be presented to a user in response to selection of the continue option <b>622</b> from <figref idref="DRAWINGS">FIG. 6</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 7</figref>, the browser display <b>300</b> may be configured to present the user interface <b>720</b> for confirming the order from <figref idref="DRAWINGS">FIGS. 3-6</figref>. More specifically, data related to the order may be presented to the user prior to submitting the order. Upon confirming the order, the user may select a place order option <b>722</b>. The order may then be submitted to Your Pizza Shack for processing.

<figref idref="DRAWINGS">FIG. 8</figref> is an exemplary embodiment of a user interface <b>820</b> that may be presented to a user in response to selection of the place order option <b>722</b> from <figref idref="DRAWINGS">FIG. 7</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 8</figref>, the user interface <b>820</b> may be configured to provide the user confirmation that the order was received and is currently being processed.

As illustrated in the nonlimiting examples of <figref idref="DRAWINGS">FIGS. 3-8</figref>, in the absence of customized ordering functionality, a user may navigate a plurality of web pages before completing the order. While such a configuration may facilitate the ordering process, oftentimes, a user desires the same order as previously used without having to complete the full ordering process.

<figref idref="DRAWINGS">FIG. 9</figref> is an exemplary embodiment of a user interface <b>920</b> that may be presented to a user in response to selection of the view account option <b>332</b> from <figref idref="DRAWINGS">FIG. 3</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 9</figref>, a user can view and/or change user information via a change option <b>922</b>. Additionally, the user can view and/or change customized information via a change option <b>924</b>. In this nonlimiting example, the vendor Your Pizza Shack is registered with the customized service. As such, the user can set customized ordering options without having to place an order at this time.

In response to setting and/or changing the customized order options, the vendor communications device <b>110</b>, the user device, such as the user device <b>102</b>, and/or the customized order server <b>106</b> may receive the updated information for future use. In at least one nonlimiting example, the vendor communications device <b>110</b> stores the information, such that any user device <b>102</b><i>a</i>, <b>102</b><i>b</i>, <b>102</b><i>c</i>, with proper authentication can send a customized signal to place an order according to the customized options. Additionally, some embodiments may be configured such that upon setting customized options, the user device <b>102</b> is configured to receive a customized command and send data related to the customized order. The user device <b>102</b> may be configured to send the order data to the customized order server <b>106</b> and/or one or more of the vendor devices <b>110</b>, <b>112</b>, <b>114</b>. Similarly, other embodiments can be configured to utilize the customized order server <b>106</b> to receive a customized command from the user device <b>102</b> and send the appropriate order data to one or more of the vendor devices <b>110</b>, <b>112</b>, <b>114</b>.

<figref idref="DRAWINGS">FIG. 10</figref> is an exemplary embodiment of a user interface <b>1020</b> that may be presented to a user for customized ordering, such as from the user device <b>102</b><i>b </i>from <figref idref="DRAWINGS">FIG. 1</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 10</figref>, the user interface <b>1020</b> may be presented via the user device <b>102</b><i>b</i>, which may include a personal computer, cellular telephone, a BellSouth® Personal Device top (BPD), a Quickconnect™ device, a Kitchen Broadband Device (KBD), other general purpose device, and/or other specific purpose device configured for facilitating customized ordering.

The user interface <b>1020</b> may be configured to display one or more selectable options associated with customized ordering. More specifically, the nonlimiting example of the user interface <b>1020</b> is configured to display selectable options <b>1022</b><i>a</i>-<b>1022</b><i>h</i>, which, according to exemplary embodiments, include names of vendors that are registered with the ordering service described herein. Upon selection of one or more of the options <b>1022</b>, an order may be automatically placed with the selected vendor. Additionally, scroll options <b>1024</b><i>a</i>, <b>1024</b><i>b </i>may be configured to view additional customized vendors associated with the user. Additionally, the user interface <b>1020</b> may also include an option for adding additional vendors to the customized vendor list of the user interface <b>1020</b>. By selecting an add more option <b>1026</b>, the user may be presented with an option to designate an additional vendor and/or an option to designate the customized order for this vendor.

Similarly, the user interface <b>1020</b> may also include a change existing option <b>1028</b> for changing the display order of vendors in the user interface <b>1020</b>, changing the display name of the vendors of the user interface <b>1020</b>, changing the order associated with the customized order options and/or changing other portions of the customized ordering configuration. Additionally, one or more vendors may be removed from the user interface <b>1020</b> by selecting a delete option <b>1030</b>.

One should note that, while the description above relates to ordering from the vendor Your Pizza Shack, this is a nonlimiting example. More specifically, as illustrated in <figref idref="DRAWINGS">FIG. 10</figref>, customized ordering can be applied to any of a plurality of different vendors. Additionally, depending on the particular configuration, a vendor may be listed as a plurality of customized ordering options. More specifically, in at least one exemplary embodiment, El Guapo Mexican Restaurant may be listed twice (under the same name or different names). A first occurrence of this vendor can include a customized order option for a first order and a second occurrence can include a customized order option for a second order with this vendor.

<figref idref="DRAWINGS">FIG. 11</figref> is an exemplary embodiment of a user interface <b>1120</b> that may be presented to a user in response to receipt of a customized order, similar to the interface <b>1020</b> from <figref idref="DRAWINGS">FIG. 10</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 11</figref>, in response to selecting one of the customized order option <b>1022</b><i>a</i>-<b>1022</b><i>h </i>from <figref idref="DRAWINGS">FIG. 10</figref>, the user interface <b>1120</b> may be displayed, confirming the order. According to exemplary embodiments, the order displayed includes an order provided by a particular vendor and selected by the user to be associated with the ordering service described herein. For example, if a user consistently orders a 12 inch hand tossed pepperoni pizza, a 2-liter bottle of brown soda, and an order of breadsticks from the vendor Your Pizza Shack, then the user may decide to associate the order with the ordering service so that when the user selects the ordering option <b>1022</b><i>a</i>, the order including the pizza, bottle of soda and breadsticks is retrieved for order confirmation, as illustrated in <figref idref="DRAWINGS">FIG. 11</figref>, eliminating the need for the user step through a number of options to achieve the same order. If the user wishes to change the order, the user may select a change option <b>1122</b> to be presented with options for changing the order. If the user wishes to cancel the order, the user can select a cancel option <b>1124</b>.

One should note that, depending on the particular configuration, the user may be presented with a intermediate user interface (not shown) to confirm that the order is being processed (similar to the user interface <b>720</b>, from <figref idref="DRAWINGS">FIG. 7</figref>). Additionally, the user interface <b>1120</b> may also be configured to display a countdown for the expected delivery of the order. Similarly, some embodiments may be configured to display a current status and/or position of the order. As a nonlimiting example, referring back to a previous example, if the user orders a pizza from the vendor Your Pizza Shack, the user interface <b>1120</b> may be configured to determine (from the vendor computing device <b>112</b> and/or from other sources) whether the pizza is currently in the oven. If the pizza is out of the oven, the user interface <b>1120</b> may be configured to determine whether the order is currently in transit and, if so, the geographical position of the order.

<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for initializing a customized feature, such as in the network of <figref idref="DRAWINGS">FIG. 1</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 12</figref>, a user can instantiate a browser (block <b>1232</b>) associated with a user device, such as the user device <b>102</b><i>b</i>. The user can then navigate the browser to a desired website (block <b>1234</b>). The user can select the start data capture option <b>326</b> (block <b>1236</b>). The browser can then begin to capture data sent to and/or received from one or more websites that the user is browsing (block <b>1238</b>). The user can then navigate one or more web pages during the purchase of goods and/or services (block <b>1240</b>). The user can select the stop data capture option <b>327</b> (block <b>1242</b>). The browser can stop data capture and send the captured data to the customized order server <b>106</b> (block <b>1244</b>). The customized order server <b>106</b> can process the received data to determine whether customized ordering is plausible. Customized ordering may be plausible when the user has an account that is configured for customized ordering and/or in other scenarios. If customized ordering is plausible, the customized order server <b>106</b> determines data, such as ordering preferences, etc., which may be associated with a code that uniquely identifies the user that is associated with the order for future customized ordering. Additionally, the server <b>106</b> stores the determined data (block <b>1246</b>).

One should note that the nonlimiting example described with reference to <figref idref="DRAWINGS">FIG. 12</figref> illustrates an exemplary embodiment associated with customized ordering when the vendor is not registered with the customized service. Additionally, depending on the particular configuration, a similar process may be utilized, regardless of whether the vendor is registered. One should also note that in at least one exemplary embodiment the user device <b>102</b> is configured to process the captured data to determine future customized ordering procedures (e.g., blocks <b>1244</b>, <b>1246</b>).

<figref idref="DRAWINGS">FIG. 13</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for placing a customized order, similar to the flowchart from <figref idref="DRAWINGS">FIG. 12</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 13</figref>, a user may select a customized order option on a user device <b>102</b> (block <b>1332</b>). The user device <b>102</b> can send an order request to the customized order server <b>106</b> (block <b>1334</b>). The customized order server <b>106</b> can determine the order associated with the order request and send data associated with the order to the designated vendor (block <b>1336</b>). A determination can then be made as to whether the order request is accepted by the vendor (block <b>1338</b>). If the order request is not accepted (e.g., the vendor is not currently open, the vendor is not taking orders at this time, the customer has a past due balance, etc.), the customized order server <b>106</b> can determine the problem with the order request (block <b>1340</b>). The customized order server <b>106</b> can then send an error message to the user device <b>102</b> (block <b>1342</b>). If, at block <b>1338</b>, the request is accepted, the vendor can send confirmation to the customized order server <b>106</b> (block <b>1344</b>). The customized order server <b>106</b> can then send confirmation to the user device <b>102</b> (block <b>1346</b>). As noted above, by using the order service described herein, the user may reduce the number of steps required to provide an order to a vendor.

<figref idref="DRAWINGS">FIG. 14</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for capturing data for customized ordering, similar to the flowchart from <figref idref="DRAWINGS">FIG. 13</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 14</figref>, a user can navigate a website associated with a vendor (block <b>1432</b>). The user can select the start data capture option <b>326</b> (block <b>1434</b>). The browser can send an indication to the customized order server <b>106</b> (block <b>1436</b>). The customized order server <b>106</b> can then determine whether there is an established agreement between the customized order service provider and the vendor (block <b>1438</b>). If there is no established agreement, the customized order server <b>106</b> can collect data communicated between the user's browser and the vendor (block <b>1440</b>). The customized order server <b>106</b> can then associate the retrieved data with the user and store the retrieved data (block <b>1442</b>).

If, at block <b>1438</b>, the customized order server <b>106</b> determines that there is an established agreement, the customized order server <b>106</b> can determine data requested by this vendor to facilitate customized ordering (block <b>1444</b>). The customized order server <b>106</b> can then store the requested data as communicated between the user and vendor until the user selects stop data capture option <b>327</b> (block <b>1446</b>).

One should note that, while the nonlimiting example of <figref idref="DRAWINGS">FIG. 14</figref> illustrates that a determination can be made in response to selection of the start data capture option <b>326</b>, this is a nonlimiting example. More specifically, in at least one exemplary embodiment, the customized order logic <b>299</b> may be configured to determine whether the vendor has an agreement with the customized order service provider upon the user accessing the vendor's website. Additionally, some embodiments may be configured to operate without utilizing the customized order server <b>106</b>.

<figref idref="DRAWINGS">FIG. 15</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for placing a customized order, similar to the flowchart from <figref idref="DRAWINGS">FIG. 14</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 15</figref>, a user can select a customized order option on user device <b>102</b> (block <b>1532</b>). The user device <b>102</b> can determine the vendor and/or order that was selected (block <b>1534</b>). A determination can then be made as to whether an agreement exists between the vendor and the customized order service provider (block <b>1536</b>). If no agreement exists, the customized order logic <b>299</b> (which may be associated with the user device <b>102</b> and/or customized order server <b>106</b>) can navigate the vendor website to place order (block <b>1538</b>). One should note that the customized order logic <b>299</b> can navigate the vendor website according to previously captured data associated with this vendor. Additionally, while the exemplary embodiment of <figref idref="DRAWINGS">FIG. 15</figref> discusses navigating a website, this is also a nonlimiting example, as some embodiments may be configured to send a facsimile to the vendor and/or place a telephone call with the vendor to place the order. Such configurations may utilize text-to-speech conversion techniques and/or other translation logic for converting the order into the desired format.

Upon placing the order, a determination can be made as to whether there is an error associated with the placed order (block <b>1540</b>). If there is an error, the customized order server <b>106</b> can receive an error message from the vendor (block <b>1542</b>). The customized order server <b>106</b> can then send the error message to the user device <b>102</b> (block <b>1544</b>). If, at block <b>1540</b>, there is not an error associated with the order, the flowchart can proceed to block <b>1548</b>, discussed below.

If, at block <b>1536</b>, a determination is made that an agreement exists between the vendor and the customized order service provider, the customized order server <b>106</b> can submit order data as requested by the vendor (block <b>1546</b>). The customized order server <b>106</b> can then receive an order confirmation (block <b>1548</b>). The customized order server <b>106</b> can then send the order confirmation to the user device <b>102</b> (block <b>1550</b>).

<figref idref="DRAWINGS">FIG. 16</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for sending a customized order in a plurality of formats, similar to the flowchart from <figref idref="DRAWINGS">FIG. 15</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 16</figref>, the customized order server <b>106</b> can receive an order for a vendor (block <b>1632</b>). The customized order server <b>106</b> can send the order data to the vendor in a first manner (block <b>1634</b>). The first manner can include any of a plurality of techniques, including navigating the vendor's website, determining whether the vendor has an agreement with the customized order service provider, sending a facsimile message, placing a telephone call, etc. In response to sending the order data in a first manner, the customized order server <b>106</b> can receive an error message indicating that the order was not processed (block <b>1636</b>). The customized order server <b>106</b> can then send an error message to the user device <b>102</b> (block <b>1638</b>). The customized order server <b>106</b> can then send the order data in a second manner (block <b>1640</b>). Sending the order data in a second manner can include sending the order data in a different manner than the first manner. More specifically, as a nonlimiting example, if the customized order server <b>106</b> first navigates the website, the customized order server <b>106</b> can send a facsimile message as the second manner. The customized order server <b>106</b> can then receive a confirmation message indicating that the order is being processed (block <b>1642</b>). The customized order server <b>106</b> can then send the substance of the confirmation message to the user device <b>102</b> (block <b>1644</b>).

One should note that while the nonlimiting example of <figref idref="DRAWINGS">FIG. 16</figref> illustrates an exemplary embodiment where sending the order data in a first manner receives an error message, this is a nonlimiting example, used for illustration purposes only. More specifically, in at least one exemplary embodiment, the order data may be sent in a first manner and then a determination is made as to whether the order is processed. If the order is not processed, the customized order server <b>106</b> may send the order data in a second manner. If the order is processed, the customized order server <b>106</b> may proceed as in blocks <b>1642</b> and <b>1644</b>. Similarly, while the nonlimiting example of <figref idref="DRAWINGS">FIG. 16</figref> illustrates sending the order data in a first manner and a second manner, one should note that the customized order server <b>106</b> may send the order data in any number of different manners until the order is processed. Additionally, the customized order server <b>106</b> may also send the order data in a first manner (or second manner, etc.) any number of times until the order is processed.

<figref idref="DRAWINGS">FIG. 17</figref> is a flowchart illustrating an exemplary embodiment of a process that may be utilized for initiating customized ordering, similar to the flowchart from <figref idref="DRAWINGS">FIG. 16</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 17</figref>, a user device <b>102</b> displays default customized order options (block <b>1732</b>). More specifically, depending on the vendors that the customized order service provider has obtained agreements from, a default listing of vendors may be displayed when the user device <b>102</b> is first used. The user can then select at least one of the customized order options (block <b>1734</b>). The user device may then contact the vendor associated with the selected option to set up customized ordering (block <b>1736</b>). As discussed above, in some embodiments, the user device <b>102</b> may be configured to directly contact the vendor. Similarly, some embodiments may be configured such that the user device <b>102</b> contacts the customized order server <b>106</b>, which then communicates with the vendor. Upon setting up the customized order options for ordering with the user, the vendor can then send the preferences to the customized order server <b>106</b> (block <b>1738</b>). The customized order server can then send the preference data to the user device <b>102</b> (block <b>1740</b>).

The embodiments disclosed herein can be implemented in hardware, software, firmware, or a combination thereof. At least one embodiment, disclosed herein is implemented in software and/or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, as in an alternative embodiment embodiments disclosed herein can be implemented with any or a combination of the following technologies: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.

One should note that the flowcharts included herein show the architecture, functionality, and operation of a possible implementation of software. In this regard, each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order and/or not at all. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

One should note that any of the programs listed herein, which can include an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a nonexhaustive list) of the computer-readable medium could include an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). In addition, the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.

One should also note that conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more particular embodiments or that one or more particular embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

It should be emphasized that the above-described embodiments are merely possible examples of implementations, merely set forth for a clear understanding of the principles of this disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure.