Every venue eventually loses internet mid-service: a router reboot, an ISP outage, a busy night overwhelming shared Wi-Fi. The question that actually matters isn't whether it'll happen, it's what your POS does when it does.
What "offline-first" means in practice
A lot of systems marketed as "cloud POS" simply stop working without a live connection to their servers. NUA is built the other way around: the terminal itself can take an order, fire it to the kitchen, and process a payment without needing to reach the cloud in that moment.
What keeps running
- Order taking and modification at the terminal
- Kitchen display routing over the local network
- Payment authorisation, where the connected processor supports offline auth
- Tab and table management
What catches up once you're back online
Cloud-dependent features (cross-venue reporting, AI recommendations that need broader data, loyalty sync) pick back up automatically the moment connectivity returns, along with every order and transaction that happened while offline.
Why this is a design decision, not a lucky feature
Building offline-first is harder than building cloud-only. It means the terminal has to be a real system in its own right, not just a thin client. It's a deliberate trade-off, made because a frozen kitchen screen mid-Friday-night-service is a worse outcome than slightly more engineering complexity.
A dropped connection at a competitor's cloud-only terminal can mean a manual paper backup process. At a NUA terminal, it's a sync delay nobody at the table even notices.