Run several tills at the same venue

Also known as: multi-till, multiple terminals, varias cajas, TPV adicional, handheld waiter, real-time sync, multi-terminal.

A venue can run as many tills as it needs. There's no per-device licensing — each device just signs in to your tenant on a browser. Desktop bar terminals, kitchen prep stations, and waiter handhelds all see the same floor plan, the same open tabs, the same Z report at end of service, all syncing in real time.

Add a second till

1. On the new device, open the browser and go to <your-slug>.brasio.io.
2. Sign in with your venue PIN keypad.
3. The till loads with the current state — open tabs, floor plan, products.
4. Take orders or run cashing actions from there.

There's no separate "add a device" step — any browser that can reach your tenant and pass the PIN keypad is a till.

How real-time sync works

Every till is a client of the central brasio API. Behind the scenes:

• Each till subscribes to Centrifugo, a WebSocket fan-out server.
• Every domain change (line added to a tab, payment made, table seated) fires a database notification.
• The notification reaches Centrifugo and is broadcast to every connected till in milliseconds.
• Each till updates its UI without a refresh.

So if a server adds a beer to Table 5 on the bar terminal, the handheld in the waiter's pocket and the floor plan on the host stand all show it instantly.

Roles and what a till can do

Each device acts based on the role of the employee signed in:

• Server / bar — take orders, fire to kitchen, take payment.
• Manager — everything above, plus voids, refunds, overrides.
• Owner — everything, plus settings, costs, accountant exports.

Each employee carries their role with them — sign in to a different till and the role follows.

Cash drawer per till

Each till that handles cash has its own cash drawer. The cash management screen shows the expected balance for that till — not the whole venue. Each till closes independently:

• One till may close at 16:00 after lunch with its own Z.
• A bar till may close at 02:00 with its own Z.
• Each Z reports per-till totals on top of per-employee.

See Cash management and end-of-service.

Printer per till

Each till has its own default printer (set at the OS level on that device). For multi-printer routing across the venue — bar prints drinks, kitchen prints food — see Route tickets across multiple printers.

Offline behaviour

If a till loses network:

• Tab actions (add line, remove line, fire to kitchen on the local printer) queue locally and replay on reconnect.
• Card payments continue via SumUp's offline mode (if the reader supports it for that merchant).
• Cash payments are blocked — Verifacti must confirm the fiscal record before the drawer opens. This is a hard rule, not a config.

When the till reconnects, the queued actions sync to the server in order, and any conflicts (rare, but possible) raise a manager prompt.

Not working?

• A new till can't sign in: confirm the device is on the same network as the API, and that the venue's URL resolves correctly. A misconfigured DNS or VPN can block the WebSocket.
• A change on one till didn't appear on another: the WebSocket connection dropped. Reload the second till — it'll re-sync from the server and reconnect.
• Two tills show different cash balances for the same drawer: that should never happen — talk to us, this is a sync bug to chase.
• One till is consistently slow: check it's not running on a low-end device (very old tablet). brasio is light, but ancient hardware will struggle.