An offline POS system for retail keeps taking cash sales, returns and stock changes on the till when the internet drops, then uploads them once the connection returns. The catch is card payments. Most systems can record a card sale offline, but the card still has to be approved by the card network, and that normally needs a connection. An offline till can keep a shop trading without keeping every sale paid. This guide shows how to test that claim before you buy, and when custom POS software development makes more sense than a ready-made product.
1Does an offline POS system for retail keep working?
A point of sale system is the software and hardware that takes payment at your counter. If you searched for an offline POS system for retail, you probably want one answer: will the tills keep working when the internet fails?
An offline point of sale keeps working when the link to the server or cloud breaks. The terminal saves each sale, void, refund and stock deduction in a local database on the device, so nothing is lost while the internet is down.
When the connection returns, the terminal sends the queued records to the server. This is called sync. Totals and stock levels update, and the back office sees the day's trading. In our experience, sync is where problems show up, so ask how it works before you sign anything.
Good offline mode should switch on by itself. Staff should not have to flip a setting in the middle of a rush.
2Can an offline POS system for retail take card payments?
Not on its own. Products handle this differently, but cash sales and stock moves can carry on without a connection. Card payments usually need the processor to approve each charge in real time, so a till with no link often cannot finish the approval.
Some systems use store-and-forward. The terminal holds the card payment and sends it when the link returns. That keeps the queue moving, but it shifts the risk: you hand over goods before you know the money has cleared. Whether a retail POS system offers this, and for which card types and amounts, depends on your payment provider and how the system is set up. Get the answer in writing from your processor, not from a sales brochure.
Ask about offline card handling before you buy, not after the first outage.
Why card authorisation still needs a connection
Card networks approve each charge when it happens. A till that cannot reach the bank cannot ask whether the card has funds. It can record the sale, but it may not be able to approve the payment at the moment the customer taps.
Ask your provider exactly which card types, amounts and time limits apply to offline holds. Terms differ between providers, and the answer shapes the rules your staff follow at the counter.
What happens to a card declined after the till syncs?
The chain runs in four steps:
- The sale is recorded offline and the customer leaves with the goods.
- The card is checked when the till syncs.
- The card is declined, perhaps for insufficient funds or a closed account.
- The goods have gone and the money has not arrived.
Whether you absorb that loss, chase the customer or refuse held payments is a decision for the owner. Write the policy down and make sure staff know it before the first outage, not during it. Some owners choose a lower offline limit for card sales while they learn how declines behave in their own shop.
3How long can a POS stay offline before it becomes a problem?
There is no single safe number of hours, and no vendor can give you one that fits every shop. The real limits depend on three things: how much card value a till can hold offline, how many sales queue up before a sync, and how long stock figures can drift before someone notices.
Write your own limits down before go-live. Decide the largest card sale an offline till may accept, and the point at which a manager must be told that a till has been offline too long. Check those limits against your processor's written terms, not your memory of the sales call.
4Is your POS offline-ready or truly offline?
'Offline-ready' is a marketing phrase. Plenty of offline POS software carries that label, but some systems freeze at the payment screen until the connection returns. Others need a cloud login before they open, or cannot change a price without internet. Those are not offline in any useful sense.
| What the vendor says | What it can hide | Test on your own till |
|---|---|---|
| Works offline | Freezes at the payment screen | Take a card sale with the internet off |
| Offline-ready | Needs a cloud login before it opens | Restart the terminal with the internet off |
| Offline mode included | Price and menu changes need the server | Change one price offline |
| Syncs automatically | No protection against repeat uploads | Ask how a repeated sale is rejected |
| Multi-store offline | One stock record with no rule for conflicts | Ask what happens when two tills sell the last item |
5How do I test whether my POS is truly offline?
Pick a quiet hour. Unplug the internet at the router, then run these steps on each till.
| Step | What should happen | Pass | Fail |
|---|---|---|---|
| Make a cash sale | Sale completes and prints a receipt | ||
| Make a card sale | Completes, or follows your written offline card rule | ||
| Process a refund | Refund saves and appears in the till report | ||
| Change one price | Price changes on that till without the server | ||
| Run a stock count | Count saves and shows locally | ||
| Restart the terminal | It opens and keeps the queued sales | ||
| Reconnect the internet | Queued sales upload once, with no duplicates |
Does offline mode work on a tablet or phone? That depends on the app, not the device name. Ask whether the app stores sales on the device itself, then run the test above on that exact hardware, because a phone and a desktop till can behave differently.
Record the results with the date. Repeat the test after every software update. A system that passed last year can fail after a patch.
6How does stock stay accurate across offline tills?
Each terminal saves its stock deductions locally and reflects them after sync. On a single till, this works well. The risk comes from shared stock, where two or more tills draw on the same stock record while both are offline.
A single-store system with one stock record avoids most of this, because the tills share one count once they reconnect. Multi-till and multi-store setups need a clear rule for what happens when two offline sales claim the same unit.
Can two offline tills sell the last unit?
The last jacket in a size is sold on two offline tills within the same minute. Both sales were valid when they happened. At sync, the system finds one unit for two sales.
You have three rules to choose from:
- Reserve stock on each till. Each till holds a share of the stock. Simple, but one till can sit on unsold stock while the other runs out.
- Accept both and flag negative stock. No customer loses a sale. The back office corrects the count, which may mean an apology or a substitute.
- Hold the second sale for a manager. Safer for high-value items, but someone has to be on hand to decide.
Choose one, write it down and train staff before go-live. Whichever rule you pick, test it on purpose during the offline test above, not for the first time on a busy Saturday.
7How do offline sales reconcile once the internet returns?
Reconciliation is the check that the till, the server and the processor agree. Sync uploads the queued sales in order, and stock and totals update. The back office then compares till totals with the processor's settlement report.
The main risk is duplication. A sale can be uploaded twice after a retry, and a card can be charged twice. Good systems give every sale a unique ID, so a repeat is recognised and rejected.
Why duplicate sales happen and how to prevent them
Say the till sends a sale, the connection drops before a reply arrives, and the till tries again. The server may already have the first copy. Without protection, it records two sales.
The fix is a unique reference on each sale. The server stores the reference the first time and ignores any repeat with the same one. Engineers call this idempotency. Then run a daily reconciliation that matches till records against the settlement report. A difference shows up the same day, not at month end.
8Does a custom offline POS need a new PCI DSS assessment?
PCI DSS, the Payment Card Industry Data Security Standard, sets the rules for handling card data. Version 4.0.1 is current, and all its requirements have been mandatory since 31 March 2025 (summary of the PCI DSS 4.0 requirements).
A custom offline POS can change your scope. A queue that holds card data on the terminal may move a store to a different self-assessment questionnaire from the one it used before. Treat that as a question to settle with your acquirer or a Qualified Security Assessor (QSA), not as a settled answer.
Every failover path belongs in your network diagram, including any cellular backup, and each one needs testing. Ask any failover vendor for the switchover time in writing, then time it yourself in your shop.
9When is a custom offline POS better than a ready-made system?
A custom build tends to win in four cases: your workflows do not fit a standard product, you need deep links to accounting or e-commerce, several stores need one stock view, or ongoing software fees will exceed the build cost over the life of the system. Off-the-shelf suits a standard single-store shop with simple needs and a short timeline.
The bigger question is who owns the code and the accounts. Treevoxa clients own the code and accounts, so the system does not depend on our continued involvement or a vendor's pricing changes. A ready-made system with full source code is the other route to weigh. For the wider trade-off, read custom software vs SaaS: how to choose.
Build or buy: the decision points
| Factor | Points towards buy | Points towards build |
|---|---|---|
| Workflows | Standard counter, returns and stock | Unique pricing, bundles or service rules |
| Integrations | Basic exports | Deep links to accounting or e-commerce |
| Stores and tills | One store, a few tills | Several stores sharing one stock view |
| Data ownership | Vendor-hosted is acceptable | You need the code and data in your control |
| Five-year fees | Low at your size | Subscriptions pass the build cost |
| Time to launch | Days to weeks | Months, set by a written scope |
Work out the five-year fee line with the vendor's written pricing for your number of tills, then compare it with a written build quote. Listed prices change, so check them on the day you decide.
If you run a pharmacy, PharmaFlow is our pharmacy POS. It is built for that trade rather than general retail, so judge it against your own counter and stock needs. Whatever you choose, we agree a written scope, a fixed price and a launch date before any work starts.
How do sales tax and card terminals shape the build?
Sales tax is the part vendors skip. In the US, rates and rules vary by state and by city, so a shop in Austin, Raleigh, Denver or New York may need different tax logic. In Canada, GST, HST and provincial taxes apply. In Ontario, which covers Toronto and the GTA, HST is 13%.
Card terminal and processor integrations also differ between the two countries. A till that works in Denver may need different work to run in Toronto. Build the tax rules and terminal links for each market, and test them offline as well as online. Confirm the tax treatment with your accountant before go-live. For US projects, see software development for US companies.
10What should you ask a vendor before you buy?
Take this list into every sales call. Good answers are specific and go in writing.
| Question | A good answer sounds like |
|---|---|
| Does it take cash and card with no internet? | Cash yes; card only under a written store-and-forward rule |
| What happens at the payment screen offline? | The sale is queued or held, with a clear message |
| Can prices change offline? | Yes, on that till, and they sync later |
| Who owns the code and accounts? | You do, and you hold the admin logins |
| Where is the data stored? | A named location, with backups you can reach |
| How are sync conflicts resolved? | A written rule for shared stock and duplicate sales |
| Is the scope written, with a fixed price and launch date? | Yes, before any work starts |
| How is failover tested? | Tested in a live shop, with results you can see |
To think through the budget before you talk to anyone, use the software development cost calculator. It is a planning tool, not a quoted price.
11What should you do before the next outage?
An offline POS system for retail is only as good as the test you run on it. Run the checklist on your current system this week. If it fails on card sales or shared stock, you know where the gap is, and you can set a written rule for each failure before the next outage. Keep the results with the date, and repeat the test after every software update.