Map a real service before configuring screens
Write down how an order arrives, who accepts it, where it is prepared, how it is paid for and who closes the shift. Include dine-in, takeaway and delivery only where they apply to your restaurant.
Use that map to decide which stations need a device or printer. A kitchen route should follow the team that prepares the item. Adding more screens without agreeing on handoffs can make a simple service harder to manage.
- List outlets, floors, tables, cashier points and preparation stations.
- Identify peak-service roles and the manager responsible for each shift.
- Document split bills, transfers, discounts, voids and refund approval steps.
- List external systems and ask which connections need a separate scope.
Check equipment and the local network
Confirm the exact supported hardware and operating systems with the implementation team. Test printer positions, cables, power and wireless coverage where staff will actually use the devices.
Distinguish the local network from the internet connection. A local workflow may continue during an internet interruption while a cloud report, external integration or payment service still depends on connectivity.
- Cashier and steward devices are charged, configured and assigned.
- Each printer and display can be reached from its intended station.
- Backup power and an interruption procedure are agreed for essential equipment.
- Supported offline behavior and later synchronization are demonstrated.
Run a service rehearsal with the actual team
Use practice transactions rather than customer payments for the rehearsal. Ask a waiter, kitchen team member, cashier and manager to perform their own steps so missing permissions and unclear handoffs become visible.
Test the exceptions as well as a normal sale. Record who fixes each issue, then repeat the failed scenario before accepting the setup.
| Scenario | What to confirm |
|---|---|
| Order with modifiers | Extras and preparation notes reach the correct kitchen station. |
| Second round or table transfer | The order stays with the intended table and bill. |
| Split payment and authorized void | Receipts, totals and approval records match the agreed workflow. |
| Internet interruption | Supported local tasks continue; dependent online services are clearly identified. |
| Shift close | The cashier and manager can reconcile sales, payments and exceptions. |
Agree on opening-day support and handover
Choose a rollout window that gives staff time to rehearse. Agree who approves the final menu, opening stock and access permissions, and how the team will contact support during the first service.
Before handover, record the configured equipment, outstanding work, support coverage and process for requesting changes. For several outlets, review the first rollout before repeating the configuration elsewhere.
- Named restaurant owner or manager for final acceptance.
- Training completed for each role, including new-staff handover notes.
- Verified support contact, coverage and escalation process.
- A documented way to handle an equipment or connectivity interruption.
Questions before you choose
How long does a POS installation take?
The timeline depends on data readiness, equipment, outlets, training and integration work. Agree on a schedule after those items have been reviewed; a universal installation time would be misleading.
Should all branches launch at once?
A pilot can help you check menu data, permissions, reporting and training before a wider rollout. Choose the rollout approach with your operations and implementation teams.
What should we test if internet access is unreliable?
Demonstrate the supported offline ordering, billing and printing workflow, plus the recovery and synchronization process. Check payment providers and external integrations separately because their connectivity requirements can differ.
Bring your own workflow to the demo.
Tell us about your outlets, menu, service stations and existing equipment. We can review the setup and put the proposed scope in writing.