When orders are arriving faster than your team can make them, pause the channel creating the most immediate pressure while keeping another service mode open. Start with the kitchen backlog and available staff, not a guess about which channel is least important. Give one person authority to make the change and another responsibility for checking when you can resume.
A targeted pause is a planned response to a rush, not a fix for a system outage. It only works if your ordering setup lets you control the chosen channel or service mode separately. Confirm that before you need it, and decide what staff should do if the controls do not match your plan.
Set a trigger based on workload
Choose a trigger your team can see during service. Ticket age is often more useful than the number of orders alone: six simple orders may be manageable, while six large orders with similar promised times may not be. Combine ticket age with the kitchen's view of what is still waiting and the front-of-house view of promised pickup or delivery times.
Assign three roles for the shift. In a small restaurant, one person may hold more than one role, but everyone should know who has the final call.
- Kitchen lead: reports the oldest open ticket, the number of orders waiting to be prepared, and any station that cannot keep up.
- Order coordinator: checks incoming channels, promised times, and whether drivers or guests are already waiting. This might be the shift's cashier or expediter.
- Shift manager: decides whether to pause, makes or delegates the setting change, and sets a time to review it.
Write the trigger in plain language and adjust it to your own operation. For example, a restaurant might decide that the manager checks capacity when the oldest unstarted ticket reaches 15 minutes and the kitchen lead reports that new orders are still arriving faster than the team can prepare them. Those figures are illustrative, not a recommended threshold for every kitchen.
Do not wait for a perfect count. A quick verbal report at a planned interval can be more useful than asking a busy cook to build a detailed spreadsheet. The manager should also check for an unusual large order, an absent employee, or a station problem. Each may change how much incoming work the restaurant can handle.
Choose the service mode to pause
First ask what is causing the bottleneck. If packing and handoff are congested but the line can still serve guests at tables, pausing an off-premise mode may help. If delivery orders require a driver handoff the team cannot manage, delivery may be the better candidate. If the kitchen itself is overloaded, keeping any channel open will still add work; choose the one the team can serve most predictably and be ready to pause more if the backlog continues to grow.
These service modes are not always the same as sales channels. A restaurant might receive pickup and delivery through its own website, through a marketplace, or by phone. Ask each provider whether you can pause delivery alone, pickup alone, or only an entire channel. Also ask whether a change applies immediately, how guests see it, and what happens to orders already accepted. Do not assume one switch controls every source.
The following is a hypothetical decision, not a claim about any particular system. A shift manager has a growing kitchen backlog and a crowded delivery handoff area. The restaurant can independently pause direct delivery while leaving direct pickup open. The table shows how the manager weighs the options; the right choice would change if the bottleneck or available controls changed.
| Option | Potential relief | Trade-off to check |
|---|---|---|
| Pause direct delivery | Fewer new delivery orders and handoffs | Pickup still adds kitchen work; delivery guests need another option |
| Pause direct pickup | Fewer new pickup arrivals at the counter | Delivery packing and handoffs continue |
| Pause the whole direct channel | No new direct online orders through that channel | Guests lose both direct service modes if they share that channel |
On those assumptions, the manager pauses direct delivery first and keeps pickup open. The manager then watches the kitchen backlog. If it keeps growing, the initial choice has not reduced demand enough; the team may need to pause pickup too, or use another available control. The goal is a manageable flow, not simply leaving a switch on.
Longer preparation times or a smaller menu may also reduce pressure, if your setup supports those controls and the kitchen can honor the new promise. Ask whether those changes affect existing orders and how quickly they appear to guests. A longer estimate is not useful if it is still shorter than the actual wait.
Tell guests what changed and protect accepted orders
A pause should be specific. Tell guests which mode is unavailable, what remains available, and when you expect to review the decision. Avoid promising a reopening time unless you are confident you can meet it. If your system offers a temporary notice, check where it appears before relying on it; guests may reach you through more than one ordering route.
A simple message could read: “Delivery ordering is temporarily paused while our kitchen catches up. Pickup ordering remains available. We will review delivery availability in 20 minutes.” That is a review time, not a promise that delivery will reopen then. If pickup later becomes unavailable, update the message rather than leaving an option advertised that guests cannot use.
The order coordinator should separate new demand from orders already accepted. A channel pause may not cancel or change those orders. Check the queue, identify upcoming promised times, and give the kitchen a clear sequence. If an accepted order will be late, follow the restaurant's normal guest-contact process and use the contact options available for that order. The manager should decide how to handle problems rather than asking a guest to discover them at the counter.
Practice the wording and staff handoff before a rush. In a simulated check, use a written sample queue and a draft notice; have the manager point out the control they would use and have the coordinator explain how they would check accepted orders. Do not submit a real payment, send a guest message, or dispatch a courier for practice. Confirm the actual settings with your provider or in a safe test environment.
For the public-facing side, review the ordering path from your restaurant website as well as any other places guests start an order. Your online ordering buying guide can help frame questions about the broader setup, but the rush plan should name the exact controls and staff responsibilities at your location.
Use a decision tree to resume at a sustainable pace
The pause is not finished when the manager flips a setting. Set a review interval at the time of the decision, then use the same workload signals that triggered it. The team needs to know who reports, who decides, and who checks the guest-facing result.
- Kitchen lead reports: Is the oldest unstarted ticket getting younger? Are the constrained stations keeping up? If not, keep the pause and identify the remaining bottleneck.
- Order coordinator checks: Are accepted orders progressing against their promised times, and is there room for another handoff? Flag any late orders or waiting guests to the manager.
- Shift manager decides: If the backlog is falling and staff can handle new work, reopen the paused mode if the system allows it. If capacity is still uncertain, continue the pause and set another review time.
- Order coordinator verifies: Check that the intended mode is available and that the notice reflects the current situation. Tell the kitchen lead the channel is open again.
- Kitchen lead and manager monitor: Watch the next wave of incoming work. If the backlog starts growing again, use the trigger and repeat the decision rather than waiting for another crisis.
There may be no gradual reopening control. If reopening immediately allows a volume the team cannot handle, ask the provider what other limits are available. If none fit, keep the pause until the team has enough capacity to accept the likely flow. Record what happened after service: the trigger, the mode paused, how long the backlog took to improve, and any confusion about the controls. Use that record to refine the next shift's plan.
Next, walk through this checklist with your shift manager and kitchen lead using your current ordering screens. Then ask Fleksa about restaurant online ordering, including verified US availability and whether the specific pause and reopening controls you need are available for your setup.
Frequently asked questions
Can I pause delivery but keep pickup open?
That depends on the controls in each ordering system and how your channels are configured. Ask whether delivery and pickup can be managed separately, and check every source that accepts orders.
What happens to orders accepted before a pause?
Do not assume they are canceled or delayed automatically. Check the accepted-order queue and ask your provider how its pause control treats existing orders.
When should I reopen the paused mode?
Review it when the kitchen lead reports a falling backlog, accepted orders are progressing, and the team has capacity for new work. If those conditions are not met, keep the pause and set another review time.
