What does an offline restaurant POS mean?
An offline restaurant POS can take orders, print tickets, send them to the kitchen and complete cash sales with no internet connection, because the software and the menu run on hardware inside the restaurant rather than in a data centre. When connectivity returns, the queued orders sync to the cloud without duplicating or losing any of them.
The phrase is worth pinning down, because vendors use it for two very different things. Ask which one you are being sold:
- Offline mode — a cloud POS that caches recent data in the browser and lets you keep ringing sales for a while. It typically cannot reach the kitchen display, cannot see the full menu, and reconciles awkwardly.
- Offline-first — the store holds the authoritative copy while service is running. Every station talks to local hardware, and the cloud is a downstream consumer. Losing the connection changes nothing about how orders flow.
ThaliPOS is the second one.
How it works in your store
One small hub sits in the back of the restaurant. It holds your menu and your orders, and it fans them out to every screen over your local network.
- The back office publishes your menu to the hub as a signed snapshot. The hub keeps it, so the menu is on-site, not fetched per order.
- A guest orders at the counter, the kiosk, or on their phone via QR. That order is written to durable storage on the hub and given an id minted in the store.
- The hub pushes it to the kitchen display and the printers immediately — over your LAN, with no round trip to the internet.
- Whenever the connection is available, the hub forwards orders to the cloud. Because the id was minted in the store, a replay after a reconnect is recognised as the same order and lands exactly once.
The in-store clients are deliberately simple: they talk only to the hub, never to the cloud. That is enforced automatically in our build — a client that tried to call the internet directly would fail the check before it could ship.
What still needs the internet — honestly
Card payments
The card networks, not usAuthorising a card requires reaching the issuer. No POS can change that. Cash tenders are unaffected and reconcile normally at close.
New delivery-app orders
Auto-pausedIf the store cannot be reached, marketplace channels are paused automatically rather than accepting orders nobody can see. They resume when you are back.
New online and QR orders
Guests off-siteOrders placed from outside the restaurant travel over the internet by definition. In-store QR ordering on your own network is unaffected.
AI features
Cloud-side by designThe assistant and menu import run in the cloud. Unavailable during an outage, and irrelevant to service.
Everything else — counter POS, kiosk, kitchen display, printing, cash, weigh-and-pay, barcode scanning, order board — keeps running.
How we test it
Offline resilience is a claim that is easy to make and easy to quietly break. ThaliPOS runs an automated chaos test on every release: it severs the store's connection to the cloud, drives real orders through the store, restores the connection, and asserts that every order arrives in the cloud exactly once — no duplicates, no losses.
If that test fails, the release does not go out. It is the reason we are willing to put "never stops taking orders" on the front page.
Who needs this most
Any restaurant whose connection is not genuinely reliable — older buildings, shared retail connections, food courts, festival and event trading, and anywhere a single provider outage takes the whole street down.
And any restaurant where the busiest two hours of the week are the ones you cannot afford to lose. An outage at 3pm on a Tuesday is an annoyance. The same outage at 7:30 on a Friday is the week.