Set up one shared transaction instead of separate device islands
Check how multiple POS devices work together using one shared transaction rather than separate demonstrations on each device. In BonZumo, table, order, payment, receipt and closing all belong to the same transaction logic. Ask to see on two POS devices how the same open table and outstanding amount appear in your setup, and when a change becomes visible on the second device.
But one practical limit matters: shared transaction logic alone does not answer every detail about parallel changes on multiple devices. Especially when two people work on the same table almost at the same time, you should have your own flow demonstrated: what information is visible on both devices, when the status updates, and how overlaps are handled. Before you decide, do not only have these situations explained. Run through them with your typical service cases.
Assign table areas and workstations by real walking routes
In day-to-day service, reliability often starts less with technology and more with clear routes. If you use multiple terminals, each device should have a recognisable work context: for example terrace, dining room, counter or bar. BonZumo works with a table and area plan, so your team sees the spatial context and does not search for tables only by number. That shortens walking distances and reduces the risk that someone continues on the wrong transaction by mistake.
In practice, that means thinking ahead not only about how many devices you want, but where they will be used and which handovers happen between them. A counter device needs different speed and different favourites than a table-service device. If two servers cover the same area, it matters less that both can do everything than that both can clearly read the same current table status. BonZumo shows the table, open orders and payment context in one shared sales context. Whether your planned number of devices and your layout work cleanly under peak pressure is something you should test in exactly that setup.
How the ideas connect
The opening sections of this article, shown together.
How do you organise multiple POS terminals safely in one venue?
You should enforce shared transaction logic, assign clear areas and define responsibilities before…
Set up one shared transaction instead of separate device islands
Check how multiple [POS](/en/resources/process-driven-pos-for-restaurant-operations/) devices work together using one shared…
Assign table areas and workstations by real walking routes
In day-to-day service, reliability often starts less with technology and more with clear routes. If you use multiple terminals, each…
Separate initial ordering and re-orders cleanly
A typical conflict case is usually not the first order, but the re-order. One server adds two more drinks on one terminal while another person is already thinking about taking payment. BonZumo supports orders in the table context and keeps order items and notes with the transaction. That lets your team see that this is not an isolated ticket, but still an open table whose contents can change.
You should still define internally when a table is considered ready for payment. Otherwise, misunderstandings arise not because of the software, but because of timing. A short team standard helps: before taking payment, the responsible person checks the current table contents and actively asks whether anything is still on the way or has just been added. When you ask for a BonZumo walkthrough, bring exactly this example: device A adds items, device B opens payment almost at the same time. Then you can see whether your team notices the updated status early enough and which working method is least prone to errors.
Treat simultaneous changes as a real stress test
If you want to know whether multiple terminals really work together reliably, a calm demo with one single table is not enough. What matters are the moments when two people want to act in parallel. So do not only ask to see the ideal flow. Deliberately trigger a test case: one device adds items, another splits the bill, a third opens the table again. That is the only way to see whether your team can work safely with the visible status.
Focus on three questions. First: which change does the other device see immediately, and which only after reopening the transaction? Second: what happens if a payment step has already started while someone is still changing the order contents in parallel? Third: who can clearly recognise that a transaction is in a sensitive stage and should not be changed casually? BonZumo links orders, partial payments and the remaining outstanding amount in one shared transaction. Whether parallel handling stays low-risk in your specific setup is something you should have demonstrated explicitly for your planned use.
Check the open table balance deliberately before every payment
Multiple terminals become especially critical once payment starts. At that point, it is no longer only about whether an order is visible, but whether sales amount, tip, partial payment and remaining balance are kept clearly separate. In BonZumo, the table stays open until the outstanding amount is fully settled. That matters in a multi-device setup because your team can see not only that something has already been paid, but also what is still open.
This is particularly helpful for groups when different servers take payments one after another. One person records a partial cash payment, the next later takes a card payment for the rest, and a third still creates a receipt. For that to stay calm, everyone in the venue should understand that payments always start from the current open status and that nobody works from old interim totals. In your test, do not only process one full payment. Also run through splitting by items, equal shares and a remaining balance. You will quickly notice whether your team understands the flow or whether you need stricter responsibility rules.
Decide who is responsible for closing the transaction
Many errors in multi-device situations happen at the final decision: who is actually allowed to close the table? Technically, several people can be involved in one transaction, but organisationally it should still be clear who is responsible for the close. BonZumo keeps authorised actions, receipts and payment information together in the transaction. That makes it easier to connect responsibilities to roles instead of letting everyone do everything.
In practice, that means deciding whether every server may close their own tables or whether split bills and special cases go to a shift lead. This is not only about control. It also reduces pressure on the team. If one person is responsible for the close, everyone else knows that once payment has started, no further order changes should be added unless there is clear coordination. Roles and permissions help you reflect these responsibilities in the system. Which rights you really need depends on how often table handovers, cover situations and spontaneous help between areas happen in your venue.
Use personal access instead of shared device habits
Multiple terminals do not help much if everyone uses them in the same casual way and, in the end, it is unclear who did what. Especially in handovers between service, counter and shift lead, you should take personal access and roles seriously. BonZumo supports different responsibilities through roles and access rights. That is important in a multi-device setup because corrections, voids or certain closing actions should not simply happen on whichever device is closest.
For you, this is also a training issue. Not everyone needs the same depth on every screen. A server mainly needs secure access to the table plan, ordering and payment start. A shift lead also needs visibility on exceptions and follow-up questions. When staff move between devices, the rule should always be: first work under the correct access, then touch the transaction. That prevents a device from being technically available while the person using it has unsuitable rights or no clear area of responsibility.
Assign printing and output points clearly to the transaction
As soon as multiple terminals trigger orders, the link to kitchen or bar stations quickly becomes more important than the pure checkout view. If two devices send orders for the bar and kitchen on the same evening, your team needs to know that the task does not simply belong to the device, but to the correct station and item context. BonZumo supports configured kitchen and bar stations, kitchen displays and printing rules, so open and processed jobs can be tracked in their relevant station context.
This helps especially when a table places a re-order and the second server is not the same person who took the first order. In that situation, the kitchen should not have to guess whether two tickets belong together or whether a drink was ordered twice. So test with your own menu and your own routes which items go to which station and whether the assignment stays just as clear when a re-order comes from the second or third device. The real question is not only: does it print? The real question is: does every station immediately recognise which table and which processing status this job belongs to?
Clarify connection interruptions and resume behaviour in advance
In real service, you also need to know what happens when the connection is interrupted. Mobile devices especially move between terrace, dining room and counter. Whether a specific workstation in your environment keeps working cleanly at all times, how quickly the current status becomes visible again, and which intermediate steps your team should avoid in that situation are things you need to have checked with your planned setup. Do not wait until a busy Friday night to find out.
A simple fallback rule helps more than hectic improvisation. Decide what staff should do if a device is not currently showing a reliable up-to-date status: do not trigger a second payment, do not charge the same open group twice, and re-check the table at one clearly defined workstation. BonZumo keeps transactions, payments and receipt context connected within the system. Whether your devices work together exactly as you need after a short interruption should be practised explicitly in a test that includes reconnection, switching devices and already started payments.
Test your planned number of devices with real shift scenarios
So the real answer to your question is not simply yes or no to multiple terminals. For your venue, check four points in particular: the same table context on all relevant devices, clear responsibilities before and during payment, understandable permissions by role, and a stress test with real parallel cases. BonZumo provides the shared transaction logic around table, order, payment, receipt and roles. Check your specific multi-device setup with two POS devices, a device handover and a payment already in progress; organise responsibilities around the results.
To prepare for a discussion or a test, note down three concrete scenes: two servers at the same open table, switching between two POS devices as well as the separate handoff to the card-payment terminal, and a partial payment while questions are still coming up at the table. Ask to see exactly these flows, not only the standard order. If afterwards you can say who sees which status when, who takes over the close, and how your team reacts to interruptions, then you have a solid basis. If those answers remain open, what is missing is not theory, but a practical multi-device trial with your intended organisation and technology.
Putting it into practice
Later sections put the topic in the context of day-to-day operations.
Assign printing and output points clearly to the transaction
As soon as multiple terminals trigger orders, the link to kitchen or bar stations quickly becomes more important than the pure…
Clarify connection interruptions and resume behaviour in advance
In real service, you also need to know what happens when the connection is interrupted. Mobile devices especially move between terrace,…
Test your planned number of devices with real shift scenarios
So the real answer to your question is not simply yes or no to multiple terminals. For your venue, check four points in particular: the…