When one item is finished before the rest of its ticket, the kitchen needs to record that progress without hiding the unfinished food. Look for a display workflow that makes the ready item clear, keeps the other items visible to the people preparing them, and gives expo an accurate view of the whole order.
The buying decision is not just whether a screen has a button labeled “done.” It is what happens after someone presses it: which item changes, which views update, and whether staff can correct a mistake without losing track of dinner.
Trace a three-item order with one item ready early
Use a small order to make the decision concrete. In this hypothetical example, a table orders one salad, one burger and one pasta. The salad station finishes first. The grill is still cooking the burger, and the pasta station has not finished its dish. Assume an expo person coordinates the three items before they leave the kitchen.
The useful result is straightforward: the salad shows as ready, while the burger and pasta remain open on the views their cooks use. Expo can see that one item is ready and two still need work. The order itself remains active until the remaining food is ready and the restaurant follows its normal handoff process.
That distinction matters even in a small kitchen. If a cook marks the entire ticket complete just to clear the salad, the other cooks may lose a prompt they still need. If nobody records the salad as ready, expo may keep asking about it or prepare a second one. Either workaround adds a verbal step that can fail during a rush.
Before a demo, write down what “ready” means in your kitchen. Does it mean the cook has finished preparing the item, or that expo has checked it and placed it with the rest of the order? Pick one meaning for the test. Item completion and expo handoff can be separate decisions; a screen should not make staff guess which one they just recorded.
Also decide how quantities should work. If a ticket has two burgers, ask whether a cook can mark one ready while the other remains open, or whether the system treats the two as one line. That difference can change the workflow even when a vendor says it supports item-level status.
Compare item and ticket completion visibility
Run the same order through each product you are considering. The worksheet below sets out the result to look for, not a list of features every system is assumed to have. Use the last column to decide what to ask if the screen behaves differently.
| Check | Result to look for | Question if it differs |
|---|---|---|
| Salad marked ready | Only the salad changes status; the order stays active. | Can an individual item be updated without closing the ticket? |
| Burger and pasta | Both remain visible as unfinished to the relevant cooks. | Where do unfinished items appear after another item is completed? |
| Expo view | Expo can distinguish the ready salad from the two open items. | Can expo see item progress without asking each station? |
| Early mark | Staff can identify and correct the salad’s status or follow a clear fallback. | Who can correct it, and what happens on other views? |
Compare the number of actions as well as the final screen. A workflow may retain all the right information but require a cook to open several views to find it. Ask the person doing the demo to show the ordinary working view first, then any detail screen needed to understand the order. Check whether an active ticket can still be recognized by its order identifier and type.
A whole-ticket-only workflow may be enough if one person prepares and releases every item together, or if the kitchen deliberately uses a reliable separate method to track individual dishes. It becomes a weaker fit when separate stations finish at different times and expo depends on the screen to coordinate them. The decision boundary is whether staff can tell, at the point of work, exactly what remains without relying on memory.
Fleksa’s kitchen display software presents restaurant order information, including item names, quantities and modifiers. Ask for a demonstration of the item-status behavior and views needed for your setup rather than assuming that the information shown also provides the completion control you want.
Test remaining items on station and expo views
First ask the vendor to set up a supported training environment. Use simulated orders only, with no real payment, guest message or courier dispatch. Have the people who would actually use the screens take turns as the salad cook, the other cooks and expo. A vendor can demonstrate the controls, but the staff should try the steps themselves.
- Enter the three-item order and confirm that each participant can find the items they are responsible for. Note what expo sees before any food is ready.
- Mark only the salad ready. Without giving the other participants a verbal update, ask each one to describe the order from their own view.
- Check that the burger and pasta are still identifiable as open. Ask expo which item is ready and which two are outstanding.
- Finish the remaining items one at a time. Observe whether the order stays easy to find and how the final completion or handoff is recorded.
- Repeat with a modifier and with a quantity greater than one. Check whether staff can distinguish the modified item and understand what has and has not been completed.
Do not treat a colored ticket alone as proof that the workflow works. Ask what each color or indicator means, whether it changes with time or item status, and what happens when multiple conditions apply. A cook should be able to identify the remaining work without interpreting an ambiguous signal.
Station routing is a separate buying question: an item can have a useful status but still appear in the wrong place for your team. Use the guide to routing kitchen tickets by preparation station to prepare that part of the demo. For this decision, concentrate on what happens to the unfinished items after one item is marked ready.
After the simulation, write down any extra steps, required screens and staff roles. Ask whether the quoted setup includes those screens and whether there are extra charges. A cheap quote for a setup that leaves expo without the necessary view is not a comparable quote. Also ask how the display fits with your broader restaurant management workflow and which order details carry through.
Only after staff can perform the simulation should you consider a supervised live service pilot. Choose a manageable service period, assign a lead to watch the workflow, and agree on a fallback before taking live orders. The pilot uses real service; it is not the place to discover for the first time what the completion button does.
Set a recovery rule for an early-ready mark
Mistakes are part of the buying test. In the training environment, mark the salad ready before it is actually finished in the scenario. Ask the vendor to show the correction path from the screen where the mistake occurred, then inspect the station and expo views again.
Your acceptance rule can be: the person responsible can identify the mistaken status, correct it or clearly communicate a fallback, and confirm that expo and the station are working from the same understanding. The burger and pasta must remain open throughout. If a correction requires a manager, an extra screen or several taps, record that as part of the workflow rather than treating it as a minor detail.
Do not assume every system offers an undo, recall or reroute control. Ask whether the item can be returned to an open state, who is allowed to do that, and whether the change appears on every relevant view. Also ask what staff should do if the item cannot be reopened. A practical fallback might be an immediate verbal correction to expo and the cook, paired with the kitchen’s existing manual tracking method until the item is finished.
Make the rule specific enough to train: who announces the error, who updates the record if possible, and who confirms the dish is genuinely ready. Check how the team distinguishes a correction from a cancellation or a request to remake food. Those are different actions and should not be inferred from the same accidental tap.
If the demo cannot show a dependable way to keep unfinished items visible and correct an early mark, decide whether your manual fallback is workable during a busy service. If it depends on constant memory or repeated calls between stations, keep looking or change the workflow before buying.
Next step: Bring the worksheet and your own sample order to a demo. Discuss your requirements with Fleksa and compare the demonstrated workflow with your current product fit before committing.
Frequently asked questions
Does item-level completion close the whole ticket?
It should not have to for the workflow described here, but behavior varies by product and setup. Ask the vendor to show whether the other items and the order remain visible after one item is marked ready.
Can a kitchen use whole-ticket completion instead?
Yes, if the team prepares and releases the order together or has a dependable separate way to track individual items. Test that method during a busy workflow rather than assuming staff will remember every partial completion.
What should staff do if an item is marked ready too soon?
Use the system’s correction process if available, then confirm the status with the cook and expo. If there is no suitable correction, follow a predetermined manual fallback so everyone knows the item is still being prepared.
