Accept future orders only for fulfillment slots your kitchen and delivery operation can actually support. Set a cutoff for each eligible order type, reserve part of your capacity for immediate orders, and stop accepting scheduled orders when the remaining capacity is gone.
A cutoff and a capacity limit do different jobs. The cutoff gives you time to prepare. The limit prevents too many orders from arriving for the same window. You need both, plus a clear way to handle an order that changes after the deadline.
Decide which orders can be scheduled
Start by separating an immediate order from an advance order. An immediate order asks for the next available pickup or delivery time. An advance order asks for a later fulfillment window, such as pickup tomorrow evening. A current pickup estimate does not establish that tomorrow's kitchen will have room.
Choose the order types that can use the calendar. A restaurant might allow regular menu orders for future pickup and delivery, while handling large group orders separately. Some items may need earlier notice than the rest of the menu. A platter that requires special preparation should not automatically inherit the same deadline as a sandwich.
Write down the rules before asking a software provider to configure them:
- Which days and hours can guests choose? Exclude closures and periods when the kitchen cannot fulfill the order.
- How far ahead can someone order? A short booking horizon makes staffing and menu availability easier to predict.
- Which items or quantities need a separate request? Define the threshold your team can recognize.
- Does delivery have a different cutoff or a smaller capacity than pickup?
- What happens when a requested window is unavailable? Offer another valid window rather than accepting an uncertain promise.
Also decide whether guests select an exact time or a window. A window can give staff room to manage several handoffs, but it must be clear to the guest when the order is expected. For delivery, ask whether the selected window refers to dispatch, an estimated arrival, or another milestone. Those are different promises.
Your restaurant website should make the order path and any important restrictions easy to find. The broader online ordering guide can help with the rest of the buying decision; the focus here is whether a future slot remains workable after orders start coming in.
Work backward from each fulfillment window
Start with the promised handoff, then list the work that must happen before it. For pickup, that may include cooking, packing, labeling, and staging. For delivery, add time to arrange the delivery and hand the order to the driver. Check what happens if a driver is delayed; the kitchen's ready time and the guest's arrival time are not interchangeable.
Next, identify the earlier decisions that affect readiness. A supplier deadline may fall the day before service. A manager may need advance notice to schedule an extra prep person. A large order may need a separate review before ingredients are committed. The customer-facing cutoff should leave enough time for the earliest necessary step, not just the final cook time.
The calendar below is a hypothetical example for one dinner service. It assumes a regular menu with predictable prep, staff already scheduled, and a delivery arrangement the restaurant has confirmed for that evening. The limits are operating choices for this example, not recommended defaults.
| Order type | Fulfillment window | Order cutoff | Capacity rule |
|---|---|---|---|
| Regular pickup | 5:00–5:30 p.m. | 3:00 p.m. same day | Shares a 12-order scheduled limit |
| Regular delivery | 5:00–5:30 p.m. | 3:00 p.m. same day | Shares the 12-order limit; no more than 4 delivery orders |
| Large group order | 5:00–5:30 p.m. | Noon the previous day | Separate request; accept only after staff review |
Read the first two rows together: the restaurant can accept at most 12 regular scheduled orders in that window, including at most four deliveries. It cannot accept 12 pickups plus four deliveries. A reviewed group order is not automatically included in that regular limit; before accepting it, the manager must decide how much regular capacity to remove.
These cutoffs do not mean every menu item is available until 3:00 p.m. If a supplier needs a count the previous day, either set an earlier deadline for that item, hold a suitable amount of stock, or remove it from later ordering. Confirm which of those choices the ordering system can support.
Set slot limits around the whole service
A slot limit is useful only if it accounts for the work already competing for the same people and equipment. Look at dine-in tickets, immediate online orders, phone orders, scheduled orders, and packing at the same time. An empty pickup shelf does not mean the grill has spare capacity.
For the example above, the 12-order scheduled limit assumes the restaurant has kept separate room for immediate orders and other service. If fewer cooks are available, the manager should reduce the limit before taking more orders. If the limit has already been reached, changing the setting does not remove the obligation to fulfill orders already accepted.
Order count is a rough control, not a measure of prep minutes. Twelve small orders and twelve complicated family orders can put very different pressure on a kitchen. Set a clear size threshold for manual review, and consider whether particular items should be excluded from the regular scheduled menu. Ask the provider whether limits can account for item quantities or order size; if not, decide whether an order-count cap and a separate large-order process are safe enough.
Check adjacent windows too. A 5:00–5:30 order may be cooked and packed alongside a 5:30–6:00 order. If both windows sell out, the combined prep load could exceed capacity even though neither individual cap was breached. Set limits with that overlap in mind, and review the busiest shared preparation period rather than only the handoff times.
Ask a provider to show how limits work across pickup and delivery, across ordering channels, and after an order is canceled. Can staff reduce a future limit? Does the system prevent further selection once a slot is full? Can it stop orders for a particular date without closing every other date? If a channel does not share the same capacity counter, assign a staff member to reconcile it or reserve separate capacity for it.
Agree on changes, cancellations, and the final promise
An accepted order needs one current version that both the guest and staff can understand. Decide who can change the time, items, or quantity; when changes stop being self-service; and who handles requests after that point. A time change may require capacity in a new slot, not just an edit to a receipt.
For a cancellation, decide whether the released space can be offered again. Before preparation begins, reopening the slot may be reasonable. After ingredients have been committed or the team has started work, a manager may need to decide case by case. Ask how the system reflects a cancellation for the kitchen, the ordering screen, and any delivery arrangement. Confirm payment handling separately with your provider and advisers where needed.
Plan for exceptions that do not fit a normal cutoff: an ingredient becomes unavailable, a staff member calls out, or delivery capacity falls through. Name the person responsible for contacting the guest and agreeing on an alternative. Record the final time and items where the team preparing the order will see them. Do not quietly move an order to another window and assume the guest knows.
When evaluating a provider, ask to see a sample confirmation and the corresponding staff view. Check that the date, time or window, order type, items, and any change are understandable. Also ask what staff see when an order is rejected, canceled, or no longer possible. The goal is a clear promise, not merely a calendar that looks full.
Practice the rules before opening the calendar
Use a simulated environment or a provider-led demonstration to walk through a regular scheduled pickup, a delivery, a full window, a large-order request, and a cancellation. Check the screens for both guests and staff. The simulation should not create a real payment, send a guest message, or dispatch a courier. If the provider cannot isolate a scenario safely, ask them to demonstrate it without submitting a real order.
Then review what would happen during a live service pilot. Choose a limited set of future windows, brief the people taking and preparing orders, and give one person authority to pause availability. A live pilot involves actual guest orders, so use your normal payment, communication, and delivery procedures. Monitor whether orders are ready within the promised window and whether staff can see changes in time. Adjust cutoffs and limits before expanding the calendar.
Next step: Pick one future service window and write its cutoff, shared capacity, delivery sublimit, and exception owner. Review Fleksa's restaurant online ordering page, then ask for a demonstration of those exact rules if the product fits your restaurant.
Frequently asked questions
Should delivery orders have an earlier cutoff than pickup orders?
Sometimes. Set an earlier cutoff when arranging delivery requires more notice than preparing a pickup. Confirm what the guest-facing delivery window represents and whether delivery capacity is available for it.
What should happen when a scheduled window is full?
Stop accepting additional orders for that window and offer another available time. Check that the limit includes every order type and channel intended to share that capacity.
Can a restaurant change an advance order after the cutoff?
It can decide to review requests after the cutoff, but a change should not be promised until staff confirm ingredients, preparation time, and capacity in any new window. Make sure the guest and kitchen receive the final details.
