When your restaurant closes unexpectedly, start with the orders you have already accepted—not just the message on your website. Set an affected time window, gather future orders from every channel, and give one person ownership of each order until the guest and payment outcomes are clear.
A closure notice helps prevent confusion, but it does not cancel an accepted order or prove that a guest has been contacted. The goal is a single working list that connects each order to its channel, fulfillment decision, contact status, and payment record.
Find affected dates, times, and ordering channels
First, record when service stopped and the earliest realistic reopening time. If you do not know when you can reopen, use a review cutoff rather than guessing that later orders are safe. For example, review everything scheduled through tomorrow evening now, then assign someone to check later dates at a set time.
Include orders placed before the closure as well as orders accepted after it began. Check pickup and delivery separately, including any orders scheduled outside the usual meal periods. An order's placement date is not necessarily its fulfillment date.
Ask the shift manager for the closure window and affected service areas. Ask whoever manages each channel to provide its future-order list. Depending on the restaurant, that may mean checking:
- Direct online orders and scheduled pickup or delivery orders.
- Marketplace dashboards and any separate delivery partner system.
- Phone orders, paper notes, email requests, and catering commitments.
- POS or payment records that may contain an order missing from another list.
Record the order ID, channel, guest name and available contact method, scheduled time, amount paid, and fulfillment method. Note the source of each record. If the same order appears in both an ordering system and a payment record, link the records rather than counting it twice. If details conflict, flag the order for review instead of choosing a version by guesswork.
Also check whether orders can still arrive while the team is working. Assign someone to monitor incoming channels and decide who can pause or adjust ordering where available. A restaurant website notice can explain the closure, but staff still need to review accepted orders in the systems where those orders were placed.
Assign the guest contact and cancellation decision
Give each order one owner, even when another party must carry out the cancellation or refund. That owner is responsible for checking the outcome and updating the sheet. Without a named person, an order can sit between the restaurant and a marketplace while each assumes the other has handled it.
Work through the soonest scheduled orders first. For each one, decide whether the restaurant can fulfill it safely at the promised time. If not, identify the available options: cancel, offer another time, or make another arrangement the guest agrees to. Do not mark an order rescheduled merely because a message was sent.
Use the channel's available contact and cancellation process. A direct order may call for the restaurant to contact the guest and act on the payment. A marketplace order may have a different process or require the marketplace to notify the guest. Check the applicable workflow before promising who will issue a refund or when it will arrive.
Keep the message short and specific: identify the restaurant and order, explain that the scheduled service is unavailable, and state the next action or request a decision. Record the attempt and time, then record the guest's response separately. If the guest cannot be reached, set a follow-up time and escalate rather than treating silence as consent.
Where delivery is involved, identify who can stop an unnecessary dispatch and who will confirm it. A canceled food order and a stopped courier request are separate checks. The same applies to a kitchen ticket: tell the kitchen not to prepare the order, then verify that its status has been updated wherever staff work.
Use a closure reconciliation sheet
Keep one row per order in a shared sheet or another controlled working list. Limit access to staff who need guest and payment details. Include enough information to act, but avoid copying full card details into the sheet. The table below shows a compact version; add columns for channel, scheduled time, owner, contact attempts, and the next review time in your working copy.
Hypothetical example: A restaurant closes before three scheduled pickup orders totaling $110. The amounts below represent payments already collected, not sales forecasts or processing fees. The restaurant decides to cancel all three. The table tracks the payment outcome alongside the operational work.
| Order | Paid | Guest and order status | Refund status and next action |
|---|---|---|---|
| A | $48 | Guest reached; cancellation confirmed | $48 completed; match to payment record |
| B | $35 | Guest reached; cancellation confirmed | $20 pending; investigate remaining $15 |
| C | $27 | Contact attempted; cancellation being handled | No refund recorded; confirm $27 outcome |
Of the $110 collected, $48 is recorded as refunded, $20 is pending, and $42 has no refund outcome yet: $15 for B and $27 for C. The pending amount is not a completed refund. Order B should remain open even though the guest was reached, because its full payment has not been resolved. Order C needs both a contact follow-up and a payment decision.
This example tracks payment amounts only. It does not estimate fixed operating costs, variable processing or delivery costs, or exception costs such as staff time or refund charges. Those costs belong in a separate closure-cost review if the owner needs one; they do not change the amount the sheet shows as collected.
Use clear status words consistently. “Contact attempted,” “guest confirmed,” “refund requested,” “refund pending,” and “refund completed” describe different events. A note such as “handled” is too vague for the next shift to verify.
Match refunds to payments and carry open work forward
For each canceled or changed order, find the original payment record and compare the amount collected with any recorded refund. Use the order ID and payment reference to connect them. If a refund is partial, record both the amount and the reason or question that remains. If another party controls the payment, record who owns the request and when the restaurant will check back.
Do not assume a refund is complete because someone pressed a button or submitted a request. Check the available status in the relevant payment record. If the system shows a pending or failed action, keep the order open and give it an owner. When a guest reports a different outcome, note the issue and follow the payment provider's or channel's process for investigating it.
Before reopening, have the manager review every row that is not resolved. The handoff should show:
- Orders awaiting a guest response, with the last attempt and next contact time.
- Orders awaiting cancellation, rescheduling confirmation, or a delivery-partner response.
- Refunds requested or pending, including amounts and the person responsible for checking them.
- Conflicting or missing records that need a channel or payment-provider follow-up.
Then confirm who is monitoring new orders as service resumes. Review the future schedule again if the reopening time changes. Keep unresolved rows visible after reopening; a busy first shift can otherwise bury a guest's unanswered message or a pending refund.
To prepare before the next disruption, walk staff through a simulation using fictional orders and statuses. Check whether they can identify the owner, next action, and payment outcome without triggering a real payment, guest message, or courier dispatch. A live service pilot is different: it involves actual operations and should be planned separately with appropriate controls.
Use this sheet to assess your current setup. Ask Fleksa about restaurant online ordering, including verified US availability and how your team would find scheduled orders and handle a closure. For a broader channel review, see the online ordering buying guide.
Frequently asked questions
Should I cancel every future order when the closure length is unknown?
Review the orders within a defined cutoff first, and set a time to revisit later dates. Cancel or offer another arrangement based on what you can reliably fulfill and the applicable channel process.
Is a closure notice enough to resolve an advance order?
No. A notice may inform visitors, but each accepted order still needs an owner, a fulfillment decision, appropriate guest follow-up, and a payment outcome.
When can an order leave the reconciliation sheet?
Keep it visible until the order and guest follow-up are resolved and the payment outcome is confirmed. Retain the record according to your restaurant's recordkeeping practices.
