Accept as many advance pickup orders in an interval as your kitchen can prepare on time while still handling walk-ins and leaving a small buffer. For a busy 15-minute slot, that might mean two orders rather than five. The right number depends on the work in each basket, the staff and equipment available, and the other tickets competing for them.
Start with a conservative cap for each busy interval, then compare promised pickup times with actual readiness. A cap controls how much work lands in a slot. An advance-order cutoff controls how close to pickup a guest can place an order. You need to decide both, but changing one does not automatically fix the other.
Estimate preparation minutes per slot
Choose an interval that matches how your kitchen plans pickup work. A 15-minute slot is a useful starting point if tickets arrive in short bursts. Longer intervals can hide a rush at one end; shorter ones may create more settings for staff to manage.
Ask the kitchen lead which stations constrain service at the time in question. Two cooks do not necessarily mean twice the capacity if both depend on the same fryer. Count usable work time at the limiting station, not every minute that every employee is on the clock. Allow for tasks those employees must do besides preparing pickup orders.
Next, estimate the workload of an ordinary advance-order basket. Use recent tickets to build a mix of simple and more demanding orders. Include packing and labeling if those tasks use the same constrained staff time. Ask the person who works the station to check the estimate: a menu item that looks quick on paper may compete for grill space or require several trips to the packing counter.
Hypothetical worksheet: A restaurant uses 15-minute pickup intervals. Its limiting station has two staff members, each with 15 minutes available for this work. The assumed mixed basket takes six staff-minutes at that station, including packing. These are planning estimates, not a promise that every basket will take six minutes.
| Slot input | Calculation | Planning result |
|---|---|---|
| Limiting-station time | 2 staff × 15 minutes | 30 staff-minutes |
| Walk-in reserve | Set aside for expected walk-in work | 12 staff-minutes |
| Service buffer | Set aside for small disruptions | 3 staff-minutes |
| Advance pickup capacity | 30 − 12 − 3 | 15 staff-minutes |
| Starting order cap | 15 ÷ 6, rounded down | 2 orders |
The table leaves three of the 15 advance-order minutes unused after two average baskets. That is additional breathing room, not permission to accept a third average basket: three would require 18 minutes. The worksheet measures staff time, not food cost, sales, payment fees, or overall operating cost. It does not include separate fixed costs or unusual exception work; the small service buffer is not a full allowance for a large catering ticket or equipment failure.
The arithmetic is a starting point. Check whether the food can actually move through the station within the interval. If both baskets contain items that each need the same piece of equipment at the same time, available staff-minutes alone may overstate capacity.
Reserve room for walk-ins and uneven baskets
A pickup cap should reflect the whole service, not just online demand. If walk-ins regularly arrive during the lunch rush, setting aside no capacity for them may keep the online queue tidy while making the counter line unmanageable. The kitchen lead and front-counter lead should agree on a realistic reserve for each busy period.
In the worksheet above, the 12-minute walk-in reserve is an assumption. If the team repeatedly uses more than that, fewer minutes remain for advance pickup. If walk-in work consistently uses less, there may be room to raise the cap—but only after checking the limiting equipment and how close the team came to missing promises.
Use different limits for different periods if your ordering setup permits it. A quiet midafternoon interval may support more advance orders than a dinner interval with the same headcount, because staff face different competing work. Check holidays, promotions, and local events separately rather than treating a normal Tuesday as a safe model for every day.
A simple order count also treats every basket as equal. One guest may order a single sandwich; another may place a large family meal. Ask whether the system can account for item quantities, large orders, or preparation workload. If it cannot, set the cap for a realistic mix and agree on how staff will handle an unusually large ticket. That may mean contacting the guest to agree on a different pickup time, not silently changing the promise.
The trade-off is visible: a low cap can turn away orders when the kitchen has room, while a high cap can create late food and crowd the counter. The best starting limit protects the pickup promise during ordinary busy service, then changes when the evidence supports it.
Decide what happens when a slot fills
Before setting a number, ask your provider exactly what a guest sees when the interval reaches its limit. Is the full time hidden, marked unavailable, or still selectable? Can the guest choose a later slot without rebuilding the basket? Does the limit apply to submitted orders, accepted orders, or another point in the process?
Also ask how cancellations, rejected tickets, and staff-entered orders affect the count. If an order is canceled, does its capacity return to the slot? If an employee takes a pickup order by phone, can that work be reflected in the same limit, or must the team reserve time for it separately? A limit is only useful if staff understand what it counts.
Set an acceptance rule before checking the setup. In the hypothetical two-order slot, the desired result is that two qualifying advance orders can select the interval and a third cannot select that same full interval. The third guest should have a clear way to choose another available time. If a canceled order is meant to reopen capacity, write that expectation down too and ask whether the system supports it.
First use a sandbox or other simulated environment with the provider or an employee acting as the guest. Do not use a real card payment, send a real guest message, or dispatch a courier for practice. Check the guest view and the staff view, including what happens when an order is canceled. If a safe simulation is unavailable, ask the provider to demonstrate the behavior without sending live orders.
A simulation checks the settings and screen behavior; it does not prove that the kitchen can meet the promised times. A live service pilot is a separate step using normal customer orders and a conservative cap. Assign someone to watch the queue and record readiness during that pilot. Tell staff how to respond if a delay develops, and keep the existing communication process available.
For the broader buying questions around order flow, the online ordering buying guide can help. Also check how guests reach pickup ordering from your restaurant website; a useful limit should be clear before a guest commits to a time.
Review readiness, late pickups, and kitchen delays
For each sampled interval, record the promised pickup time, the time the order was ready, and the time the guest collected it when staff can reasonably capture that information. Note the number of advance orders, approximate basket mix, walk-in pressure, staffing, and any unusual disruption. A short shift note is more useful than a complicated form nobody completes.
Separate two different delays. If food is ready after the promised time, investigate the kitchen queue, capacity assumption, or preparation lead time. If food is ready on time but the guest arrives later, the kitchen may have met its promise; the operational issue may instead be holding space or food quality. Late collection alone is not a reason to lower the order cap.
Review a few comparable services with the kitchen and counter leads. Look for patterns rather than reacting to one difficult ticket. Were large baskets clustered in one interval? Did walk-ins consume more than their reserve? Was a station unavailable? Did the queue move slowly even though the order count stayed under the cap?
If ordinary baskets are repeatedly ready late, lower the cap or increase the walk-in reserve for that period, then observe the next comparable services. If orders are consistently ready on time and staff report unused capacity at the limiting station, consider a small increase and watch for changes. Keep the cutoff decision separate: a cap may be appropriate while the kitchen still needs more lead time before the selected pickup interval.
Use the worksheet with your busiest predictable pickup period and ask the kitchen lead to challenge each assumption. Then review your current ordering setup against the full-slot questions above. If you are considering Fleksa's restaurant online ordering, ask Fleksa which capacity controls are available for your setup and confirm current US availability before making a decision.
Frequently asked questions
How many pickup orders should fit in a 15-minute slot?
There is no universal number. Estimate usable time at the limiting station, subtract reserves for walk-ins and disruptions, and divide the remainder by the work in an assumed mixed basket. Round down and check the result against actual readiness.
Is an advance-order cutoff the same as a slot limit?
No. A cutoff determines how late a guest can place an order for a pickup time. A slot limit determines how many qualifying orders can be accepted for an interval. A restaurant may need both.
Should late guest pickups count as kitchen delays?
Not if the food was ready by the promised time. Record readiness and collection separately so you can distinguish kitchen capacity problems from the need for better holding or pickup arrangements.
