Multi-Device POS: Running Your Point of Sale Across Multiple Devices

Why small businesses need multi-device POS

Most small businesses start with a single POS terminal — one counter, one cashier, one device. As the business grows, that single point becomes a bottleneck. A restaurant needs table orders and a bar tab running simultaneously. A retail shop needs a second till at peak hours. A venue needs to process sales from multiple locations at once.

Cloud POS providers solve this easily, but at a cost — many charge per terminal, per month. For a business with three active selling points, that can mean three separate monthly fees on top of the base subscription. For Caribbean small businesses already managing tight margins, that model doesn't hold up.

How multi-device POS works

A browser-based POS system runs on your server and is accessed through any web browser. This means any device with a browser — a tablet on the counter, a laptop at the bar, a phone used for table orders — can access the same POS system simultaneously. Every sale processed on every device is recorded in the same transaction database, in real time.

This is fundamentally different from standalone POS hardware, where each terminal maintains its own separate database that has to be reconciled at end of day. Browser-based POS means one source of truth — all devices read and write to the same data store.

The shared-device problem

Multi-device operation introduces a common operational challenge: staff handover on a shared device. When two cashiers share a tablet across shifts, the outgoing cashier needs to stop selling and the incoming cashier needs to start — but a full logout and re-login disrupts the workflow, especially during busy service.

The same problem applies when a supervisor needs to briefly approve a discount on a cashier's terminal, or when the night shift takes over from the day shift without fully restarting the session. You need a way to switch the active operator quickly without closing everything down.

Why full logout doesn't always work

Full logout forces the incoming user to type an email address and password — which is slow, requires both users to know the login details, and can leave shifts in an inconsistent state if the previous session wasn't closed correctly. For a busy counter at peak hour, it's simply not practical.

Staff PIN login — the practical solution

The cleanest solution to shared-device handover is a 4-digit PIN system. Each staff member is assigned a unique PIN in the system. When they take over a device, they select their name from the lock screen and enter their PIN — the session switches to their account in under five seconds.

This model is common in hospitality and retail environments where multiple staff share a single terminal across a day. The PIN lock screen shows a grid of staff names — tap your name, enter your PIN, and you're selling. The previous cashier's session is closed, your session opens, and all sales from that point forward are recorded under your account.

Real-time sync across devices

When multiple devices are active at the same time — not just sequentially — the system needs to keep inventory and transaction data consistent across all of them. If Device A processes a sale that depletes stock, Device B needs to know immediately. If Device B voids a transaction, that void needs to be visible in the transaction list on every other device.

A practical approach for browser-based POS is lightweight polling: each device periodically asks the server for a hash of the current data state. When the hash changes — because another device made a sale or updated stock — the polling device silently refreshes its local cache. The cashier sees updated stock levels without any manual refresh.

What gets synced

• Stock levels — product quantities are updated centrally on every sale
• Transaction records — all sales appear in the transaction list regardless of which device processed them
• Voided transactions — a void on one device is reflected immediately across all devices
• Today's sales totals — dashboard figures reflect the combined output of all active devices

Offline operation and sync queues

Multi-device POS faces an additional challenge: what happens when one device loses connectivity? In a Caribbean context — where internet stability is not always guaranteed — a POS system that stops working during an outage is a serious operational risk.

The answer is an offline sale queue. When connectivity is lost, the device continues to process sales and stores them locally. When connectivity is restored, the queued sales are pushed to the server automatically. The cashier never stops selling, and no transactions are lost.

• Sales are queued on-device during outage using browser storage
• Queue is flushed to the server in order when connectivity returns
• Duplicate detection prevents the same offline sale being recorded twice if the device reconnects and retries
• Other devices see the synced transactions appear once the queue has been processed

How CWPOS handles multi-device

CWPOS is browser-based and runs on your own server. Any device with a web browser can access it — there are no per-device licences and no per-terminal fees. A three-till retail setup uses the same installation, the same licence, and the same data store as a single-till setup.

1. Staff PIN setup: Each staff member is assigned a 4-digit PIN in Staff → Edit. The lock screen appears when a cashier taps "Lock Screen" in the sidebar — no full logout required.
2. Device sync: Each active device polls the server every 8 seconds. When another device makes a sale, the stock cache updates silently across all devices.
3. Offline queue: Sales made during connectivity loss are queued locally and synced automatically when the connection returns. Duplicate checking prevents double-counting.
4. Shift attribution: Each sale is recorded against the cashier who processed it, regardless of which physical device was used. End-of-shift reports show per-cashier totals.

Related: Self-hosted POS software — what CWPOS is and who it's for · Business finance software with no subscription · Self-hosted accounting for small business