A kitchen display can distinguish an approved substitute from the standard recipe only if the kitchen has a clear way to identify the change and show it wherever the item is prepared. That might be a prominent staff note, a distinct recipe identifier, or another vendor-supported method. The buying decision is whether that method is visible and dependable enough for your service.
Ask vendors to demonstrate the complete path: select the alternate, send a simulated order, and show what each affected station sees. A note that appears on one screen but not another does not solve the shortage.
Decide who controls the recipe change
Start with an item your team knows well. Identify its standard ingredient, the approved substitute, and every station that must act differently. Include the person who checks the finished dish, not just the cook who first handles the ingredient.
The chef or another designated recipe owner should approve the substitute before it is used. That person also needs to tell the manager when the change starts and ends. The manager can then assign someone to update the order setup and tell the affected stations. Do not leave individual cooks to decide whether a substitute is acceptable from a ticket alone.
Define what the screen must communicate. At minimum, the cook needs to know which version to make and what to do differently. If the identifier is a code, staff also need a reliable place to find its meaning. A code such as ALT is not useful if nobody can tell which ingredient or preparation it represents.
This is a recipe-control decision, not simply a question of whether a display can show a customer modifier. A guest request may apply to one order; a shortage may affect every order for the item until the approved ingredient changes back. Ask how staff will apply the alternate consistently across order sources and shifts.
Also decide what happens to orders already in progress when the change starts. The team needs a handoff between the person making the change and the stations preparing existing tickets. A screen update alone should not be assumed to settle that transition.
Compare a staff note with a recipe identifier
A staff note puts an instruction alongside the item, such as “use approved substitute.” It can be practical for a short shortage if the note is easy to add, prominent on every relevant screen, and specific enough to act on. Check whether staff must add it to each order or can apply it consistently in another supported way. Manual entry on every ticket creates another opportunity to miss one during a rush.
A distinct recipe identifier gives the alternate a recognizable name or code separate from the standard version. For example, a ticket might show a standard identifier or an alternate identifier with a short instruction. This can make the versions easier to distinguish, but only if the system can display the identifier where cooks need it and the team knows what it means.
Neither approach is automatically better. A short note may be sufficient for one station over one shift. A distinct identifier may be preferable when several stations need to recognize the same alternate repeatedly. If the identifier requires staff to look up a long instruction away from the screen, factor that extra step into the decision.
Ask how each method is added, changed and removed. Can the same instruction appear for counter and online orders? Does changing it affect orders already sent to the kitchen? What happens if someone selects the standard version by mistake? Have the vendor show the actual workflow rather than relying on a feature name.
Fleksa offers a kitchen display system linked to restaurant orders. Its public product information describes item names, quantities and modifiers on the display. Ask for a demonstration of how your proposed note or identifier appears in your intended setup; those general display details do not establish that a particular alternate-recipe workflow is available.
Use an operator worksheet for one substitute
Hypothetical example: A restaurant normally makes a chicken bowl with a lemon dressing. The chef approves a yogurt-herb dressing as a temporary substitute. The hot line prepares the chicken, while the cold station adds the dressing and the expediter checks the finished bowl. The chef decides the hot line also needs to see the alternate so it can identify the correct bowl during handoff.
The worksheet below sets an expected result, not a claim about any product. Both approaches must tell all three roles which version is being made. The cold station also needs the ingredient instruction; the expediter needs an observable check before release.
| Checkpoint | Staff note | Distinct identifier | Owner and next action |
|---|---|---|---|
| Recipe approval | “Use yogurt-herb dressing” is the approved note. | “BOWL-YH” means the approved yogurt-herb version. | Chef approves wording and tells the manager when to activate it. |
| Hot line | Item and substitute note are visible. | Item and BOWL-YH are visible. | Hot-line lead identifies the bowl for handoff. |
| Cold station | Note names the dressing to add. | BOWL-YH and its dressing instruction are available to the cook. | Cold-station lead confirms the correct dressing is used. |
| Expediter | Note is visible for the final check. | BOWL-YH is visible for the final check. | Expediter checks the approved version before release. |
| Return to standard | Note is removed from new orders. | New orders use the standard identifier. | Manager confirms the change with all three roles. |
Before the demonstration, write down the exact screen or station each role uses. “The kitchen can see it” is too vague: an expediter view is not a substitute for an instruction on the cold-station screen. If a role needs a separate reference for an identifier, include that reference in the demonstration and time the extra lookup as part of your own evaluation.
Now consider the failure case. A simulated bowl reaches the cold station without the note or identifier. The expected response is to stop that simulated item, alert the shift lead, and resolve the version before preparation continues. The manager records the missing display as a failed requirement and asks the vendor whether it can be corrected. A verbal reminder may be a temporary backup, but it is not evidence that the display passed.
When lemon dressing returns, the chef approves the switch back. The manager changes the setup using the supported workflow and checks a new simulated ticket at every affected station. Separately, the team must identify any earlier tickets still being prepared under the alternate. Ask the vendor to show how those tickets appear during the transition; do not assume they update automatically.
Run a pass-or-fail vendor demonstration
Give each vendor the same item, roles, instruction and acceptance criteria. Use a vendor-supported training environment for simulations. Configure it so the exercise cannot take a real payment, send a guest message or dispatch a courier. Confirm those safeguards before entering the sample order. A simulated order is not a live service pilot.
- Set the standard: Show the standard bowl on each affected station. Pass if the team can distinguish it from the alternate. Fail if the version is ambiguous.
- Activate the alternate: Show who enters the approved note or identifier and how it is applied. Pass if the assigned manager can complete the steps and explain which new orders will carry the change. Fail if the team cannot tell where the change applies.
- Send a simulated order: Show the order at the hot line, cold station and expediter. Pass if each sees the agreed information and the cold station can find the dressing instruction. Fail if any required view is missing or unclear.
- Try an exception: Simulate a standard-version ticket arriving after the alternate is active, or a ticket missing the instruction. Pass if staff can recognize the mismatch and follow an agreed recovery process. Fail if the team cannot identify or resolve it before preparation continues.
- Restore the standard: Make the change back and send another simulated order. Pass if all affected views show the standard version and staff can distinguish any earlier alternate tickets. Fail if the transition leaves the team unsure which recipe applies.
For manual recovery, agree on a clear stop-and-check procedure. The affected cook alerts the shift lead, who confirms the approved version with the recipe owner or designated manager. The team then follows the vendor-supported correction process, if one is available, and communicates the result to every affected station. Ask the vendor to demonstrate correction, recall or rerouting if those steps matter to your procedure; do not assume they exist.
Ask support what happens when the display or connection is unavailable, who to contact during service, and how staff should identify outstanding alternate orders while using the restaurant's backup process. Also ask for a written quote covering setup, screens, training and support relevant to your workflow. Check any recurring or exception charges separately rather than treating a processing fee as the full operating cost.
After the simulation passes, train the affected roles. If you choose to proceed, plan a supervised live service period with the recipe owner or shift lead available to resolve issues. Use normal service controls and monitor the handoffs; do not treat a simulation as proof that every live-service condition has been covered.
The display is only one part of the order path. Review how the restaurant POS system and restaurant management software fit your ordering workflow. For the separate question of which screens receive an item, see the guide to routing tickets by preparation station.
Take your completed worksheet to a Fleksa demonstration and compare it with your KDS requirements. Ask Fleksa to confirm whether the note or identifier workflow, station visibility and recovery steps are available for your setup.
Frequently asked questions
Is a staff note enough for an approved substitute?
It can be, if the instruction is specific, applied consistently and visible at every affected station. Test those conditions before relying on it during service.
Does a recipe identifier replace the instruction?
Not necessarily. An identifier distinguishes versions, but staff still need to know what the alternate means and where to find any preparation instruction.
What should happen if a station cannot see the alternate?
Stop the affected item and have the shift lead confirm the approved version. Use the agreed manual recovery procedure, communicate with the other stations and resolve the display problem before relying on that workflow again.
