Before trusting kitchen screens for service, verify three things: the right screens are active and assigned to the right stations, a representative order reaches those stations with the details cooks need, and someone has acknowledged each ticket. If any required check fails, use the agreed fallback until the shift lead can verify a fix.
A glowing display alone is not a pass. A ticket can appear at one station while another never receives its portion, or a cook can see an item without the modifier that changes how it should be prepared. The opening decision is whether the whole workflow is ready, not simply whether the hardware turns on.
1. Inventory screens and station assignments
Start with the service plan. The shift lead should identify which physical screens are in use, which preparation stations need tickets and who is covering each station. A screen count and a station count are different: one display might serve two stations, while a single station might have more than one display. Confirm the arrangement your restaurant actually intends to use.
Use the current station assignment list as the expected input. Walk the kitchen and compare it with the screen names, locations and staff assignments you can observe. Ask the person responsible for the restaurant POS system to confirm which menu items should go to each station and which order types are included. Do not assume yesterday's assignment still applies after a schedule or menu change.
- List each screen required for the shift and confirm it is on, readable and reachable from the workstation.
- Match each display to its intended station and identify the cook or other staff member responsible for watching it.
- Confirm the expected route for a mixed order, including items prepared at different stations and any modifier that changes preparation.
- Agree on who watches for missing tickets and who can authorize a switch to the fallback.
Record what you actually saw separately from what you expect. For example, “grill screen is on” is an observation. “All grill items will arrive here” remains an expectation until the order check confirms the route. The guide to routing tickets by preparation station can help you prepare the assignment list.
2. Send one representative order safely
Use a vendor-supported training environment for the opening simulation. Confirm with the vendor that the exercise cannot create a real payment, send a guest message or dispatch a courier. A practice order should not become a real order merely because someone selected the wrong environment. If that isolation cannot be confirmed, do not run the simulation; use the agreed fallback and arrange a safe demonstration with the vendor.
Choose an order that exercises the routes you need for the shift. Include an item for each critical station, a quantity greater than one where useful, and a modifier that a cook must see. Tell staff the expected result before sending it. Then compare the actual display at each station with the original order, rather than asking only whether a ticket appeared somewhere.
The following worksheet is hypothetical. Assume a restaurant has two required screens, one for grill and one for cold prep. The simulated order contains two burgers with a no-onion modifier and one salad. The expected route is burgers and modifier to grill, salad to cold prep. The shift lead has decided both screens and both acknowledgments are required before normal screen-only service.
| Check | Pass outcome | Fail outcome | Decision |
|---|---|---|---|
| Station routing | Grill receives the burgers; cold prep receives the salad. | Only grill receives a ticket. | Do not use screens alone if a required station is missing its ticket. |
| Ticket details | Grill shows quantity two and no onion; cold prep shows one salad. | Both tickets appear, but the modifier is absent at grill. | Use the fallback until the required details can be verified. |
| Staff acknowledgment | Both assigned staff members confirm their own ticket and details. | The lead sees both tickets, but cold prep does not acknowledge its ticket. | Resolve the coverage issue and repeat the check before relying on the workflow. |
The table separates delivery, usable content and human acknowledgment. In the first outcome, all three checks pass, so the lead can authorize the screen workflow under the stated assumptions. In the second, a missing ticket, missing modifier or unacknowledged station changes the decision: the team uses its fallback rather than treating a partial result as a pass.
Ask vendors to demonstrate the same order and expected routes. Fleksa's kitchen display system is linked to restaurant orders; its public product information describes item names, quantities, modifiers and order types on the display. Confirm the behavior and setup for your own stations rather than assuming a demonstration configuration matches your kitchen.
3. Check visibility, acknowledgment and the failure path
During the simulation, the assigned cook at each station should read back the item and relevant modifier from that station's screen. The shift lead compares those responses with the original test order. This prevents a misleading pass in which the lead sees a ticket on one display and assumes every cook has received the right information.
Also check whether the ticket is practical to use from the normal working position. Can the cook identify the quantity and preparation instruction without leaving the station or guessing? If a screen is on but unreadable because of its location or glare, record that as an operational failure. A technically delivered ticket is not useful if the assigned person cannot reliably read it.
Run a failure discussion before service, even if the normal simulation passes. Ask the vendor to show what staff would see when a required screen or connection is unavailable, using a safe training scenario. Do not assume every system can reroute, recall or handle a cancellation in the same way. Ask what the operator must do, which details remain visible and how the team confirms that each station has the complete order.
Name the detector and the decision-maker. A station cook can report a missing or unreadable ticket; the shift lead decides whether to stop using screens alone. The lead should tell every affected station when the fallback starts and identify one person to reconcile incoming orders across stations. That handoff matters: two competing sources can create duplicate preparation just as easily as a missing screen can hide an item.
A fallback could be the restaurant's established paper-ticket or written-order procedure, if staff have the equipment and training to use it. Define where the order originates, who distributes each station's instructions and how the team checks modifiers. Do not assume a printer or another device will work without checking it. If the fallback cannot cover a required station, escalate before accepting orders under that workflow.
4. Set the pass, record exceptions and authorize service
Write the acceptance criteria before a vendor demonstration or shift check. For the hypothetical two-station order above, a pass requires both screens to receive their assigned items, the grill ticket to show two burgers and the no-onion modifier, the cold-prep ticket to show one salad, and both assigned staff members to acknowledge their own tickets. Any missing element is a fail, even if the vendor can explain what probably happened.
Give the exception an owner. The shift lead records the screen or station affected, the expected and observed result, the time, the fallback in use and the person responsible for follow-up. The person handling the setup can investigate; the lead remains responsible for the service decision. After a correction, repeat the representative check rather than assuming the change worked.
For a buying demonstration, add these questions to the same scorecard:
- Can you show our required station assignments and the expected route for a mixed order?
- Can each assigned person see the item, quantity and preparation modifier they need?
- How does the system indicate ticket timing, and can those indications be configured for our workflow?
- What happens when a required display or connection is unavailable, and what must our staff do next?
- Can we safely repeat this test in a training environment without a payment, guest message or courier dispatch?
- What hardware, setup work and additional screen costs would our written quote include?
Keep the demonstration and a live service pilot separate. A simulation checks the workflow without affecting guests. If it passes and you decide to proceed, a supervised service period lets the lead watch real orders and use the agreed fallback if a problem appears. It does not eliminate the need for staff coverage or exception handling.
Compare your requirements with Fleksa's order-management workflow, then ask Fleksa to demonstrate your representative order and confirm current support for your stations before choosing a workflow.
Frequently asked questions
How often should a kitchen check its display system?
Check the screens, assignments and staff coverage before each service. Repeat the representative simulation when the setup or staffing changes, using a vendor-supported training environment that cannot affect guests.
Is a ticket on one screen enough to pass?
No. A pass should cover every required station, the necessary item details and acknowledgment by the assigned staff. A mixed order is useful because it can expose a missing route.
What should staff do if a screen check fails?
Tell the shift lead, record the failure and use the agreed fallback. After the issue is addressed, repeat the relevant check before returning to the screen-only workflow.
