Before preparation starts, check that the kitchen can make the requested items and that the team knows when and how to fulfill them. If a missing or conflicting detail changes the food, timing, destination or price, pause the affected item and get an answer rather than guessing.
Give one person responsibility for resolving the question. Once it is settled, make sure the final instruction reaches the people preparing and handing off the order. The goal is a usable order for the kitchen, not simply a ticket that has been accepted.
Check items, modifiers and fulfillment time
Start with the order as the guest submitted it: item names, quantities, selected options, free-text notes and the requested pickup or delivery details. Compare these with the current menu and the instructions your team uses to prepare each item.
The guest supplies their choices and any notes. The restaurant supplies the menu descriptions, available options, preparation rules and handoff process. When those inputs do not agree, staff need to decide whether they can resolve the issue from reliable information or whether the guest must choose.
Review these points before sending an ambiguous basket into preparation:
- Items and quantities: Can staff identify each item? Does a note appear to request an extra item that is not in the basket?
- Modifiers: Are required choices present? Do selected options conflict with a written note?
- Special requests: Is the request specific enough to act on, and can the restaurant accommodate it?
- Fulfillment: Is the order for pickup or delivery? Is the requested time clear and workable?
- Handoff details: For delivery, is there enough information to find the destination? For pickup, is the identifying information clear enough for the handoff?
- Price or availability changes: Would the correction change what the guest expects to receive or pay?
Do not treat every note as a problem. “Sauce on the side” may be actionable if the dish and sauce are clear. “Make it like last time” is not actionable unless the team has a reliable, appropriate way to establish what the guest means.
Review the whole basket, but hold only what needs clarification when your workflow permits. If a side can be prepared independently while a main dish is unclear, the team can decide whether starting that side makes sense for its quality and the requested handoff time.
Know when the guest needs to decide
Staff can resolve an issue internally when the answer is already clear from the order and the restaurant’s documented menu or preparation rules. For example, a note asking for a listed sauce on the side does not need a call if it identifies the sauce and the kitchen can provide it.
Contact the guest when the choice belongs to them. That includes conflicting instructions, a missing choice that changes the dish, an unavailable item requiring a substitute, or a change to the expected charge. Do not add a paid extra or remove a meaningful ingredient based on a guess.
Dietary and allergy notes deserve particular care. If a guest writes “no dairy” but selects an item the team knows contains dairy, ask what they want to do. Follow the restaurant’s food-safety procedures and be honest about what the kitchen can and cannot accommodate. A clarification is not a guarantee that a meal is suitable for a particular guest.
The following hypothetical baskets show how the distinction works. They are practice examples, not descriptions of a particular ordering system.
| Basket detail | Decision before preparation | Reason |
|---|---|---|
| Two sandwiches; one note says “no tomato,” but does not identify which sandwich. | Ask the guest which sandwich should have no tomato. | The note changes one item, but its target is unclear. |
| One rice bowl with a selected hot sauce; note says “sauce on the side.” | Prepare with that sauce on the side if the kitchen can do so. | The selected sauce and requested handling are identifiable. |
| One pasta with cheese selected; note says “no dairy.” | Pause the pasta and ask the guest how to proceed. | The selection and dietary note conflict; staff should not choose for the guest. |
| Delivery address includes a building but no unit number; the building has multiple units. | Ask for the unit or an agreed handoff point before dispatch. | The destination may not be sufficient for handoff. |
The table separates a clear handling request from choices that need the guest’s input. A restaurant can add its own recurring examples, such as an unclear spice level or a requested substitution that the menu does not offer.
When contacting the guest, ask a narrow question and offer the actual available choices. “Your order has cheese selected and a no-dairy note. Would you like to change the item or cancel it?” is more useful than “There is a problem with your order.” Do not promise a substitute or revised price until the team has checked it.
If the guest cannot be reached, follow a written restaurant policy. That policy should tell staff who decides whether to hold or cancel the affected item or order, how to handle timing, and how to communicate the outcome. Avoid a default that silently changes the guest’s selection.
Assign one owner to each correction
Choose an order reviewer for each shift and a backup for breaks or busy periods. The reviewer does not have to solve every problem personally. Their job is to notice the issue, involve the right person and make sure it has a clear outcome before the affected food is prepared.
A simple division of work is:
- Reviewer: Checks the order, identifies the question and owns the follow-up.
- Kitchen lead: Confirms what can be prepared and whether a substitution is available.
- Guest-contact owner: Asks the guest to choose when needed and repeats the decision back.
- Handoff owner: Checks the final pickup or delivery details before the order leaves.
One person may fill several roles. What matters is that the team knows who has the next action. A ticket marked “check with guest” is not enough if nobody is responsible for making contact.
In a separate hypothetical example, an order has two soups and the note “one without onions.” The reviewer asks the kitchen lead whether either soup can be made without onions. If both can, the guest-contact owner asks which soup needs the change. If neither can, the owner explains the available choices rather than promising a change the kitchen cannot make. The reviewer then passes the guest’s decision to the kitchen and checks that the relevant ticket or other shared record reflects it.
Practice this handoff before relying on it during service. Use a simulated order and a staff member acting as the guest. Trace the question from review to kitchen instruction and handoff record. Keep the exercise in a training environment or on paper; it must not trigger a real payment, guest message or courier dispatch.
A simulation can expose an unclear role or a missed instruction, but it cannot show how the process holds up during a rush. For a live service pilot, designate the reviewer and backup on an actual shift, use normal channels only for genuine orders, and inspect how exceptions were resolved afterward. Do not manufacture a real guest contact or dispatch for practice.
Record the final decision before preparation
The final record should tell the next person what to do without requiring them to reconstruct a conversation. Use the order system’s available notes or another agreed shared record. Do not assume that a change made in one place automatically appears on every kitchen or handoff screen; check how your setup passes it along.
For an order that needed clarification, record:
- The affected item and the original ambiguity.
- The agreed action, including the specific item and modification.
- Any change to fulfillment time, destination or expected charge, if applicable.
- Who confirmed the decision and who must act next.
- Whether preparation may proceed or the affected item remains on hold.
Keep the wording operational: “Guest confirmed no tomato on sandwich 2; sandwich 1 unchanged” is easier to use than “fixed with customer.” If the original order cannot be edited, make the correction visible through the team’s established process and tell the kitchen directly. For a price change, confirm both the amount and the method for handling it under your restaurant’s procedures before proceeding.
At handoff, compare the prepared items and any delivery or pickup instructions against the final decision, not just the original basket. If the team discovers a mismatch, stop and resolve it before release. A record supports the check; it does not replace looking at the order.
Review repeated ambiguities at the end of a shift. If guests often write a note because a menu choice is unclear, consider revising the wording or options on your restaurant website. When evaluating software, ask how notes, changes and holds appear to the kitchen and handoff team, and who can update them. The online ordering buying guide covers broader purchasing questions.
Next step: Use this checklist on a simulated basket with your shift lead, then identify where a correction could be missed. If you are considering a new setup, ask Fleksa about its restaurant online ordering and verified US availability, including how your team would record and pass along an order correction.
Frequently asked questions
Should the kitchen start an order with one unclear item?
Hold the affected item until the question is resolved. The team may prepare independent items if doing so fits the restaurant’s workflow, food quality and requested handoff time.
What if the guest does not answer?
Follow the restaurant’s written policy for holding or canceling the affected item or order. Assign a person to make that decision and record the outcome rather than silently guessing.
Who should verify an online order?
Assign a reviewer on each shift, with a backup. The reviewer can involve the kitchen, a guest-contact owner and the handoff team, but should remain responsible for tracking the correction to a clear outcome.
