# Offline Functionality

WCPOS stores your product and customer data in a local database on each device. This means parts of the POS work without an internet connection, while others require connectivity.

## What Works Offline[​](#what-works-offline "Direct link to What Works Offline")

* **Browsing products** — search, filter, and view product details from local data
* **Browsing customers** — look up customer names, emails, and addresses
* **Building a cart** — add items, change quantities, edit prices, and apply POS discounts
* **Applying coupons** — codes validate locally against the coupon list, provided it has been opened on this device while online; the server re-validates when the queued order reaches it
* **Saving an order** — hold or save an order to the device; it joins the outbound queue and lands in WooCommerce when the connection returns
* **Barcode scanning** — scan barcodes to find products in the local database
* **Viewing reports** — the default (offline) report type generates reports from locally stored orders
* **Cash and other recorded payments** — a sale paid with cash or another payment recorded at the till (card on an external terminal, cash on delivery, bank transfer or cheque) completes at the till while the store can't be reached. For these methods the cashier records the payment and nothing has to be confirmed by a server. The receipt keeps the real time and register, and the order syncs when the connection returns

## What Requires a Connection[​](#what-requires-a-connection "Direct link to What Requires a Connection")

* **Integrated card readers and online gateways** — a reader driven from the till, or a gateway that runs on your server, needs both the gateway and your store to be reachable. Take cash, choose **Card** and record a payment taken on an external terminal, or save the order to the device and take the payment once you're back online.
* The **Legacy** tab and **Save to Server** — both need your store to be reachable
* **Syncing data** — pulling new products, updated prices, or new customers from WooCommerce
* **Logging in** — initial authentication requires a connection to your WordPress site
* **Licence activation** — Pro licence checks need to reach the WCPOS licence server
* **Processing refunds** — refunds can't be queued offline; the gateway and your store both need to be reachable (see [Refunds](/orders/refunds.md))

Recorded payments complete offline, integrated readers don't

A sale paid with cash or another payment recorded at the till (card on an external terminal, cash on delivery, bank transfer or cheque) finishes with no connection and syncs later. Payments through an integrated reader or an online gateway still wait for a connection; offline payments through integrated readers are on the [roadmap](/getting-started/roadmap.md).

## How the Local Database Works[​](#how-the-local-database-works "Direct link to How the Local Database Works")

When you first open WCPOS, it seeds your product catalogue in the background and pulls other data as you use it — you can start selling as soon as the first products are on the device. From then on, a background change check (every 60 seconds by default, tunable in [Store health](/support/store-health.md)) fetches only what changed on the server.

The local database:

* **Persists between sessions** — data survives browser restarts and device reboots
* **Is per device (and per cashier)** — each device keeps its own local copy; cashiers don't share local data
* **Stays in sync** — background change checks pull updates; your changes queue locally and push to the server

You can see exactly what's on the device — and what's still waiting to send — in **Store health → Database**. For more technical detail, see [How the Sync Engine Works](/reference/sync-engine.md).

## Changes You Make Offline Are Queued[​](#offline-writes "Direct link to Changes You Make Offline Are Queued")

Every change you make in the POS — a saved order, a new or edited customer, a coupon, a stock or price edit (Pro), a receipt email — is saved to the device first and queued to send. While you're offline the queue simply waits; nothing is lost by losing connectivity mid-shift. The queue is durable across restarts and crashes too: if the app hits an error screen, choosing **Try again** reloads it without discarding sales that haven't been sent yet. Don't [clear local data](/support/troubleshooting/clear-local-data.md) while **changes waiting to send** is above zero: that discards them, and an offline sale is a payment already recorded.

When the connection returns, the queue drains automatically. If your server refuses a change outright (rare — for example, a record the server considers invalid), the POS won't retry it silently forever: the change is parked in **Store health → Database** under *"changes never reached your server"*, with the server's reason and explicit **Send again** / **Discard** actions. See [Store Health](/support/store-health.md#refused-changes).

## Connectivity Indicator[​](#connectivity-indicator "Direct link to Connectivity Indicator")

The POS header shows a coloured dot indicating connection status:

* **Green** — connected to the server, all features available
* **Yellow** — intermittent connection, some operations may be slow
* **Red** — offline, limited to local data

## What Happens During Connectivity Loss[​](#what-happens-during-connectivity-loss "Direct link to What Happens During Connectivity Loss")

If you lose your internet connection while using the POS:

1. **Products and customers remain browsable** from local data.
2. **You can continue building carts** and editing items — every change queues locally.
3. **Recorded payments go through; reader and gateway payments wait** — a sale paid with cash or another payment recorded at the till (card on an external terminal, cash on delivery, bank transfer or cheque) completes on the device and queues to send. Carts and edits queue locally too, and an order for an integrated reader or online gateway can be saved and finished when the connection returns.
4. **Open orders are preserved** in the local database until connectivity returns.

## When Connection Restores[​](#when-connection-restores "Direct link to When Connection Restores")

Once your connection comes back:

* The connectivity indicator turns green.
* **Queued changes drain to your server automatically** — sales and edits made while offline push without any manual action.
* Integrated card readers, online gateways and **Save to Server** become available again.
* Background sync resumes, pulling any product or customer changes that happened while you were offline.

## Tips for Unreliable Connections[​](#tips-for-unreliable-connections "Direct link to Tips for Unreliable Connections")

* **Use "Save to Server" on important orders** — this pushes the order to WooCommerce immediately, so it's not lost if the device's local database is cleared.
* **Check Store health after an outage** — the *changes waiting to send* tile in **Store health → Database** confirms when everything has reached your server.
* **Sync while you have signal** — if you know connectivity will be intermittent, let the catalogue seed finish while you have a good connection.
