Home › Blog › Running Two iPads on One Till: Shared Registers for a Busy Café

Running Two iPads on One Till: Shared Registers for a Busy Café

10 Jul 2026 • 9 min read

There comes a point in a growing café where one iPad POS at the counter isn't enough. The queue backs up at peak, or you open a second service point, or the kitchen wants its own screen. Adding another iPad sounds simple — until you try to count the cash drawer at close and the numbers don't add up. This is the problem a shared register solves.

Why one POS isn't enough

A single till is a bottleneck the moment two things happen at once: a long queue and a staff member who needs to ring something up elsewhere. Common triggers for a second iPad:

• Peak-hour queues — two people ringing up in parallel halves the wait.
• A second service point — a takeaway window plus the main counter.
• Dine-in floor service — staff taking orders at tables on a roaming iPad.
• A kitchen display — a screen on the pass, separate from the till (see Kitchen Display).

Adding the hardware is easy. The hard part is the money.

The reconciliation trap

Most POS systems tie a register shift (the open-count, the takings, the close-count) to a single device. That's fine with one iPad. But put two iPads on the same physical cash drawer and each one opens its own shift with its own starting float — and now you have two shifts trying to account for one drawer. At close, neither balances, because cash went into the drawer from sales rung on both devices while each shift only knows about its own.

Operators usually "solve" this by nominating one iPad as the only cash till and making the others card-only, or by doing painful manual maths at close. Both are workarounds for a POS that wasn't built for more than one terminal per drawer.

What a shared register is

A shared register flips the model: the shift belongs to the drawer, not the device. Multiple iPads join one shift over one cash drawer, and every sale — from any joined iPad, in any payment type — rolls up to that single shift. At close, you count the drawer once and it reconciles against the combined takings of every device.

How it works, in practice

1. Open — the first iPad opens the shift with the starting float. That shift is registered to the server, not just the device.
2. Join — the second (and third) iPad joins the same open shift instead of starting its own. Now they share one drawer's books.
3. Sell — every sale on every joined iPad contributes to the shared shift's running totals, by payment type.
4. Close — closing uses server-wide sums across all devices, so the expected cash reflects everything that happened on the drawer. You count once; the variance is real, not an artefact of split shifts.

Cash handling with one drawer

Physically, one drawer means one person is ultimately responsible for it — that doesn't change. What changes is that the POS now knows every device is feeding that drawer, so pay-ins, pay-outs (float adjustments, paying a supplier from the till) and the final count all sit in one place. If you genuinely run two separate drawers, you'd run two shifts — the point is that the system should match your physical setup, not force it.

The kitchen-iPad guard

A subtle trap: if you add a second iPad purely as a Kitchen Display, you don't want someone accidentally opening a cash shift on it. A well-designed shared-register flow guards against this — a device meant to be a KDS shouldn't quietly start its own drawer shift and desync your books. Small detail, big difference at close.

Offline behaviour

Multi-device only helps if it survives a Wi-Fi wobble. The shift state and its running totals should hold up when the connection drops and reconcile when it returns, so a blip mid-service doesn't strand one iPad with numbers the others can't see. (More on why this matters in why your POS must work offline.)

When to use it — and when not

• Use a shared register when multiple iPads take payment into one drawer — the classic busy-counter or counter-plus-window setup.
• Use separate shifts when each iPad has its own physical drawer and its own cashier responsible for it.
• No drawer at all (fully cashless / PayNow-only) — reconciliation is simpler either way, but shared totals still give you one clean shift report.

How Shopways does it

Shopways supports multiple iPads on one drawer: the first opens the shift, the others join it, and closing uses server-wide sums across every device so the drawer reconciles in one count. It includes the kitchen-iPad guard so a display device doesn't accidentally open a cash shift, and the shift state is resilient to connection drops. It's part of running a real floor on iPads you already own — see the restaurant POS guide and best restaurant POS for 2026 for the wider picture.

Frequently asked questions

Can two iPads really share one cash drawer and still balance?

Yes — with a shared register, both join one shift and closing uses combined server-wide totals, so you count the drawer once and it reconciles across every device.

What if I add an iPad just as a kitchen display?

It shouldn't open a cash shift. Shopways guards a display device from accidentally starting its own drawer shift, which would otherwise desync your close.

Does it keep working if the internet drops?

The shift and its running totals are built to survive a connection drop and reconcile on reconnect, so a Wi-Fi blip doesn't strand a device or break the close.

Do I need separate shifts if each iPad has its own drawer?

Yes. Shared registers are for multiple devices on ONE drawer. Separate physical drawers should run separate shifts, each with its own responsible cashier.

← Back to all articles