Start with one table and a real menu
A waiter selects the table, enters two mains and adds a kitchen note. The POS records the order, and the kitchen screen or printer receives the relevant lines. Identify the order and table on both sides. Decide whether drinks, grill and preparation stations need different routing; a one-station demo does not prove that your real layout will work.
Define what happens when the order changes
Add a side and cancel a main after the first send. The kitchen should know whether it is seeing a new instruction or a full order reprint. Agree a rule for cancelled items and who can authorize them. Avoid counting a reprint as a new order. When the order moves tables, check that the waiter, kitchen and cashier can still identify the same order.
Follow the bill through payment and reset
Print a provisional bill, then complete payment and check the final invoice and shift totals. Verify that opening the table again creates a fresh order, rather than carrying forward an old ticket. Test a split bill, a failed payment and a refund if they are part of your service. Compare cash and card totals to the cashier report.
Pilot during a real shift
Choose one branch or section. Set a fallback for a printer or network outage, assign someone to handle exceptions, and record which order scenarios passed. Ask staff where they still copy data or walk a ticket to the kitchen. Fix that handoff before rolling out more tablets or stations.
What should a restaurant POS demo prove?
It should show a full table lifecycle including a modified order, the kitchen record, payment, the final invoice and a clean table reset.
