Key takeaways
- “Offline mode” means different things to different vendors. Some keep full trading going, some allow only basic sales, and some stop until the connection returns.
- Order taking, kitchen tickets on the local network and cash sales usually keep working on a hybrid or on-premise system. Online orders, delivery platform orders and remote reports usually pause.
- Card, NETS and QR payments depend on the payment terminal and its own connection, not only on the POS. Ask what your terminal does when your network is down.
- When the connection returns, offline orders sync to the cloud. Ask how the system handles two devices changing the same bill.
- ChaChaCha is a web/hybrid POS that keeps taking orders if the internet drops and syncs later. Ask us to confirm which payment methods work offline with your terminal set-up.
Singapore has good fixed and mobile coverage, but individual outlets still lose their connection. A router fails, a mall network has a bad hour, a contractor next door damages a cable, or a basement unit sits in a weak mobile area. When that happens in the middle of service, staff need to know straight away what still works and what does not.
Our cloud vs traditional POS guide gives a short overview of offline behaviour as one factor among many. This article goes deeper: how the different architectures behave, what typically keeps working and what stops, how syncing works afterwards, how several devices keep working together offline, and how to test it all before your opening day. For the staff steps during an actual outage, see our restaurant emergency plan.
Three types of POS and how each handles an outage
Cloud-only POS
The POS app or browser talks directly to the vendor’s servers for every action. The menu, open bills and transactions live in the cloud. If the connection drops, the terminal may not be able to open a table, add an item or close a bill, because there is nowhere to save it. Some cloud-only systems offer a limited fallback, such as queuing cash sales, but many simply wait for the connection to return.
Hybrid POS with a local cache
The system runs from the cloud but keeps a working copy of the menu, settings and open orders on the device, or on a local hub in the outlet. When the connection drops, it keeps saving orders locally and carries on. When the connection returns, it sends the offline orders to the cloud and picks up any changes made elsewhere. How much keeps working depends on how the vendor built the local layer.
On-premise (traditional) POS
The software and database run on a server or main terminal inside the outlet, and other terminals connect to it over the local network. Losing the internet usually does not stop trading, because the internet was never in the middle of the order flow. What does stop is anything that needs the outside world: remote reports, online orders, delivery platforms and, often, payments. If the local server itself fails, though, every terminal can go down with it.
ChaChaCha is a web/hybrid POS: it keeps taking orders if the internet drops and syncs when the connection comes back.
What typically keeps working and what typically stops
The table below describes typical behaviour. Every product is different, so treat it as a list of things to check, not a promise about any particular system.
| Function | Cloud-only | Hybrid | On-premise |
|---|---|---|---|
| Taking orders and opening tables | Often stops or is limited | Usually continues | Usually continues |
| Kitchen printers and KDS on the local network | Depends on the vendor | Often continues if routed locally; check | Usually continues |
| Cloud-routed kitchen printing | Stops | May pause until online; check | Not applicable |
| Cash payments | Depends on the vendor | Usually continues | Usually continues |
| Card and NETS payments | Depends on the terminal and its own connection (see below) | Depends on the terminal and its own connection (see below) | Depends on the terminal and its own connection (see below) |
| Customer-scanned QR payments | Depends on the customer’s phone and on how payment confirmation reaches the POS | Depends on the customer’s phone and on how payment confirmation reaches the POS | Depends on the customer’s phone and on how payment confirmation reaches the POS |
| QR ordering by guests | Usually pauses if the outlet’s connection is needed to receive orders | Usually pauses if the outlet’s connection is needed to receive orders | Usually pauses if the outlet’s connection is needed to receive orders |
| Online orders and delivery platforms | Usually pause, because orders cannot reach the outlet | Usually pause, because orders cannot reach the outlet | Usually pause, because orders cannot reach the outlet |
| Loyalty points and stored value | Often need a live connection to check balances; ask how offline redemptions are handled | Often need a live connection to check balances; ask how offline redemptions are handled | Often need a live connection to check balances; ask how offline redemptions are handled |
| Remote reports and head office view | Show data only up to the last sync | Show data only up to the last sync | Show data only up to the last sync |
The practical point is simple: before go-live, write your own version of this table for the system you are buying, with the vendor’s answers, and keep it next to the emergency plan.
Payments when the internet is down
Payments are where offline mode most often surprises people, because the POS is only part of the chain.
Card and NETS
A card or NETS payment needs the terminal to reach the acquirer or network for authorisation. Whether that works when your outlet’s internet is down depends on how the terminal connects. A terminal on your outlet’s Wi-Fi or wired network loses its link along with the POS. A terminal with its own mobile data connection may keep working. For trucks and carts that trade on mobile data all day, see our food truck POS guide. Some terminals and acquirers support deferred or offline authorisation for certain transactions, with conditions and risk that sit with the merchant; others do not. Only your terminal provider or acquirer can tell you what applies to your set-up.
There is a second question: if the terminal can process the card but the POS cannot talk to the terminal in the usual way, how does the payment get recorded against the bill? Ask whether staff should record it manually and how it is matched later.
PayNow and other QR payments
With a customer-scanned QR code, the customer’s phone makes the payment using its own mobile data, so the customer side usually works. The problem is on your side: a dynamic QR generated per bill may need a connection to create, and the confirmation that the payment arrived usually needs to reach your POS or your banking app. Staff should not accept a screenshot of a “payment sent” screen as proof. Agree a fallback in advance, such as checking the business account on a manager’s phone with mobile data.
ChaChaCha supports PayNow, PayLah!, NETS, Visa, Mastercard and GrabPay through DBS, UOB and 2C2P. Which of these work during an outage depends on the terminal and acquirer set-up, so ask us to confirm for your outlet. See POS payments and our guide to payment terminals in Singapore.
Online orders, QR ordering and delivery during an outage
Any order that starts outside your outlet needs a connection to reach you. That includes delivery platform orders, your own online ordering page and, in most set-ups, QR ordering from guests’ phones.
- Delivery platforms. If the outlet cannot receive orders, the platform may still accept them from customers. Know how to pause your store on each platform from a phone with mobile data, so you do not collect orders you cannot see.
- Own online ordering. Decide whether to pause ordering or switch to a longer preparation time until the connection is back.
- QR ordering at tables. Guests may still be able to place orders from their phones, but those orders may not reach the kitchen. Have staff ready to take orders at the table or counter instead, and put a simple sign on tables if the outage lasts.
For how GrabFood and your own delivery orders flow into the POS normally, see delivery integration.
Syncing and conflicts when the connection returns
When a hybrid system reconnects, it sends the orders, payments and changes made offline to the cloud. Most of the time this happens in the background and nobody notices. The questions worth asking are about the edge cases:
- Order numbering. Do offline orders keep a unique number, or can two devices issue the same one?
- Same bill, two devices. If one staff member adds a drink on the counter terminal while another splits the same bill on a handheld, which change wins? Is anything lost, and is the conflict flagged?
- Menu and price changes. If head office changed a price during the outage, does the outlet sell at the old price until it syncs? Most do, which is usually fine, but you should know.
- Stock and loyalty. Are stock deductions, loyalty points and stored-value balances updated after sync, and in what order?
- Reports. Do offline sales land on the correct date and shift, even if they sync after the day was closed?
- Failures. If a record fails to sync, where does it show, and who is alerted?
A good rule during any outage: avoid closing the day or running end-of-day until the system has synced, so your POS reports include every sale. Our guide to POS reports explained covers the end-of-day routine.
Several devices working together offline
Most outlets run more than one device: a counter terminal, handheld ordering tablets, kitchen printers or a kitchen display system, and perhaps a self-order kiosk. Offline, the question is whether these can still talk to each other.
Losing the internet is not the same as losing the local network. If your router is still powered and your internet line alone has dropped, devices on the same Wi-Fi or wired network can usually still reach each other. If the router itself has failed, the local network is gone too, and each device is on its own.
Ask the vendor:
- Do handheld orders reach the kitchen printer or KDS when the internet is down but the local network is up?
- Do orders sent from one terminal show on the others offline, or only after sync?
- Is there a main device that the others depend on? What happens if that device is switched off?
Two practical measures help. Put the router, network switch and any local hub on a small UPS so a brief power blip does not take down the network. And label every network device so staff can restart the right one.
Backup internet: 4G and 5G routers
Many outlets add a second connection so the POS rarely needs offline mode at all. Common options are a mobile router with a data SIM, a router with automatic failover to mobile data when the fixed line drops, or simply a manager’s phone hotspot as a last resort.
- Test signal where the router will sit. Basement and mall-interior units can have weak reception; try more than one telco.
- Automatic failover is better than manual. Staff in the middle of service will not remember to switch networks.
- Put payment terminals on the backup too, or give them their own mobile connection, otherwise the POS may be online while card payments are not.
- Check data usage. POS traffic is usually modest, but kiosks, cameras and music streaming on the same connection are not.
- Keep the guest Wi-Fi separate from the POS network, for both speed and security.
Check the plan and router with your telco or IT provider, since coverage and pricing vary by location and plan. For the wider set-up, see our guide to restaurant networks for POS, printers and QR ordering.
Test offline mode before go-live
Do not wait for a real outage to find out how your system behaves. During setup or soft opening, run a short test with real devices and staff:
- Unplug the internet line from the router (leave the router on). Open a table, add items with modifiers, send to the kitchen and check that tickets print or appear on the KDS.
- Take a cash payment and a split payment. Try a card and a QR payment and note exactly what happens.
- Take an order on a handheld and check it appears on the counter terminal.
- Edit the same bill from two devices and note the result.
- Try a loyalty redemption or voucher.
- Now switch off the router entirely and repeat the key steps.
- Reconnect. Check that every order, payment and void appears in the back office, on the right date, with the right staff name.
- Check delivery and online ordering: how do you pause and resume them?
Write the results on one page and add them to your staff training and emergency plan. Repeat the test after major updates or when you add new hardware.
Questions to ask every POS vendor
| Question | Why it matters |
|---|---|
| What exactly keeps working when the internet drops but the local network is up? | This is the most common outage. |
| What keeps working if the router itself fails? | Tells you whether devices can trade independently. |
| Which payment methods work offline with the terminal you supply? | Payments depend on the terminal and acquirer, not only the POS. |
| How long can the system run offline, and is there a limit on stored orders? | A long outage on a busy day can be many hours. |
| How are conflicts handled when two devices edit the same bill? | Avoids lost items and double charges. |
| How are offline sales dated and assigned to shifts after sync? | Keeps end-of-day reports and reconciliation correct. |
| How are loyalty, stored value and stock handled offline? | These balances can be over-used if not checked. |
| How do staff know the system is offline, and when sync is complete? | A clear indicator prevents early closing and confusion. |
| Can you show us an offline test during the demo? | A demonstration is worth more than a feature list. |
Get the answers in writing from each vendor, including us. Our POS buying checklist covers the rest of the evaluation, and if you want to see ChaChaCha’s offline behaviour on your own set-up, contact us to arrange a demo. For an overview of the system by business type, see our restaurant POS and cafe POS pages.