Set your pickup promise around the time an order spends waiting, cooking, and being packed—not just the time it takes to make the food. Start with a realistic estimate for a normal service, then use a longer estimate or later pickup window when the kitchen queue grows. If the queue exceeds what the team can clear, pause new orders rather than offer a time you cannot meet.
The right settings depend on what your ordering system lets you change during service. Before choosing one, ask whether staff can adjust lead times, limit orders in a pickup window, and pause ordering without taking the whole website offline. Then match those controls to the way your kitchen actually works.
Separate preparation from pickup handoff
An online order may arrive while the cook is working on several tickets. The first wait is the queue before anyone starts preparing it. After cooking, the order may still need sauces, labels, a bag, and a final check. A guest-facing pickup time needs to account for all of those steps.
Track four points for a sample of orders: when the order arrives, when preparation starts, when the food is ready for packing, and when the complete order is ready for pickup. If someone routinely waits to bring bags to a pickup shelf or counter, include that step too. Record when the guest collects the order separately; a late-arriving guest should not make a well-prepared order look late.
Measure during a quiet period and again during your busiest pickup period. Include orders of different sizes and menu items that take longer. A small sandwich order and a large order with several cooked dishes may not belong in the same estimate. Note interruptions, such as a staff member leaving the packing station to answer the phone.
Use the busiest reasonable conditions you expect to handle, not the single fastest ticket. You do not need a complicated study to start. A few services of handwritten times can expose whether the main delay is at the grill, in the queue, or at the counter. Keep collecting observations as the menu, staffing, or order mix changes.
A pickup promise differs from a delivery estimate: there is no driver travel time to add. The guest still needs a clear time to arrive, and the restaurant needs a workable place to hold the order until collection.
Build a baseline and a peak-period buffer
A fixed estimate is simple: every new order receives the same lead time. It can work when demand and preparation times are fairly steady. Its weakness is that a quiet-period estimate may become unrealistic once several tickets land together. A long fixed estimate has the opposite problem: it may discourage a guest when the kitchen is nearly empty.
Scheduled pickup windows offer another approach where available. Guests choose from offered times, and the restaurant can plan work toward those handoffs. Ask whether a window represents a single promised time or a range, how far ahead guests can order, and whether the system limits orders per window. A displayed window alone does not guarantee the kitchen has capacity to fill it.
The following is a hypothetical peak-period worksheet for one ordinary order. The figures are planning assumptions, not a claim about any product or an actual service test.
| Stage | Time | What it covers | Operator check |
|---|---|---|---|
| Queue | 12 minutes | Wait before preparation starts | Count work already ahead |
| Preparation | 8 minutes | Active cooking and assembly | Check the slowest typical item |
| Packing | 5 minutes | Bagging, labels, and order check | Allow for a shared packing station |
| Handoff setup | 3 minutes | Move the bag to the pickup point | Keep this separate from guest arrival |
| Buffer | 7 minutes | Normal variation in service | Review if delays regularly exceed it |
| Total promise | 35 minutes | Arrival to order ready for pickup | Extend it if the queue grows |
The table adds 12 + 8 + 5 + 3 + 7 minutes. It includes a normal operating buffer, but not an equipment failure, an unusually large order, or another exceptional disruption. It also does not add time for the guest to travel. For a guest ordering at 6:00 p.m., the resulting target is ready by 6:35 p.m.
Build a separate baseline from your quieter observations. If the queue is shorter then, a shorter promise may be reasonable. Keep the peak worksheet available at the order-taking station so the person adjusting settings can see which assumption has changed.
Extend the promise or pause when demand exceeds capacity
A time estimate needs a capacity rule behind it. Decide how much work the kitchen can complete in a given period while still serving dine-in guests and other orders. Count the limiting station: a kitchen may have enough hands to pack ten bags but only enough grill space to cook six typical orders.
For a separate hypothetical example, suppose the team can prepare six typical pickup orders in 15 minutes during a particular shift after allowing for its other work. If six orders are already assigned to that period, a seventh needs a later slot or a longer lead time. Six is an assumed order limit here, not a count of physical tables or guest parties. Large or unusually complex orders may consume more than one ordinary order's worth of capacity, so staff still need judgment.
Set a trigger before service. For example, the shift lead might extend the lead time when the existing queue is longer than the queue used in the peak worksheet. If the system offers capacity controls, ask whether they apply by order count, item count, or another measure. Find out whether scheduled orders, walk-in tickets, and orders from other channels are included or must be checked separately.
Pause new online orders when extending the time no longer gives the team a credible target, or when an equipment or staffing problem makes capacity uncertain. Agree on who can pause and reopen ordering, where that control sits, and how the team will communicate the change. Pausing new orders should not mean forgetting orders already accepted: assign someone to review those tickets and contact affected guests through the restaurant's normal process if a promise must change.
Before a live service pilot, practice the steps in a simulation or training environment. Use dummy orders and disable real payments, guest messages, and courier dispatch. Check that staff can identify the queue, choose a longer time, pause, and reopen. Then, in a live pilot, observe normal orders during a defined service and use the restaurant's usual guest communication only when needed. Do not treat a simulation as proof of live-service performance.
Check the promise against actual ready times
After each pilot service, compare the time shown or given to the guest with the time the complete order was actually ready. Record the difference in minutes and the reason for a meaningful delay. Also note orders ready much too early: food quality and counter space can suffer when bags sit waiting for pickup.
Review the pattern by service period and order type. If most late orders contain the same slow item, address that item or ask whether the ordering system can apply a different preparation time to it. If delays occur across the menu whenever the queue grows, the lead time or capacity rule is the more useful setting to revisit. If food is ready but bags are missing drinks, change the packing check before simply adding more minutes.
Ask vendors to demonstrate the guest's view as well as the staff controls. What time appears before checkout and after the order is accepted? Can staff change a promise for an existing order, and how is the guest informed? What happens to future scheduled orders when ordering is paused? Confirm whether each control is available in the setup you would buy and who is responsible for changing it during a rush.
Your restaurant website should make pickup instructions easy to find, including where guests collect their food. For the wider ordering decision, the online ordering guide covers questions beyond timing. Keep your timing worksheet alongside those buying questions rather than relying on a default estimate.
Next step: Review Fleksa's restaurant online ordering page. If it fits your restaurant, ask for a demonstration using your busiest pickup period and the controls your team needs to adjust or pause orders.
Frequently asked questions
Should pickup time include the guest's travel?
No. Set the restaurant's promise for when the complete order will be ready for pickup. Guests can plan their own travel around that time. Record actual collection separately from the time the food was ready.
How much buffer should I add?
Use observations from your own service to cover ordinary variation, then check whether orders are consistently late or ready too early. A buffer is not a substitute for extending the estimate or pausing when demand exceeds capacity.
What if my ordering system cannot limit pickup windows?
Ask whether staff can manually extend lead times or pause new orders. Compare the visible queue with your kitchen's capacity, including work from other channels. If the controls are too slow or hard to use during a rush, include that in your buying decision.
