Quick Answer
In LS Central, an online POS talks directly to Head Office for every action, while an offline POS runs on its own local database so it keeps selling even if the internet or Head Office goes down. Offline tills receive master data from Head Office through replication (the modern method is Web Replication using Azure Storage) and send their sales back to Head Office using web services. This guide explains both modes in simple words, when to use each, and how offline setup works.
What happens to your till if the internet drops in the middle of a busy Saturday? For a retailer, that’s a scary question and it was exactly why LS Central offers two ways to run a POS: online and offline.
Understanding the difference helps you choose the right setup for your stores and avoid lost sales when the connection fails. In this guide, I will explain both modes in plain English, show when each makes sense, and walk through how offline POS works behind the scenes. Let’s dive in.
📋 In This Guide
Table of Contents
What is an Online POS?
An online POS connects directly to Head Office (which, in LS Central SaaS, lives in the cloud). Every time a cashier looks up an item, checks a price, or completes a sale, the till talks to Head Office in real time.
The big advantage is that everything is always current prices, stock, gift cards, and member points are live, with no waiting for data to sync. The trade-off is dependence on the connection: if the internet or Head Office is unreachable, an online-only till can’t sell.
💼 From 18 Years in the Field
Online POS is perfect for stores with rock-solid internet — a mall location with business fibre, for example. But I always ask the client one question first: “What does one hour of downtime cost you?” If the answer is a lot of lost sales, you want offline capability, no matter how good the connection looks today.
What is an Offline POS?
An offline POS runs on its own local database stored at the store (or on the POS machine itself). Because the data it needs is right there locally, the till isn’t affected by internet outages or Head Office downtime — it keeps selling no matter what.
Here’s the clever part: an offline POS still uses online features when the connection is available (this is sometimes called “online functionality”), but it doesn’t depend on them to make a basic sale. It gets the resilience of a standalone till plus the data availability of a connected one.
The offline POS receives its master and setup data (items, prices, customers) from Head Office through replication, and sends its transactions back to Head Office using web services (the “Send Transaction” web service). So sales are never lost — they’re stored locally and pushed up when the connection is available.
Offline vs Online POS : Side by Side
| Feature | Online POS | Offline POS |
|---|---|---|
| Works without internet? | No — needs the connection to sell | Yes — keeps selling offline |
| Data source | Live from Head Office | Local database at the store |
| Data freshness | Always current | Updated via replication |
| Setup complexity | Simpler | More complex |
| Cost to run | Lower | Higher (local infrastructure) |
| Best for | Stable-connection stores | Uptime-critical stores |
When to Use Each Mode
Choose Online POS when…
- Your store has a reliable, fast internet connection
- You want the simplest setup and lowest running cost
- You need always-live data (e.g. fast-changing prices or central gift cards)
- A short outage wouldn’t seriously hurt your sales
Choose Offline POS when…
- Your store cannot afford downtime — a busy supermarket, pharmacy, or fuel station
- Your internet is unreliable or occasionally drops
- You run high transaction volumes where even minutes of downtime mean big losses
- You have stores in areas with weak connectivity
📋 Real Project Note
For most multi-store retailers I’ve worked with, the answer is a mix: flagship high-volume stores run offline for safety, while small or newer locations start online for simplicity. You don’t have to pick one mode for the whole chain — decide store by store based on connection quality and sales volume.
How Offline POS Works (Replication & Upload)
An offline POS has two jobs happening quietly in the background: getting data down from Head Office, and sending sales up to Head Office.
1. Getting Data Down (Replication)
Head Office needs to push items, prices, customers, and settings to the offline till. In modern LS Central (version 24 and later), the recommended way to do this is Web Replication using Azure Storage. The Scheduler runs in Head Office (in the cloud), and master data is pushed to the offline POS through Azure Blob Storage no need for the older on-site Hybrid Component Server.
💡 Why Azure Storage replication is popular: It’s cheaper to run because you don’t have to maintain the on-site Hybrid Component Server, and it moves you toward a fully cloud-hosted setup. LS Retail reports the Azure Storage cost can be under $10 a month for a typical customer.
2. Sending Sales Up (Transactions)
When the offline till makes a sale, the transaction is stored locally first, then sent to Head Office using the Send Transaction web service. If the connection is down at that moment, the sale simply waits and uploads automatically once the connection returns. Nothing is lost.
⚙️ On the Mobile POS: Offline mode is very visible. A banner shows at the bottom of the screen when the till is offline, and buttons that need the internet are disabled. You can still sell items and post transactions. When the connection returns, the app checks for offline transactions every minute and uploads them automatically — or you can upload them manually from Functions → Offline transactions.
Offline Deployment Options
There are two common ways to set up offline tills, and the right one depends on how much local infrastructure you want to maintain:
| Option | How It Works |
|---|---|
| Resilient POS (database on each till) | Every POS has its own database and service tier installed. Best uptime — each till is fully independent. But maintenance is heavier, since every device’s database must be kept updated. |
| Store Server (one database per store) | A single POS Server in the store (on the LAN) runs the database, service tier, and Hardware Station. The tills are browser-based and connect to that server. Lighter maintenance — only one database per store to update — but the tills rely on the store LAN. |
💼 From 18 Years in the Field
For a small store with two or three tills, the store-server option keeps maintenance simple — one database to update instead of three. For a large store where even one till going down matters, the resilient option (database on every till) is worth the extra upkeep. Match the deployment to how critical each till is.
Offline POS Setup : The Basics
A full offline setup is a technical, partner-led job, but here’s the high-level flow so you know what’s involved. With modern LS Central, the Update Service handles most of the heavy lifting.
- Prepare Head Office (SaaS): set up all the data the offline POS needs, publish the POS Web Services, and enable the Send Transaction web service in the POS Functionality Profile
- Set up Azure Blob Storage: create the storage account (ideally in the same region as LS Central for speed) for Web Replication
- Set up S2S authentication: configure Service-to-Service authentication with an Entra ID (Azure AD) app so the POS can talk to the cloud securely
- Install the offline POS with Update Service: this creates the local database and installs the POS on the terminal, assigned to the right Store No. and Distribution Location
- Set the local details: in the Retail Setup card, set the Local Distribution Location and Local Store No., and activate Azure Storage as the web replication method
- Run the first replication: run the replication job once manually to confirm master data flows down correctly
- Test a sale: disconnect the internet, ring a test sale, reconnect, and confirm the transaction uploads to Head Office
📌 Version compatibility matters: LS Retail supports offline POS backwards compatibility across three major versions. For example, a Head Office on version 26 is tested to work with offline POS versions back to version 23. When Head Office moves to version 27, LS Retail recommends the offline POS be at least on version 24. Keep your tills within this window to stay supported.
Common Mistakes to Avoid
- ❌ Choosing online-only for a high-volume store : one outage during peak hours can cost more than years of offline infrastructure.
- ❌ Forgetting to enable the Send Transaction web service : without it, offline sales can’t upload to Head Office.
- ❌ Skipping the first manual replication test : always confirm data flows down before going live.
- ❌ Letting POS versions fall outside the 3-version window : older tills may lose Head Office compatibility and support.
- ❌ Not testing a real offline sale : disconnect, sell, reconnect, and confirm the upload before trusting it in production.
- ❌ Over-building infrastructure : a small store may only need the store-server option, not a full database on every till.
FAQ : LS Central Offline & Online POS
What is the difference between offline and online POS in LS Central?
An online POS talks to Head Office in real time and needs a connection to sell. An offline POS runs on a local database at the store, so it keeps selling even without internet. The offline POS still uses online features when available, but doesn’t depend on them for basic sales.
Does an offline POS lose sales if the internet goes down?
No. The offline POS stores each transaction locally and sends it to Head Office using the Send Transaction web service. If the connection is down, the sale waits and uploads automatically once the connection returns — nothing is lost.
How does an offline POS get its data from Head Office?
Through replication. In modern LS Central (version 24+), the recommended method is Web Replication using Azure Storage: the Scheduler runs in Head Office (cloud) and pushes master and setup data to the offline POS via Azure Blob Storage, without needing the older on-site Hybrid Component Server.
Is offline POS more expensive than online?
Generally yes, because it needs local infrastructure (a database at the store or on each till). However, the modern Azure Storage replication method is much cheaper than the old Hybrid Component Server approach — LS Retail reports Azure Storage costs can be under $10 a month for a typical customer.
What are the two offline deployment options?
First, a resilient POS where every till has its own database and service tier — best uptime, heavier maintenance. Second, a store server where one server in the store runs the database for browser-based tills — lighter maintenance, but the tills rely on the store LAN.
Does the Mobile POS support offline mode?
Yes. When the Mobile POS is offline, a banner appears at the bottom and internet-dependent buttons are disabled, but you can still sell and post transactions. When the connection returns, offline transactions upload automatically every minute, or you can upload them manually from Functions → Offline transactions.
Do I need the Hybrid Component Server for offline POS?
Not anymore, in most cases. Since LS Central version 24, Web Replication using Azure Storage lets you run offline POS without the Hybrid Component Server. The older HCS method is still available, but Azure Storage replication is the recommended, lower-cost approach.
Can I run some stores online and others offline?
Yes. You can decide per store. Many retailers run high-volume or poor-connectivity stores offline for safety, while smaller or well-connected stores run online for simplicity. You don’t have to use one mode for the entire chain.
Final Thoughts
Choosing between offline and online POS in LS Central comes down to one question: how much would downtime cost your store? If your connection is reliable and a short outage is no big deal, online is simpler and cheaper. If you can’t afford to stop selling, offline gives you peace of mind — the till keeps running no matter what, and no sale is ever lost.
The good news is that modern LS Central makes offline far easier and cheaper than it used to be, thanks to Web Replication using Azure Storage and the Update Service. Decide store by store, test a real offline sale before go-live, and keep your versions in the supported window.
Stay tuned to NavisionPlanet for more simple, step-by-step LS Central and Business Central guides drawn from real store implementations.
📖 Related guides on Navision Planet:
→ LS Central POS Setup Guide for Beginners
→ LS Central Loyalty Program Setup
→ Business Central Modules Explained
→ Business Central Keyboard Shortcuts
