Offline vs Cloud POS: What Happens When the Internet Goes Down?

Every shop eventually loses its internet connection — a router fails, the provider has an outage, or a contractor cuts a cable down the street. What happens next depends almost entirely on where your POS keeps its data.

This guide compares cloud-first and offline-first (local) POS architectures, explains what each can and cannot do during an outage — including the important limits on card payments — and shows how to make either setup more resilient.

Two architectures, explained

A cloud-first POS stores the master database on the vendor’s servers. The till — often a tablet or browser — is a window onto that database, so most actions require a connection. Many cloud systems add an “offline mode” that caches some data and queues transactions until the connection returns.

An offline-first (local) POS stores the master database on a computer inside the business. Tills, scanners and printers talk to that computer directly or over the store’s local network. The internet is used for optional tasks such as software updates, licence activation, remote features or integrations.

What happens during an internet outage

Example: a grocery store’s connection drops at 5 pm on a Friday. With a local POS, the two tills keep scanning and the stock count stays accurate. With a cloud POS in offline mode, both tills continue selling from their caches, but stock levels only reconcile once the connection returns — so two cashiers can sell the last unit of the same item.

The card-payment limitation nobody mentions

Here is the part that applies to both architectures: a card payment cannot be authorised by the bank without a connection. Whether your POS is cloud or local, card acceptance during an outage is decided by your payment terminal and provider, not by the POS software.

Some providers offer a “store and forward” offline mode. The terminal records the card details securely and submits them once the connection returns. Providers are clear about the trade-off:

• Stripe’s Terminal documentation explains that offline payments are only authorised after the reader reconnects, and that the merchant assumes the risk of declines.
• Square’s help centre states that offline payments must be uploaded within a time limit (24 hours in the US for many readers) or they expire, and that declined offline payments cannot be recovered by Square.
• Both providers allow limits on the value of offline transactions, which is a sensible control.

Why a local database is more resilient

An offline-first system removes the internet from the critical path. That has three practical benefits:

• No waiting: product lookups and sales do not depend on a round trip to a remote server.
• No reconciliation surprises: stock updates immediately, even with several tills, because they all share one database on the local network.
• Data on your premises: you decide where the computer sits and how it is backed up.

The trade-off is responsibility. If the main computer fails, the store is affected until it is replaced or restored — which is why backups and a recovery plan are essential. Our multi-terminal setup guide covers this in detail, and the offline POS page explains how Poskio applies this design.

Backups: the other half of reliability

Cloud vendors back up their servers; with a local POS, backups are your job — ideally automated. A widely recommended approach is the 3-2-1 rule:

• 3 copies of your data (the live database plus two backups);
• 2 different types of storage (for example an external drive and a cloud folder);
• 1 copy kept off-site.

Equally important: test a restore. A backup you have never restored is a hope, not a plan. Schedule backups daily after closing and keep at least one copy that is not permanently connected to the POS computer, so ransomware or a power surge cannot reach it.

Hybrid setups: the best of both?

The line between the two models is not absolute. Some cloud products cache enough data to sell for hours offline, and some local products offer optional internet features such as remote reporting, automated report delivery or online assistants. When you compare products, ask two precise questions rather than accepting the label “cloud” or “offline”:

1. Which functions keep working with no internet at all — sales, stock, receipts, multiple tills, reports?
2. Which functions require the internet — and what happens to them during an outage?

The answers matter more than the marketing category. A local POS whose optional online features pause during an outage is still fully usable at the counter; a cloud POS whose offline mode cannot apply discounts or look up customers may leave staff improvising.

An outage procedure your staff can follow

Print this and keep it at the counter. In a stressful moment, a written procedure prevents improvisation:

1. Confirm the outage: check the router lights and whether other devices are online.
2. Keep selling: continue ringing up sales as normal on the POS.
3. Cash: accept cash as usual and keep the drawer count accurate.
4. Cards: follow the payment provider’s offline instructions and respect the maximum offline amount set by the manager. Above that limit, ask for another payment method.
5. Record: note the time the outage started and any offline card payments.
6. Escalate: contact the internet provider and switch on the backup hotspot if available.
7. Recover: once online, upload offline card payments immediately and check that none were declined.

Questions to ask about any POS offline mode

• Can I complete a full sale, including discounts and customer selection, offline?
• Do stock levels update immediately, or only after reconnection?
• Can several tills keep selling together without the internet?
• Are reports available during an outage?
• How long can the system run offline, and is there any limit on the number of sales?
• What happens to card payments taken offline, and who bears the risk of declines?

Reliability checklist for either architecture

• Put the main computer, router and switch on a UPS (battery backup).
• Use wired Ethernet for fixed tills; reserve Wi-Fi for mobile devices.
• Keep a 4G/5G hotspot or backup line for card payments and updates.
• Know your payment provider’s offline limits and set a maximum offline amount.
• Automate daily backups and test a restore every quarter.
• Keep a printed “outage procedure” at the counter: who to call, what to accept, how to record.
• Keep a small cash float so cash sales can continue smoothly.

Offline vs cloud POS: summary comparison

Which should you choose?

Choose offline-first if internet reliability is a concern, speed at the till matters, or you prefer to keep data on site. Choose cloud-first if you manage several locations remotely and your connections are dependable. In both cases, plan for card payments during outages separately. For the full selection process, see how to choose a POS system.

Frequently asked questions

Related guides

• What is a POS system?
• Multi-terminal POS setup
• POS hardware setup checklist
• Offline POS features

Sources and further reading

• Stripe Docs — Collect card payments while offline
• Stripe Support — Terminal offline mode FAQ
• Square Help — Offline payments time limits
• Federal Reserve — Offline payments: implications for reliability and resiliency
• U.S. Chamber of Commerce — The 3-2-1 backup rule