When an order changes after cooking starts, the kitchen needs to see the change as a correction to existing work, not simply as another ticket. The useful distinction is the item’s current state: what was originally requested, what is now required, and whether anyone has acknowledged the change.
Ask a vendor to demonstrate that distinction on every affected screen. If a cook cannot tell which instruction is current without guessing, you need a reliable verbal or written handoff to close the gap. The goal is to prevent both versions from being made or the corrected version from being missed.
Define new, changed, and canceled work
Start with a shared vocabulary. A new item is work the kitchen has not previously received. A changed item replaces an earlier instruction. A canceled item should no longer be prepared or sent. These states matter most after a ticket has been fired and someone may already have started it.
An addition can be straightforward: a guest adds fries, so the fry station receives one new portion. But the team still needs the order identifier and a way to connect the fries with the rest of the meal. Otherwise, the new item can be mistaken for a separate order.
A removal needs a stop instruction. If the guest removes a side salad, the pantry station should know not to finish or send it. If the salad is already plated, someone must decide what to do with the prepared food; a screen cannot undo the work.
A replacement combines both actions. Changing a beef burger to a veggie burger means stopping the beef item and starting the veggie item. The kitchen must not read that as two burgers. Ask whether the display shows the old instruction, the new instruction, and their relationship clearly enough for a busy cook to act.
Modifiers need the same care. A change from cheese to no cheese may affect a topping station even if the patty stays the same. For an allergy-related request, follow your restaurant’s established safety procedure and communicate directly with the responsible staff; do not treat a screen change alone as proof that an item is safe.
Routing determines where work goes in the first place. For that separate decision, see the guide to routing kitchen tickets by preparation station. Here, the question is what happens after those stations have already received work.
Trace a replacement across stations
Consider this hypothetical order: one beef burger with cheese, with grill responsible for the patty and pantry responsible for the bun and toppings. After both stations receive the ticket, the guest changes it to one veggie burger without cheese. The desired result is one veggie burger without cheese, not two burgers and not a veggie burger with the original topping.
First, the person taking the request confirms the full new instruction and enters the change through the order system. The grill cook needs to stop the beef patty if possible and start the veggie patty. Pantry needs to remove cheese from its instruction. If the bun is already assembled with cheese, pantry must follow the restaurant’s procedure for correcting it rather than assuming the old assembly is usable.
The expeditor or designated lead then checks both parts of the handoff. Has grill seen the replacement? Has pantry seen the modifier change? If the original beef patty has already been cooked, the lead also needs to know that it is no longer part of the guest’s order. The order should leave the pass only when the current item and its components match.
In a demonstration, ask the vendor to make this exact change after the original ticket appears on both stations. Watch what happens to the original line and the updated line. Can staff identify which version is current? Does each affected station receive a visible indication, and can the lead tell whether it has been acted on? If the workflow relies on a person calling the correction, establish who makes that call and who confirms it.
Do not assume an edit automatically recalls food already being made or clears every earlier instruction. A display can convey information, but a person still has to stop, remake, or replace physical food.
Use a change-decision worksheet
Before a demo, write down the point at which each change arrives and the action each station needs to take. The following hypothetical worksheet shows how the decision changes as work progresses. It is an operating aid, not a claim that any particular screen supports these displays or controls.
| Change and timing | Kitchen decision | What to verify |
|---|---|---|
| Add fries before fry work starts | Make one new portion and connect it to the existing order. | The fry cook can identify the addition and its order. |
| Remove a salad while pantry is plating it | Stop the salad; the lead handles anything already prepared. | Pantry receives a clear stop instruction and acknowledges it. |
| Replace a beef burger after grill starts and pantry receives the ticket | Stop the original item, start the replacement, and update affected toppings. | Both stations can distinguish current work from the original instruction. |
| Change a topping after the burger reaches the pass | Hold the item and have the responsible cook correct it before release. | The lead can identify the held item and confirm the correction. |
For each row, ask what the team sees, who must act, and how the lead knows the action is complete. If the answer is a verbal confirmation rather than a screen control, write that into the procedure. Also ask what happens when a change is entered while a station is away from its screen or while the original item has already been marked complete.
Keep the worksheet beside your buying notes. A clear visual update may be enough for a simple addition, while a replacement across stations needs an explicit stop-and-start handoff. A late correction at the pass needs a hold and a final check, even if the earlier stations have already cleared their work.
Assign acknowledgment and a recovery path
Pick one role to own the correction from entry to release. In a small kitchen, that may be the cook on duty. In a busier operation, it may be an expeditor or shift lead. The owner does not have to perform every task, but must know which stations are affected and get confirmation from each one.
Use a short handoff: order identifier, old item or instruction, new item or instruction, and required action. For the burger example, the message is to stop the beef burger, make the veggie burger, and remove cheese. Each affected cook repeats or otherwise confirms the relevant action. The lead then checks the finished item against the current order.
Decide what counts as acknowledgment in your operation. If the product offers a suitable control, ask to see what it records and who can view it. If it does not, use a defined verbal confirmation or another house procedure. An alert appearing on a screen is not the same as a cook confirming that work has stopped.
Also set an escalation rule. If a station cannot confirm promptly, the lead contacts it directly and holds the affected item at the pass. If the old item has already left the kitchen, staff should alert the service lead and follow the restaurant’s correction procedure. Avoid sending a second item merely because the team is unsure what happened to the first.
Test stale and duplicate tickets before service
Run practice scenarios in a vendor-supported training environment. Confirm beforehand that the simulation will not cause a real payment, guest message, or courier dispatch. Have the people who enter orders, cook, and run the pass take their usual roles. This is a simulation, not a live service pilot.
- Enter a practice order and show it at the affected stations. Change one item after staff have seen the original. Ask each person to point out the current instruction and describe the action required.
- Create a duplicate or stale-ticket situation using a vendor-supported method. Can the team recognize that an old instruction is no longer current? Ask what identifiers, timestamps, or other cues are available in that setup rather than assuming they exist.
- Walk through recovery. The lead identifies the order, confirms its current contents in the restaurant POS system or other designated source, tells each affected station what to stop or make, and checks the item at the pass.
- Repeat with an item already marked complete. Ask how staff can find the current order and communicate the correction if the earlier ticket is no longer visible. Do not assume a recall function is available.
Write down where staff hesitated and what handoff resolved it. Then run a supervised live service pilot using the agreed procedure, with a lead available to intervene. Real guest changes require normal service handling; do not manufacture payments, messages, or deliveries for practice.
Next, bring your completed worksheet to a demo and compare the workflow against your operating requirements with Fleksa’s kitchen display system. Ask the team to show the change on each affected screen and agree on the human fallback wherever the display alone is not enough.
Frequently asked questions
Should a changed item appear as a new ticket?
It can, but staff must be able to connect it to the original order and know whether it replaces or adds to earlier work. Ask the vendor to demonstrate how that distinction is communicated.
Who should acknowledge a correction?
Each affected station should confirm its own action. A designated lead should own the overall handoff and check that the current item is ready before it leaves the pass.
What if the original ticket is no longer visible?
Have the lead confirm the current order in the designated source, contact the affected stations, and hold the item until the correction is checked. Ask the vendor how staff locate completed work in the proposed setup.
