How to Hand Off Order Changes: Check Kitchen Progress, Then Confirm the Change and Bill

When a guest requests a change, first check how far along the original dish is, then explain whether it can be changed. Don’t promise a change at the table and then only update the bill or add a note. The kitchen’s response, the guest’s agreement, and what is actually done must all relate to the same change. Even in a family-run restaurant where relatives share responsibilities, follow the same verification steps. An internal decision does not mean the guest has agreed.

Check the original order status first, then confirm what can be changed

Staff should locate the original order and confirm whether the guest wants to change the size, swap a dish, add something, or cancel an item. Don’t reduce every request to “make a change.” A request that has not yet been formally accepted is different from one involving a dish already in preparation. Front-of-house staff must first ask the kitchen station about the current status, then explain what the restaurant can accommodate. Don’t agree first and look for a reason to take it back later.

The kitchen’s response should specify the dish and its status—for example, whether preparation has not started, is at a particular stage, or is finished and waiting to be handed over. This information helps the person in charge decide what to do next; it does not mean every requested change can still be made. If a guest’s ingredient restriction is unclear, check the recipe and preparation requirements separately. Don’t assume that changing a side dish automatically meets all dietary requirements.

Use one order-change checklist to record each specific change

• Original order and item: Record an identifier that staff can look up, along with the original size and quantity. Avoid writing only “change the whole table’s order” or “make a change.”
• Guest’s new request: Specify whether they want a size change, a different dish, an addition, or a cancellation. List any ingredients, price differences, or wait times that still need to be checked.
• Kitchen response: Record the actual preparation status, whether the item can be stopped or changed, and which station responded. If no one has replied yet, leave it marked as unresolved.
• Guest’s confirmation: Repeat what the kitchen can do, then record the guest’s final choice. Don’t pass an unapproved substitution to the kitchen as a final decision.
• Confirmation of execution: Record who is taking over, what will happen to the original dish, whether the correction reached the kitchen station, and whose response is still pending.

After sending the change to the kitchen station, get a specific acknowledgment

MenuSnap’s kitchen guide notes that printed tickets do not automatically reflect later changes made on screen, so staff need an agreed method for passing on corrections. Front-of-house staff should give the kitchen station the original order identifier and the specific change, then have the recipient repeat back what they received. Don’t make kitchen staff search the entire order to work out what is different. Even when using a KDS, verify what the station actually received. A correction slip is only a handoff tool; it does not replace system updates or an acknowledgment from the kitchen.

When using screens and printed tickets together, the recipient should first check the order identifier and determine whether the new ticket is a correction, a reprint, or additional work. Printing also depends on the plan, equipment, rules, and executor configuration. If there is any doubt about whether the change was delivered, check the original order and what the kitchen station actually did. The staff member responsible should confirm which change the kitchen received, then report back to the front counter. Continue serving the guest as usual; don’t repeatedly reprint their order to troubleshoot a fault.

If the kitchen has already finished the original dish, the person in charge should explain the situation and the options permitted by the restaurant, then let the guest choose what happens next. Don’t have the kitchen tell the guest one thing while the cashier says another, and don’t make the guest track down the chef because of an internal communication mistake. If the dish needs to be remade, clearly identify the table that must not receive the original dish so the original and replacement aren’t both sent out later.

Don’t treat four separate outcomes as one

• Preparation: The kitchen station responsible confirms whether preparation of the original dish has stopped and whether the replacement can be made. Don’t infer this from a successful save at the front counter.
• Food served: The staff member running food checks which dish should be delivered. Handle the original and replacement separately; don’t put them together and rely on memory to tell them apart.
• Bill: An authorized staff member checks the latest items and amount due, then repeats the final order to the guest before taking payment. Don’t handle a price difference based only on a family member’s verbal report.
• Funds: Handle paid orders using the permitted process. Changing bill items, splitting a bill, or printing a new bill does not mean a refund has been issued. For online payments and refunds, rely on the results from the service and payment provider. For a standalone card terminal, verify the terminal transaction first, then record it against the corresponding bill; MenuSnap does not automatically verify this standalone terminal transaction.

During a network outage, keep a single record of changes already carried out and anything still awaiting a response. QR-code ordering through a web page, cloud syncing, and online payments depend on network access. The offline capabilities of a native client depend on the official version in use and its configuration. Once service is restored, check the orders and payments. Whoever takes over should first check the last confirmed details, then verify preparation changes and payment outcomes separately. Don’t carry out the same change twice.