Kitchen and multiple tills: core versus plugins
Orders need to reach the kitchen, several tills need to recognise each other, and data needs to match up once the network is back. Core kitchen tasks are included in this item; LAN terminal registration and data sync status are viewed in the back office. Overview by category: home page; order intake: Ordering and tables.
What is included
This item covers: core kitchen task creation, order routing and status updates; receiving customer and platform orders; offline checkout, data sync, terminal registration, multi-till checkout lock and recovery after faults.
How far offline checkout goes is explained under “Data sync” below.
Core kitchen tasks versus the kitchen display plugin
Core kitchen tasks are created by the system, which also reports their status back. The kitchen display is a plugin, opened from the plugin center: a kitchen display screen is not included in this item. How-tos for kitchen printing and displays are in the guides.
Terminal registration and LAN coordination
Under LAN multi-till / terminal registration in the back office, a new till is registered first and then approved by the store; lost credentials can be recovered here too.
Data sync
The data sync center summarises sync status. Offline checkout does not mean you can stay offline indefinitely without syncing; once you are back online, finish syncing and reconciliation.
Receiving customer and platform orders (boundary)
Orders that come in through customer order entry or from delivery platforms can be viewed under matching entries in the back office. Platform orders go as far as being received and visible.
What to check before you choose
- Do you need a kitchen display? Core kitchen tasks are created and reported back by the system; the kitchen display is a plugin.
- How many tills need to work together? Terminals register on the LAN, and the back office can approve them and recover credentials.
- What if the network is unreliable? After offline checkout you must sync once back online, which you can check in the data sync center; long-term offline running is not promised.
- How far do platform orders need to go? At present they are received and visible, not deeply integrated.
Good fit / less of a fit
Good fit: Stores with several tills that need registration and approval in one place; stores with an occasionally unstable network that need to sync and reconcile afterwards.
Less of a fit: Stores that expect a kitchen display in the core; setups that need to run offline long-term without syncing.
How it fits into a store day
- In the morning a new till has been added to the store, and it is approved in the back office under LAN multi-till / terminal registration.
- At lunch the front of house takes orders, the kitchen cooks from the tasks the system creates, and finished status goes back to the front.
- In the afternoon the network drops for a while and the till keeps taking orders offline; once it is back, check the data sync center to see that syncing has finished.
Out of scope / see also
- Not included: the kitchen display and other plugin-licensed features; plugin marketplace features do not count toward this item.
- Deep delivery-platform integration.
- How to pair terminals and troubleshoot: LAN & terminals guide.
Next steps
- Same channel: Ordering and tables · Members, order centre and after-sales · Inventory and item master data
- How-to: LAN multi-till and terminal registration: how to manage
- Prices: Pricing
- By store type: A day in a table-service restaurant · A day in a cafe or dessert shop