System, method and apparatus for receiving bids from diners for expedited food delivery

An order server operated by a restaurant service communicates with a restaurant server and a driver to retrieve incentive based food preparation and delivery time frames for an order. Using the time frames, the order server formulate a list of incentive based delivery plans, and provides the list to a diner device. From the diner device, the order server receives a selected incentive based delivery plan for the order from the list.

FIELD OF THE DISCLOSURE

The present invention relates to a system, method and apparatus for managing incentive based delivery of made-to-order food, and more particularly relates to a system, method and apparatus utilizing software applications operating on a delivery driver mobile device, a diner device, an on-site service appliance, a restaurant server, a driver server, and an order server respectively to efficiently deliver made-to-order food to diners based on one or more incentive plans offered to diners.

DESCRIPTION OF BACKGROUND

Delivery of made-to-order food is typically accomplished by delivery drivers (driving automobiles or riding bicycles) hired by a restaurant or delivery service. A delivery driver may deliver made-to-order food for multiple restaurants, while a restaurant may use multiple delivery drivers. The delivery time of an order is affected by a number of factors, such as the time that the serving restaurant of the order takes to prepare the order. Restaurants generally try to prepare food as soon as they can to satisfy their diners. A restaurant usually prepares its orders based on the reception time, from the first to the last, of the orders. However, neither the restaurant nor a restaurant service including the restaurant provides a way for a diner to selectively expedite the preparation of her order.

The delivery time of the order is also affected by the time between when the order is ready for delivery and when a delivery driver takes the order on a delivery trip. This time is determined by how fast the restaurant or delivery service finds a delivery driver for the order. Oftentimes, a restaurant uses certain delivery drivers. When none of the delivery drivers are immediately available to deliver the order, the restaurant is forced to wait until one of the delivery drivers becomes available to deliver the order. In particular, neither the restaurant nor delivery service can typically find a delivery driver who can deliver the order and deliver it within a certain time frame, if all of the restaurant's or delivery service's usual drivers are handling other orders.

Furthermore, the delivery time of the order is affected by the number of orders assigned to particular delivery trip, as well as the order in which a delivery driver delivers the orders. Delivery drivers generally follow delivery routes and deliver orders in predetermined orders or sequences, such as delivering the order with the address closest to the driver's restaurant or base first, or delivering an order designated by a restaurant manager as “important” first. However, diners sometimes desire to have their orders delivered earlier than a time dictated by the delivery route and sequence. The conventional delivery method does not provide an efficient way for diners to reduce the delivery time of her order.

OBJECTS OF THE DISCLOSED SYSTEM AND METHOD

An object of the disclosed made-to-order food delivery management system is to provide efficient delivery of made-to-order food;

Another object of the disclosed made-to-order food delivery management system is to allow a diner to expedite delivery of an order based on an incentive plan;

Another object of the disclosed made-to-order food delivery management system is to provide an incentive to a restaurant for expediting preparation of an order;

Another object of the disclosed made-to-order food delivery management system is to ensure timely delivery of made-to-order food;

Another object of the disclosed made-to-order food delivery management system is to maximize revenue for restaurants;

Another object of the disclosed made-to-order food delivery management system is to maximize revenue for a restaurant service;

Other advantages of the disclosed made-to-order food delivery management system will be clear to a person of ordinary skill in the art. It should be understood, however, that a system, method, or apparatus could practice the disclosed made-to-order food delivery management system while not achieving all of the enumerated advantages, and that the protected made-to-order food delivery management system is defined by the claims.

SUMMARY OF THE DISCLOSURE

By equipping delivery drivers with a wireless mobile device (“driver mobile device”), such as a smart phone or a tablet computer, that includes an application in communication with a driver server controlled by a restaurant service, a restaurant service can aid drivers in efficiently bidding for orders to deliver made-to-order food. In addition, the driver mobile device can aid in expediting deliveries, maximizing income, and providing prompt delivery statuses for diners. Furthermore, the driver mobile device application along with other server software applications assist the restaurant service in maximizing revenue for member restaurants, and providing incentive based deliveries for diners.

The driver server includes a driver server software application that is adapted to retrieve a list of orders for the driver mobile device and send the list to the mobile device. For example, the driver server application queries a database controlled by the restaurant service to retrieve the list of orders. The driver server software application is further adapted to receive a set of selected orders out of the list from the mobile device. Moreover, the driver server software application is adapted to assign one or more orders from the set of selected orders to the delivery driver in possession of the mobile device.

An order server of a restaurant service includes an order server software application to aid diners in efficiently bidding for expedited delivery of made-to-order food. The order server software application is adapted to retrieve incentive based food preparation time frames from a restaurant server and incentive based delivery time frames from a driver server for an order. Based on the time frames, the order server software application formulates incentive based delivery plans for the order, and communicates these plans to a diner software application running on a diner device. Alternatively, these plans are presented on a website and accessed using the diner device. Additionally, the order server software application is adapted to receive an indication of a selected incentive based delivery plan from the list of incentive based delivery plans.

The diner software application is adapted to request the list of incentive based delivery plans for the order from the order server software application over a wide area network, such as the Internet. Moreover, the diner software application displays the list of incentive based delivery plans for the diner to select one. Upon selection of one incentive based delivery plan for the order from the list, the diner software application communicates the selected plan to the order server software application. Additionally, the diner software application is adapted to receive order statuses for the order from the order server software application and/or other applications.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENT

Turning to the Figures and toFIG. 1in particular, an incentive based delivery management system100for a restaurant service is shown. The illustrated delivery management system100allows restaurants and delivery services to provide incentive based delivery of made-to-order food. Furthermore, the illustrated delivery management system100allows diners to use the supported delivery service(s) by, for example, bidding on earlier delivery of food.

An order server102collects orders from diners116, who use diner devices126, over a wide area network110such as the Internet. In one embodiment in accordance with the present teachings, the order server102includes a processor, a network interface, and some amount of memory. The orders are queued in a database104, which also includes information regarding diners as well as restaurant menus, as more fully set forth in U.S. application Ser. No. 13/337,362, which was previously incorporated by reference. A restaurant server34processes queued orders and communicates those orders to member restaurants35via the Internet110, a public telephone network (such as a phone network134), or some other method. In one embodiment, the member restaurant35houses an on-site service appliance36and/or a point-of-sale system38(“POS”). The member restaurant35and a delivery service may receive the orders using the on-site service appliance36. The member restaurant35then prepares the food, which is delivered by a delivery driver118to the corresponding diner.

The restaurant server34is coupled to a communication server130over a network132(such as an intranet or extranet). The communication server130is used to communicate with the diners116over the Internet110or a phone network134. A driver server108communicates with a driver mobile device122, which runs a driver mobile software application, over the Internet110. Alternatively, the driver server108communicates with the driver mobile device122via the communication server130, which is coupled to the Internet110and the phone network134. In one embodiment, in accordance with the present teachings, the driver server108includes a processor, a network interface, and some amount of memory.

Additionally, the driver mobile device122(which can be one of the mobile devices pictured inFIG. 11) includes a housing that comprises a touchscreen, a display, a processor, a wireless network interface, and a memory. For example, the driver mobile device122is a smartphone, such as an iPhone device created by Apple Inc. As an additional example, the driver mobile device122is a tablet computer or a laptop computer. A delivery driver118uses the driver mobile device122to retrieve orders from the driver server108for delivery, as more fully set forth in U.S. application No. 61/640,439, which was previously incorporated by reference. Furthermore, the driver mobile device122can send order delivery statuses to the diner device126over the Internet110or the phone network134.

In one embodiment of the disclosed delivery management system, when a diner software application running on the diner device126(which can be a desktop computer or one of the mobile devices pictured inFIG. 11) places an order, the order server102queries the restaurant server34, which subsequently queries the on-site service appliance36, for different incentive based food preparation time frames. In one implementation, the order server102communicates with the restaurant server34over the network132. Furthermore, the order server102retrieves incentive based delivery time frames for the order from a database104. Upon receiving the incentive based delivery plans from the order server102, the diner software application displays the order along with the plans, and allows the diner116to select an incentive based delivery plan.

When the diners116place orders using their diner devices126, the diner software application running on the diner devices126performs a process200, as illustrated by reference toFIG. 2. The diner software application can be a proprietary software application operating on a computer, such as, for example, a smartphone or tablet, or a browser displaying web pages. The diner software application provides a screen allowing the diner116to enter restaurant searching parameters. At202, the diner software application retrieves a set of restaurant search parameters entered by the diner116. At204, the diner software application sends the parameters to the order server102. Subsequently, at206, the diner software application receives a list of restaurants from the order server102. The diner software application then, at208, displays the list of restaurants on a screen of the diner device126. Responding to the diner116's selection of a restaurant, at210, the diner software application selects one restaurant from the list.

At212, the diner software application sends a request to the order server102for menu items of the selected restaurant. Subsequently, at214, the diner software application receives a list of menu items of the selected restaurants. In step216, the diner software application displays the list of menu items on the screen of the diner device126. The diner116chooses menu items and quantities of each selected menu item for her order. In response to the diner116's order, at218, the diner software application selects the chosen menu items and forms an order for delivery to the diner116. At220, the diner software application sends the order to the order server102. Then, at222, the diner software application receives, from the order server102, a set of incentive based delivery plans for the order. The diner software application, at224, displays the order and the incentive based delivery plans on the screen of the diner device126. A sample screen of the order and the incentive based delivery plans is shown at300, as illustrated by reference toFIG. 3.

Referring now toFIG. 3, the screen300includes some details302of the order. Additionally, the screen300includes three incentive based delivery plans304,306,308. For example, the delivery plan304is a normal delivery plan, under which the order is delivered by 7:30 PM without additional charge to the diner116. Under the plan306, if the order is delivered by 7:10 PM, the diner116will be charged an extra five dollars for the earlier delivery. Similarly, under the plan308, where the order is delivered by 6:50 PM, the diner116will be charged an extra ten dollars for the earlier delivery. For the delivery plans304,306,308, the screen300provides three checkboxes310,312,314respectively. The checkboxes310,312,314allow the diner116to select one of the delivery plans304,306,308. For example, where the diner116selects the delivery plan306, the checkbox312is marked, and a total charge of $43.50, including the five dollar upcharge for the delivery plan306, is indicated at316.

A “Place Order” button318allows the diner116to place the order. Turning back toFIG. 2, at226, the diner software application selects one delivery plan in response to a press of the “Place Order” button318by the diner116. Furthermore, at228, the diner software application sends the order along with the selected incentive based delivery plan to the order server102.

To enable the diner software application to place an order, the order server102runs an order server software application, which performs a process400, as illustrated by reference toFIG. 4, to handle order placement. Referring toFIG. 4, at402, the order server software application receives a restaurant search request with parameters, which were sent at204. At404, based on the received restaurant search parameters, the order server software application searches for restaurants from the database104. At406, the order server software application sends the search result, i.e., a list of restaurants, to the diner device126. At408, the order server software application receives a request for menu items of a restaurant. At410and412, the order server software application respectively retrieves the menu items for the restaurant from the database104, and sends the menu items to the diner device126.

At414, the order server software application receives an order from the diner device126. The order includes, but is not limited to, the restaurant, diner information (such as name, phone number, email address, address, etc.), order items, quantity for each order item, total charge, among others. At416, the order server software application requests for incentive based food preparation time frames for the order from the restaurant server34. In one implementation, the order server102sends the request directly to the restaurant server34over the network132. Alternatively, the order server102sends the request to the restaurant server34via the database104. At418, the order server software application receives one or more incentive based food preparation time frames for the order.

For example, where the order is completely prepared for delivery by 7:30 PM, the serving restaurant makes no extra charges for the order. However, if the order is completely prepared for delivery by 7:10 PM, the serving restaurant will charge the diner for an extra five dollars. As an additional example, if the order is completely prepared for delivery by 6:50 PM, the serving restaurant will charge the diner for an extra ten dollars.

At420, the order server software application requests for incentive based delivery time frames for the order from the database104or the driver server108. At422, the order server software application receives one or more incentive based delivery time frames for the order. At424, the order server software application formulates one or more delivery plans for the order. For example, the serving restaurant makes the order ready for delivery by 7:30 PM without extra charge, by 7:10 PM with an extra charge of five dollars, and by 6:50 PM with an extra charge of ten dollars. Additionally, a delivery driver can deliver the order by 7:45 PM without extra delivery charge, by 7:25 PM with an extra charge of five dollars, and by 7:10 PM with an extra charge of eight dollars. In such a case, the order server software application can formulate a number of incentive delivery plans. Some example delivery plans are: delivering the order by 7:45 PM on without incurring extra charges on the diner, delivering the order by 7:25 PM incurs an extra charge of ten dollars on the diner, and delivering the order by 7:10 PM incurs an extra charge of eighteen dollars on the diner.

At426, the order server software application sends the incentive based delivery plans for the order to the diner device126. At428, the order server software application receives the placed order with a selected delivery plan. At430and432, the order server software application respectively allocates the extra charge associated with the selected delivery plan between the serving restaurant and the delivery driver. In a further implementation, the order server software application allocates a portion of the extra charge for other parties, such as a restaurant service hosting the delivery management system100. It should be noted that, where the serving restaurant does not expedite the preparation of the order, the serving restaurant receives no incentive for an early delivery of the order. Similarly, where the delivery driver does not expedite the delivery of the order, the delivery driver receives no incentive for an early delivery of the order. Furthermore, where the serving restaurant and/or the delivery driver fail to expedite the order as agreed to, they may be charged a penalty. At434, the order server software application stores the order along with the delivery plan into the database104.

To provide incentive based food preparation time frames for an order, a restaurant server software application operating on the restaurant server34performs a process500, as illustrated by reference toFIG. 5. Referring toFIG. 5, at502, the restaurant server software application receives a request, sent at416, for incentive based food preparation time frames for the order. At504, the restaurant server software application sends the order to the on-site service appliance36over the Internet110, and requests for incentive based food preparation time frames for the order. At506, the restaurant server software application receives one or more incentive based food preparation time frames for the order. Thereafter, at508, the restaurant server software application sends the received incentive based food preparation time frames to the order server102.

To provide incentive based food preparation time frames for an order, an on-site service appliance software application operating on the appliance36performs a process600, as illustrated by reference toFIG. 6. Referring toFIG. 6, at602, the appliance software application receives a request for incentive based food preparation time frames for the order, which was sent at504. At604, the appliance software application displays the order and the request for incentive based food preparation time frames on a screen of the appliance36. A sample screen700of the order and request is illustrated by reference toFIG. 7. Turning toFIG. 7for now, the screen700includes some order details702, and different food preparation time frames704-708along with associated incentives710-714respectively. For example, if the serving restaurant35readies the order by 7:15 PM, it receives no extra incentive for preparing the order. However, if the serving restaurant35readies the order by 6:55 PM, it receives an extra five dollars for preparing the order. Additionally, if the serving restaurant35readies the order by 6:35 PM, it receives an extra ten dollars for preparing the order.

In one implementation, an employee of the serving restaurant can specify the different time frames704,706,708. In a further implementation, the employee can specify the amount of incentives710,712,714. Additionally, the employee can add and remove different time frames. When the employee is done with configuring different food preparation plans for the order, she presses a “Confirm” button716to respond to the request received at602. Turning back toFIG. 6, in response to the pressing of the “Confirm” button716by the employee, at606, the appliance software application receives one or more food preparation time frames for the order. At608, the appliance software application sends the received one or more food preparation time frames for the order to the restaurant server34.

Sometimes, incentive based delivery plans are not available for an order at the time the order is placed. For example, expedited preparation of food may not be available when the serving restaurant is overloaded with orders when the order is placed. As an additional example, expedited delivery plans may not be available when all delivery drivers associated with the serving restaurant of the order are delivering food at the time the order is placed. However, such options may become available for the order at a later time. For instance, when the order is out for delivery by the delivery driver118and the driver118has multiple orders to deliver, expedited delivery of the order can be made available to the diner116, provided that the driver118will not be made late for delivery of other orders of her current delivery trip. The diner116can be alerted of the newly available incentive based delivery plans via a text message, an email, a push notification, a web page, or a proprietary message. In such a case, the process of expediting the delivery of the order is illustrated by reference toFIG. 8.

Referring now toFIG. 8, a sequence diagram depicting the process of expediting the delivery of an order while the order is out for delivery is shown. At802, the diner device126sends a request for incentive based delivery plans for the order. The order server102receives this request and, at804, sends the request to the driver server108over the network132or via the database104. At806, the driver server, based on a set of factors, formulates different incentive based delivery plans. For example, where the driver118is delivering three orders, including the order in question, on a delivery trip, the driver server108can stipulate that, if the diner116pays an extra five dollars, the driver118will deliver her order ahead of the driver's other two orders. Another factor that the driver server108can consider is whether the driver118can still deliver the other two orders on time under the new delivery plan. Additionally, the driver server108can consider other factors, such as traffic patterns, where the driver118is in her delivery route, weather conditions, delivery plans for the other two orders, etc. In some cases, the driver server108may decide that no incentive based delivery plans can be provided for the diner116at a particular time.

Where incentive based delivery plans are available, at808, the driver server108sends the plans to the driver mobile device122. At810, the driver118decides whether to accept, modify, or reject the new delivery plans. Additionally, at812, the driver mobile device122sends the driver118's decision regarding the delivery plans to the driver server108. For example, the driver118selects one or more of the incentive based delivery plans. At814, the driver server108returns the decision to the order server102, which, at816, forwards the decision to the diner device126. For example, where the diner116selects one incentive based delivery plan, at818, the diner device126accepts the selected delivery plan. Accordingly, at820, the diner device126sends the diner116's acceptance of the delivery plan to the order server102. At822, the order server102allocates the incentive for the expedited delivery of the order to the driver116and/or other parties, such as the one that hosts the delivery management system100.

At822, the order server102further saves the change to the order into the database104. In a further implementation, the change is communicated to the restaurant server34which then forwards the change to the restaurant35for being displayed on the appliance36or the POS38. Alternatively, the restaurant server34retrieves the change from the database104. At824, the order server102sends a notification of the acceptance of the delivery plan to the driver server108. Accordingly, at826, the driver server108notifies the driver mobile device122of the new delivery plan for the order.

Sometimes, due to various reasons, a restaurant and/or delivery driver cannot execute an incentive based delivery plan for an order. In such a case, it is desirable to provide a prompt notification to the diner corresponding to the order. The notification process is further illustrated by reference toFIGS. 9 and 10. Turning first toFIG. 9, where the driver118determines that she cannot perform an incentive based delivery while she is driving her delivery route, at902, she uses the driver mobile device122to send a notification that she cannot deliver the order within the expedited time frame to the driver server108. At904, the driver server108removes the incentive for expedited delivery from the driver118and/or the serving restaurant. Additionally, at904, the driver server108may assess a penalty on the driver118for failing to deliver the order within the expedited time frame. Furthermore, the driver server108, at904, stores the changes to the order into the database104.

At906, via either the network132or the database104, the driver server108sends the order status change to the restaurant server34. For example, the driver server108writes the order status change to the database104, and a process running on the restaurant server34or the order server102retrieves this order status change. In one implementation, the process polls the database104for changes. Alternatively, the process receives notifications of changes from the database104, and then retrieves the changes from the database104. At908, the restaurant server34or the order server102sends the order status change to the communication server130, which, at910, sends the order status change to the diner device126. In a different implementation, the restaurant server34or the order server102sends the order status change to the diner device126directly. Alternatively, at912, the driver mobile device122sends the order status change directly to the diner device126. The order status change can be sent using an Email message, a text message, a robocall, a push notification, or a proprietary application message.

Turning now toFIG. 10, where the restaurant35determines that it cannot fulfill a promise for expedited preparation of an order, at1002, the appliance36sends the order status change to the restaurant server34. At1004, the restaurant server34removes the incentive for expedited preparation of the order from the restaurant35. Additionally, at1004, the restaurant server34may assess a penalty on the restaurant35for failure to prepare the order within the expedited time frame. Furthermore, at1004, the restaurant server34stores the change into the database104. At1006, the restaurant server34detects the changed database entry and sends the order status change to the communication server130. At1008, the communication server130sends the order status change to the diner device126.

Alternatively, the restaurant server34sends the order status change directly to the diner device126. In a different embodiment, the order server102retrieves the order status change from the database104, and sends, either directly or via the communication server130, the change to the diner device126. In a further implementation, the order status change is presented on a web page or sent to a software application running on the diner device126. The message accompanying the order status change may also indicate any modification, such as reduction or removal, to extra charges for expedited delivery.

Obviously, many additional modifications and variations of the present disclosure are possible in light of the above teachings. Thus, it is to be understood that, within the scope of the appended claims, the disclosure may be practiced otherwise than is specifically described above. For example, the functionality of each server as illustrated herein, such as the driver server108or the order server102, can be performed by more than one physical server.

The foregoing description of the disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. The description was selected to best explain the principles of the present teachings and practical application of these principles to enable others skilled in the art to best utilize the disclosure in various embodiments and various modifications as are suited to the particular use contemplated. It is intended that the scope of the disclosure not be limited by the specification, but be defined by the claims set forth below.