When an item note conflicts with an order-wide instruction, the kitchen needs to see both instructions before preparation and know who can resolve the conflict. A display that shows each note somewhere is not enough if a cook can easily act on one without seeing the other.
Choose a decision owner before shopping: usually the kitchen manager, with input from the person who handles guest questions. Together, they should decide what stops preparation, who asks for clarification, and how the answer gets back to the station. Then use the same simulated ticket with each vendor.
Decide what happens when instructions compete
A guest might remove cheese from one item and also write an order-wide note asking for cheese on every item. The kitchen cannot safely infer which instruction the guest intended to change. Either choice could produce an unwanted meal, a remake, or a delay while a new item is prepared.
The operational decision is not simply whether the screen can display notes. It is whether staff can recognize that the notes apply to the same item, pause that item, and get a clear answer before work starts. The rest of the order may or may not be able to proceed; set that rule according to your kitchen’s workflow and the nature of the question.
Do not establish a blanket rule that item notes always win or that the latest note always wins without considering what the guest meant. A note can be incomplete, entered in the wrong field, or added by someone other than the person eating the item. For an unclear or potentially safety-sensitive instruction, stop and clarify rather than guessing.
Map the people involved as well as the screen. A cook might spot the conflict, but a cashier or manager may be better placed to contact the guest. The kitchen manager should own the procedure and make sure a resolved instruction reaches the person preparing the food. Decide who covers that role during a rush or when the usual owner is absent.
Compare ways to catch conflicting notes
Start with the ticket layout. Ask vendors to show an item-level note and an order-level note together on the screen where the item will be prepared. Can staff read both without opening another view? If the order note is elsewhere, what action reveals it, and how would a cook know to look?
Visible notes support a human check, but they do not automatically flag a contradiction. This approach can work when staff have a consistent review step and ticket volume allows it. It is weaker when the order-level note is easy to miss, when text is truncated, or when different stations see different parts of the order.
A second approach is a manual hold-and-clarify procedure. Staff identify the conflict, keep the affected item from being prepared, and pass the question to the assigned owner. Ask how staff can mark or communicate that hold in the vendor’s actual setup. If the display has no suitable control, a clearly defined verbal or written handoff may be needed. That handoff must still tell the station when it can resume.
A third approach is a vendor-provided warning or workflow for competing instructions. Ask for a demonstration rather than assuming the system interprets free-text notes. Find out exactly which instructions trigger a warning, who sees it, and what happens if a conflict is not recognized. An automated warning can help staff notice a problem; it should not be treated as the guest’s answer.
Station routing adds another question: does the person preparing the affected item see the order-wide instruction as well as the item note? Use the guide to routing kitchen tickets by preparation station to think through the handoff, then test the conflicting notes at the actual station views you expect to use.
Work through a hypothetical ticket
Use this hypothetical order in a vendor-supported training environment. It contains two burgers. The first has an item note, “no cheese.” The order-wide note says, “add cheese to every burger.” The second burger has no item-specific note. The instructions conflict for the first burger; the second is not the subject of that conflict.
For this exercise, the expected response is to pause the first burger, ask the designated clarification owner to resolve the contradiction, and communicate the answer to its preparation station. The kitchen manager may allow the second burger to proceed under the normal workflow, but should account for timing so the complete order can still be served together.
The worksheet below follows the ticket from display to release. It separates what staff should see from who must act. Replace the role names with your own before using it in a demonstration.
| Step | Expected result | Responsible person | If it fails |
|---|---|---|---|
| Review ticket | Item removal and order-wide cheese instruction are both readable at the relevant station. | Cook | Pause the affected item and notify the kitchen manager; do not guess. |
| Identify conflict | Cook recognizes that the first burger has opposing instructions. | Cook | Manager reviews the complete ticket and reinforces the check. |
| Clarify | Assigned owner asks which instruction applies to the first burger. | Cashier or manager | If no answer is available, keep the item on hold and follow the restaurant’s unresolved-order procedure. |
| Release | The resolved instruction is communicated to the preparing station before work starts. | Clarification owner and cook | Keep the item on hold until the cook confirms the instruction. |
In the simulation, have one staff member play the guest and answer, “No cheese on the first burger; add cheese to the second.” The clarification owner then conveys that answer to the cook. Ask the vendor to show how the resolved instruction can be recorded or displayed in the proposed setup; do not assume an edit, flag, or recall control is available.
Now change the answer: the simulated guest cannot be reached. The expected result is not an invented resolution. The affected item stays on hold while the manager follows the restaurant’s procedure for an unresolved order. That procedure should say who decides the next step and how the rest of the order is handled.
Run the exercise without a real card payment, guest message, or courier dispatch. A training ticket should not enter a live service queue. If the vendor cannot provide a suitable training environment, use a non-transactional walkthrough with screenshots or a mock ticket until a safe simulation is available.
Set a pass-or-fail vendor test
Give every vendor the same ticket and the same station layout. Include the people who would actually review and prepare orders, not only the person buying the software. A restaurant POS system and its kitchen display may share order information, but the buying decision depends on what each role can see and do in your configuration.
- Visibility: Pass if the cook can read both instructions before starting the first burger and can tell which item the removal applies to. Fail if either instruction is missing, hidden without an obvious review step, or unreadable in the demonstrated view.
- Recognition: Pass if the cook identifies the contradiction and pauses the affected item. Fail if the cook proceeds based on only one note. A warning is not required to pass if the agreed manual check reliably catches the simulated conflict.
- Handoff: Pass if the cook identifies the clarification owner and that person receives the question. Fail if staff do not know who owns the next action or the question is lost between roles.
- Resolution: Pass if the cook receives and confirms the simulated answer before preparation. Fail if the item is released before confirmation or the original conflicting instructions remain the only guidance staff use.
- Exception: Pass if staff keep the affected item on hold when the simulated guest cannot answer and follow the assigned unresolved-order procedure. Fail if anyone silently chooses an instruction.
Record the result for each step, including any extra screen, verbal handoff, or workaround the team needed. A pass is specific to the demonstrated setup and staff procedure. Repeat the exercise with a longer order note and at each relevant station; a layout that works on one screen may be harder to use on another.
Ask support a practical recovery question: “If the person who spotted the conflict leaves the station before clarification returns, how does the next cook know the item is still on hold and who has the answer?” Have the vendor show the proposed workflow and explain any setup or staff steps it requires. Also ask how changes to an order are communicated to the kitchen after a ticket has appeared.
After simulations, a supervised service pilot can help your team observe the agreed workflow with actual orders. Use normal restaurant procedures for any real guest clarification, and stop the pilot to correct gaps. A simulation checks the planned steps; a live pilot shows how those steps fit the pace and handoffs of service. Neither guarantees that every future conflict will be caught.
Before choosing, compare your requirements with Fleksa’s kitchen display system and the wider restaurant management software. Bring the hypothetical ticket to a demonstration, confirm feature availability for your setup, and ask Fleksa to walk your team through each acceptance step.
Frequently asked questions
Should an item note override an order-wide note?
Not automatically. When the two instructions conflict, pause the affected item and ask the designated owner to clarify what the guest wants before preparation.
Does a kitchen display automatically detect conflicting notes?
Do not assume it does. Ask the vendor to demonstrate any warning with your sample ticket, including what staff see and what happens when the system does not recognize a conflict.
Who should clarify a conflicting instruction?
Assign a cashier, manager, or other available role before service. The cook should know how to reach that person, and the clarification owner should confirm the answer reaches the preparing station.
