Choose the screen by the job it needs to do.

Separate three display roles

Start with the person using the screen. A cook needs the right dishes, quantities and order reference. A guest checking the bill needs the selected items and payable amount. A person waiting for a parcel needs a clear collection reference and reliable instruction about when to approach the counter. One screen should not be assumed to provide all three workflows.

Ask what makes an order appear and disappear

During the demonstration, ask the operator to explain each screen’s selection rules. Does an order appear when it is entered, saved, accepted or sent to the kitchen? What removes it: payment, cancellation, a staff action, a time filter or something else? Record the actual behavior rather than assigning a meaning to a colour or disappearing card.

For DeccanPro, inspect the kitchen display with your proposed ordering and billing sequence. A kitchen order leaving the screen must not automatically be interpreted as food prepared, packed or handed to the guest. Confirm how your installed configuration handles an order paid before cooking, as well as one paid after service. Ask separately for any customer bill display or dedicated pickup-board requirement; those are not established by demonstrating the kitchen display.

Try a paid order that is not ready yet

Use fictional training order P21: two meals at Rs.140 each, an item subtotal of Rs.280 before configured adjustments. Use paper markers for the food and the demonstrator’s agreed test-payment procedure. At the first checkpoint, payment is recorded but neither practice meal is prepared. Ask the cashier and kitchen observer to identify the same saved order and explain what each screen shows.

Move one paper meal marker to the packing position. Only one of two meals is ready in this exercise. Ask who checks the complete order before any collection announcement. If a pickup board is part of the proposed system, demonstrate its actual readiness action and the information the guest sees. If it is not, rehearse the restaurant’s manual call-and-check procedure. A staff decision about readiness is still needed; displaying a paid amount does not establish it.

Finally place both meal markers at packing, check their quantity against P21 and simulate collection by the correct guest. Record three separate facts: payment evidence, both meals checked and actual handover. A single completed label is not enough unless the demonstrator can explain precisely which event it represents. Never run this exercise by creating unplanned real payments or sending test meals into a live kitchen.

Test visibility from the intended position

Place the proposed screen where it will be used and read it from the normal working or waiting position. Try a long dish name, several simultaneous orders and a changed quantity. Check glare, text size and whether important details require another page. A large monitor is not automatically readable if the layout makes every order too small.

Consider what customers can see. A screen facing the dining room should not expose private contact details or internal notes that are unnecessary for the guest’s task. Inspect the actual visible fields with training data. Do not mirror an entire cashier desktop simply because a second monitor is available; confirm the supported display route and what it presents.

Include a stale-screen check

Agree a controlled demo interruption with the installer, away from live service. Check what staff see when the screen cannot refresh, how they notice that its information may be old and how they recover the current order. Keep a fallback way to inspect the saved order rather than re-entering it to make a missing card appear.

For pickup service, nominate the staff role that confirms the parcel at the handover point if the guest-facing display is unavailable. Avoid promising refresh speeds or automatic failover without observing them on the intended equipment. Record the interruption, visible result and successful recovery as separate checks.

Bring a screen plan to your Chennai demo

Sketch the cashier, preparation area, packing point and guest waiting position. Mark which role each proposed screen serves and who changes its state. Bring the monitor connections and device details so the installation can be checked against the actual hardware.

DeccanPro’s Rs.6,000 annual software plan covers its restaurant billing, table orders, captain mobile, KOT printing, kitchen display and voice-announcement workflow, with unlimited use and no setup or hidden software fees. Confirm any additional display workflow and equipment requirement separately. Use the P21 exercise to evaluate the proposed setup before buying screens or printing collection instructions.