Expo should be able to see that an order is incomplete, identify the unavailable item, and know who is responsible for resolving it. The ticket should not look ready to leave simply because the other items are finished. Before buying a kitchen display system, ask the vendor to demonstrate that handoff from the expo screen through the final resolution.
The important distinction is between food that is ready and an order that is ready to release. A useful workflow keeps those states separate, gives staff a clear next action, and leaves a way to verify what happened after a substitution or refund.
Trace a ticket with two ready items and one unavailable item
Consider a hypothetical pickup order containing a burger, fries, and a bottled drink. The burger and fries are ready, but the requested drink is unavailable. The guest has not agreed to a replacement. The order is therefore incomplete even though two of its three items are ready.
Start the demonstration where expo normally receives the order. Ask the vendor to show the item names, quantities, and any relevant modifiers. Then have the trainer mark the burger and fries ready while leaving the drink unresolved. The person playing expo should be able to answer three questions without guessing: What is missing? Can this order leave? Who takes the next step?
A hold may appear as a status, a flag, a note, or another visible indicator. The exact design matters less than whether it is legible during a busy service and remains associated with the right order. Ask what happens if expo moves to another screen and comes back. If the hold depends on a handwritten note or a verbal handoff, include that step in the evaluation rather than assuming the display handles it.
Also check how the ready food is identified while it waits. A screen cannot keep fries crisp or prevent a bag from being picked up early. Decide where held food sits, how staff label it, and who checks it before release. The display and the physical holding area need to tell the same story.
Fleksa's kitchen display system shows order details including item names, quantities, and modifiers. Ask to see how your intended setup represents an unavailable item and an order that must stay at expo; do not assume a future-order hold is the same as a missing-item hold.
Compare a visible hold with a completed-order view
A completed-order view can be useful for finding a ticket after it leaves the active queue. It is not necessarily a good place to manage an unresolved order. If expo must search a history screen to discover that the drink is still missing, the workflow may make an incomplete ticket look finished during service.
Ask the vendor to show both views side by side, or in sequence if the system uses one display. Look for the point at which the ticket disappears from the active view. Can expo still distinguish a held order from one that was assembled and handed off? Can another staff member find it using the order identifier? If the answer depends on a manager, another device, or a separate POS screen, record that dependency.
The worksheet below gives an owner a starting standard for the demonstration. Adapt the acceptance criteria to your service, then record the vendor's actual evidence and any manual step beside each one. A verbal assurance is less useful than a screen walkthrough that shows the state before and after an action.
| Decision point | Evidence to request | Owner's acceptance criterion |
|---|---|---|
| Item unavailable | Show the drink unresolved while the other two items are ready. | Expo can identify the missing item and see that the order cannot leave. |
| Ticket visibility | Navigate away and return; show where the held ticket appears. | A second expo worker can find the order without treating it as completed. |
| Guest contact | Show how the contact task is recorded or explain the manual handoff. | One named role owns contact, and expo can tell whether a response is pending. |
| Resolution | Simulate a substitution and, separately, an item refund; show the final record. | Expo can verify the agreed outcome before release; the POS record matches the outcome. |
Use the same ticket and acceptance criteria with each vendor. Square describes kitchen tickets, timers, station routing, and expeditor functions for its KDS. Toast also offers a kitchen display product. Those descriptions do not establish how either product handles this particular hold, so ask each vendor to demonstrate it.
Station routing is a related decision: the person who sees a problem may not be the person who fixes it. If you are also deciding where tickets should appear, use the guide to routing tickets by preparation station alongside this test.
Assign guest contact and the front-of-house handoff
A missing item needs an owner, not just a warning. Choose the role before service: for example, expo flags the problem, while a front-of-house lead contacts the guest and reports the response. If the order is for an on-site guest, that may mean speaking to the server. For pickup, it may mean a call or another contact method your restaurant already uses.
In the hypothetical order, expo should not substitute a different drink merely because one is nearby. The front-of-house lead offers the available choices, gets the guest's decision, and tells expo exactly what was agreed. Until then, the order stays held. If the guest cannot be reached, your policy should say who decides what happens next and when the order is escalated.
Ask the vendor where staff record the contact status. Can the ticket show that someone is handling it, or must the team use a separate log? Can the next shift or another expo worker see the guest's answer? If the answer is no, a manual handoff can still work, but assign it explicitly and include its time and training in the buying decision.
Keep the message to expo specific: the order identifier, the missing item, the agreed replacement or refund, and the person who confirmed it. A vague instruction such as “all set” does not tell expo what belongs in the bag. Likewise, a replacement on a payment screen is not enough by itself if the assembly team never sees it.
Test the final state after substitution or refund
Run two separate paths in a vendor-supported training environment. These are simulations: they must not send a real guest message, charge or refund a real card, or dispatch a courier. Ask the vendor how the training setup prevents those actions before starting.
First, simulate the guest agreeing to a replacement drink. Show how the decision reaches expo, how the replacement is identified for assembly, and how staff confirm the order is complete. The acceptance criterion is not merely that someone entered a note. Expo must be able to match the replacement to the correct ticket and verify it is in the bag before release.
Next, reset the scenario and simulate the guest declining a replacement and receiving an item refund. Have the person authorized under your restaurant's process record the simulated refund in the POS. Then show what expo sees. The revised order can be complete without the drink only after the agreed refund is recorded and the handoff confirms that the drink should not be packed. Check that the final order record reflects the resolution and that the ticket no longer appears as an unresolved hold.
Ask what happens if the first resolution was entered incorrectly. Can an authorized person correct it, and can expo see the correction? Do not assume a system can recall a ticket or reverse an action; ask the vendor to show the supported path. If staff must use both the restaurant POS system and the KDS, identify who checks that their records agree.
After staff can complete both simulated paths, schedule a supervised service pilot with your normal authorization and guest-contact procedures. Observe whether the assigned roles can manage a real exception without losing track of the order. A training simulation checks the steps safely; a live pilot shows how those steps fit actual service.
Next step: Take the worksheet to a Fleksa demonstration and use it to compare your requirements with the KDS workflow. Ask to see the hold, handoff, and final record in your intended setup before buying.
Frequently asked questions
Should expo release an order when only one item is missing?
Not while the order remains unresolved under your service policy. First confirm the guest's decision and make sure expo knows exactly what to pack or leave out.
Is a completed-ticket screen enough to manage a missing item?
Only if staff can reliably find the order and distinguish an unresolved hold from an order that was actually handed off. Ask the vendor to demonstrate that distinction during the workflow.
Who should contact the guest about a substitution?
Assign a specific role, such as a front-of-house lead, and give expo a clear way to learn the response. The right role depends on your service, but ownership should be clear before the exception occurs.
