Keep working on orders accepted before the pause unless the restaurant and guest agree on a different outcome. A pause on new orders should not be treated as a cancellation of existing ones. First, identify every accepted order, assign someone to own it, and confirm whether the kitchen can meet the promised time.
If an order cannot be fulfilled as promised, tell the guest promptly and offer the options your restaurant can actually carry out. Record the decision and check the order through to its final outcome. The shift lead should keep the accepted-order queue visible even while staff deal with the reason for the pause.
Identify the accepted-order queue
Start with the time the pause took effect and the channels that may have sent orders before it. Depending on your setup, that might include your direct ordering site, phone orders, a POS, and separate marketplace or delivery screens. Ask the person who paused ordering what they saw, but do not rely on memory alone.
Pull together a list of orders that the restaurant has accepted but has not yet completed. Include orders placed before the pause that are still waiting for staff action; those need a separate decision, because a request received is not necessarily an order accepted. Check the status and your restaurant's acceptance rules before promising fulfillment.
For each order, the handoff needs an order identifier, items, promised pickup or delivery time, current preparation status, payment status, and a reachable guest contact method if available. For delivery, also note who is responsible for dispatch and what the current handoff status is. Do not assume that a delivery request means a courier has been assigned.
The shift lead can assemble the list, the kitchen lead can report what is being prepared, and the front counter or delivery coordinator can confirm pickup and dispatch details. Assign one person to maintain the list. That person does not have to perform every task, but should know who owns each next action.
Use the table as a working guide for a handoff. The right action depends on the actual order record and the restaurant's authority to change it.
| Order state | Check first | Next action |
|---|---|---|
| Accepted, not started | Items, promised time, kitchen capacity | Assign preparation or contact the guest about an alternative |
| In preparation | Progress, item availability, realistic finish time | Finish if feasible; flag any material delay |
| Ready for pickup or delivery | Guest or courier handoff status | Keep the order identifiable and follow up on the handoff |
| Received, acceptance unclear | Channel status and restaurant acceptance rules | Have an authorized staff member decide and record the outcome |
Do not clear a ticket merely to tidy a screen. A ticket disappearing from one view is not proof that the guest received the food, that a payment was handled, or that another channel has the same status.
Confirm preparation and promised times
Once the queue is visible, compare each promised time with what the kitchen can do now. The cause of the pause matters. A short staffing problem may slow every ticket; an unavailable ingredient may affect only certain items. A power or equipment problem may prevent preparation altogether.
Ask the kitchen lead for a realistic completion estimate for each affected order, not just a general reopening estimate. Check whether items can still be made safely and whether the order can be held appropriately if the guest or courier arrives late. The manager should decide which substitutions, cancellations, or payment remedies staff are authorized to offer.
Hypothetical example: A restaurant accepts three pickup orders before pausing new orders at 6:10 p.m. Order A is promised for 6:20 and is already being packed. Order B is promised for 6:25, but the kitchen estimates 6:35. Order C is promised for 6:40 and contains an item that has run out. Assume the restaurant can still prepare the remaining items and has contact details for all three guests.
The lead assigns A to the counter for its normal pickup. A staff member contacts B with the revised estimate and records the guest's choice. For C, staff check the approved alternatives before contacting the guest; they do not substitute an item without agreement. If the guest declines the available options, an authorized person follows the restaurant's cancellation and payment process.
This example separates an order that can proceed from one that is late and one that cannot be made as requested. In practice, a time estimate may change again. If it does, the order owner should update the record and decide whether another guest contact is needed.
Payment status deserves its own check. An accepted order may show a payment, an authorization, a failed payment, or payment due at pickup. Do not tell a guest that money has been returned until the responsible person has confirmed the relevant transaction status. Record any remaining follow-up rather than treating a cancellation as proof of a completed refund.
Contact guests when service changes
Contact the guest as soon as staff know that the promised order or timing needs to change. Give the order identifier, the issue, a realistic estimate or available alternative, and a clear way for the guest to respond. Avoid giving a new time the kitchen has not agreed to.
A useful message is: “Your order is running late. We expect it to be ready around 6:35 instead of 6:25. Would you like to keep the order or discuss another option?” Adapt the wording to the channel and the options the shift lead has approved. A delivery delay may also require coordination with the party responsible for dispatch; do not promise a courier arrival time without a reliable estimate.
Record the contact attempt, time, method, response, and next action. If the guest cannot be reached, give the order an owner and set a time to try again. Follow the restaurant's policy for how long to hold food and when an authorized person should make a further decision. A note such as “called, no answer” is more useful when it also says who will follow up.
For pickup orders, tell the counter about changes so the guest does not have to repeat the entire conversation. For delivery, separate the kitchen's ready time from the courier handoff. Food marked ready is not the same as food collected, and collection is not the same as confirmed delivery. Check what each channel can actually show.
Practice this handoff before a busy service with a simulated order and fictional contact details. Walk through a delay, a substitution request, and an unanswered contact attempt using a paper checklist or a safe training environment. The simulation must not trigger a real payment, guest message, or courier dispatch. A later live-service pilot uses real orders and requires an assigned lead to monitor actual communications and exceptions; it is not a substitute for safe practice.
Reconcile accepted orders before reopening
Reopening new orders should be a deliberate decision, not a way to make the old queue disappear. The shift lead should compare the handoff list with the available order, kitchen, payment, and delivery records. Resolve differences where possible and give any remaining exception a named owner and follow-up time.
Use this accepted-order handoff checklist during the pause and again at the shift change:
- Capture the boundary. Record when the pause took effect and which order channels were checked.
- List the work. Identify accepted orders that are not complete and separately flag requests whose acceptance is unclear.
- Assign ownership. Name the person responsible for each order and the person maintaining the overall list.
- Confirm the promise. Check items, preparation progress, promised time, pickup or delivery method, and a realistic next time with the kitchen and handoff staff.
- Handle changes. Contact guests when needed, record their decisions, and route cancellations or payment issues to someone authorized to act.
- Verify the outcome. Record fulfillment, cancellation, or an unresolved exception. Check payment and delivery follow-up separately.
- Hand over open items. Tell the incoming lead what remains, who owns it, and when the next check is due.
Before reopening, confirm that the kitchen and handoff staff can take additional work without abandoning those open items. An unresolved refund follow-up, for example, may have a named owner even after food service resumes. An unassigned order waiting to be prepared is a different problem: it still needs a service decision.
When evaluating software, ask vendors how staff can view accepted and pending orders during a pause, see promised times, record changes, and identify unresolved orders across the channels you use. Ask to see those steps with your own workflow rather than assuming that every screen or integration shares the same status. The online ordering buying guide can help frame the wider purchase decision, while your restaurant website and ordering channels should give guests clear expectations about when they can place an order.
Use the checklist against your current setup, then ask Fleksa about restaurant online ordering, the workflow you need, and verified US availability for your location.
Frequently asked questions
Does pausing new orders cancel accepted orders?
Do not assume it does. Identify accepted orders and continue handling them, or contact guests when the restaurant cannot fulfill them as promised. Confirm how each ordering channel represents a pause and an order cancellation.
What if an order arrived just before the pause but was not accepted?
Check its actual status and your restaurant's acceptance rules. Have an authorized staff member decide whether it can be accepted, then record the outcome and communicate with the guest as appropriate.
Can the restaurant reopen with an unresolved order issue?
That depends on the issue and the restaurant's capacity. Assign the exception to a named person with a follow-up time, and make sure the team can handle new orders without neglecting work still owed to existing guests.
