SalevaChoosing tools
Offline POS or online POS: which one suits your shop
Cloud tills stop when the internet stops. Offline tills cannot see your second branch. Here is how to tell which side your shop belongs on, and why the answer is usually both.
Software companies present this as a philosophical choice. For a shopkeeper it is a much narrower question: what happens to my counter when the internet goes down in the middle of a queue?
If the answer is "we stop selling", the software is wrong for the shop, no matter how good the dashboard looks.
Here is what the two approaches actually mean, where each one genuinely wins, and how to judge the hybrid arrangement that most shops end up needing.
What the words mean in practice
An online, or cloud, POS keeps your data on a server. The till is a window onto that server. Prices, stock and sales live in one place, which is why the owner can see the shop from home.
An offline, or local, POS keeps your data on the device in the shop. It works whether or not there is a connection, because nothing has to travel anywhere for a sale to complete.
The distinction that matters is not where the data lives. It is what the till needs in order to finish a sale. Some systems described as cloud-based have an offline mode that queues sales; others simply stop.
Where an offline till wins
When the connection is unreliable. This is not an edge case in most of the world. Mobile data drops, a fibre cut takes a neighbourhood off for a day, the shop sits in a basement, the phone is out of credit. A till that keeps working through all of that is not a luxury.
When speed at the counter matters. Local data means no waiting. Searching a product, adding it, taking payment — all instant, because nothing is being fetched. On a busy evening this is the difference between a queue that moves and one that does not.
When the shop is one counter. A single shop with one till has no synchronisation problem to solve. The main argument for the cloud does not apply.
When you are careful about running costs. No connection required means no monthly data dependency for the core job of selling.
Where an online till wins
When there is more than one device. Two people serving customers from the same stock need to see the same numbers. Without a shared copy somewhere, you have two shops that happen to share a doorway.
When the owner is not always in the shop. Seeing today's sales from elsewhere is genuinely valuable, and it is only possible if the data leaves the device.
When customers interact with you online. A public product page, online orders, delivery tracking and chat all require a server by definition. There is no offline version of a link you send to a customer.
When you want a backup that survives the device. A phone can be lost, stolen or dropped in water. Data that exists only on it disappears with it.
The arrangement most shops actually need
Put plainly: selling should never need the internet; everything else can.
That is not a compromise, it is the correct design. Sales are the one operation with a customer standing in front of you, so they must complete locally and instantly. Reporting from home, syncing to a second phone, publishing a catalogue, receiving online orders — none of those has a queue waiting, so all of them can tolerate a connection that comes and goes.
A system built this way behaves predictably: the counter never stops, and when the connection returns, the shop's phones catch up with each other.
This is how Saleva is built. Selling, stock, customers, dues, expenses and reports all work with no connection at all. Multi-device sync, the public shop page, customer orders and cloud backup use the internet when it is there and queue quietly when it is not.
How to judge a system before you commit
Whatever you are considering, these questions separate marketing from behaviour:
- Turn off the internet and make a sale. Not a demo — the real app, flight mode on. Does it complete? Does it print? This one test settles most of the argument.
- Turn the internet back on. Does the sale reach the other device? And does it arrive once, not twice?
- Edit the same product on two devices while both are offline, then reconnect. A serious system tells you there was a conflict. A careless one silently discards one of the edits.
- Where is the backup, and who controls it? "In the cloud" is not an answer. Can you take a copy with you if you stop using the product?
- What happens if you stop paying? Do you keep your data? Can you export it? This is the question people ask only when it is too late.
- What does it cost when the shop grows? Per device, per branch, per month — find the number before the second branch, not after.
The questions that are not really about offline
Two worries come up in this discussion that belong somewhere else.
"Is my data safe on someone else's server?" A fair question, but the useful version is narrower: what exactly is uploaded, who can read it, and can you delete it? A shop's supplier prices and customer list are sensitive; the names and prices of products you publish on a public page are not. Read the privacy policy and look for the difference. Ours is here.
"Will I be locked in?" This is about export, not architecture. A system you can take a full backup out of is one you can leave. Ask how to get your data out before you put it in.
A short way to decide
| Your situation | What to prioritise |
|---|---|
| One counter, unreliable internet | Offline-first, cloud optional |
| One counter, good internet, you travel | Offline-first with sync switched on |
| Two or more people serving | Offline-first plus sync, and staff permissions |
| Several branches | Sync is not optional; check how transfers between branches work |
| You want online orders | You need the server side, but insist that selling still works offline |
| You sell at markets or on the move | Offline-first, and check it runs on a phone rather than only a terminal |
Notice that offline-first appears in every row. That is the point. Cloud features are worth having and most shops eventually want them, but they should be added on top of a till that can stand on its own, not underneath one that falls over without them.
Questions shopkeepers ask
If the app works offline, where is my data?
On the device, in a database only that app can read. That is why a backup matters: a phone is a single point of failure. Back up to your own cloud storage, and keep a copy you control.
Does offline mean my staff's phones will disagree with mine?
Only until they reconnect. A well-built sync sends each device's changes both ways and flags genuine conflicts rather than hiding them. Read our note on what to check above before trusting any system with two tills.
Can I use an offline POS and still take online orders?
Yes, and this is the common arrangement: the catalogue is published to a page customers can open, orders arrive at the shop, and the selling itself still happens on a till that does not need the connection.
Do I need a proper POS terminal or is a phone enough?
For most small shops a phone is enough, and it is the device the owner already carries and knows how to use. Add a Bluetooth thermal printer for receipts and you have the whole counter.
What happens to online features if I stop paying for them?
Ask this of any provider. In Saleva, the app and everything local stay free and keep working; the online parts, such as the public shop page, need an active balance and pause when it lapses. Your records stay on your phone either way.
Try this in Saleva
Saleva is a free Android point-of-sale app for small shops: selling, stock, customer dues, staff and an online shop page. Selling works with no internet at all.