ERPNext is a browser-based system: every read and write goes to its server, so it does not run offline. The browser-cache offline POS ended with version 12. What works today is a server on your own network, a connection with automatic fallback, or an offline-first POS app at the counter that syncs back to ERPNext.
Short answer
No. ERPNext is a web application, so users need a network path to the server. The browser-cache offline POS was in ERPNext up to version 12; the POS rebuilt for version 13 is online-only, and the Event Streaming sync offered instead left the framework in version 15 and is no longer maintained. For billing through outages, pair ERPNext with an offline-first POS app that syncs when the connection returns.
A shop in a Bengaluru basement, a distributor's van on a patchy 4G route, a factory floor with dead Wi-Fi corners: each wants to know whether ERPNext keeps running when the internet drops. I run ERPNext and Frappe implementations at MithTech, a team of Frappe specialists in Bengaluru, and it is better to say this before go-live than after. ERPNext is built to be online, and a rollout that pretends otherwise has a hard first week.
Does ERPNext work offline without internet?
No. Without a network path to its server, ERPNext cannot load or save a record. The browser sends every read and write to a backend made of Python, a database and background workers.
It works like internet banking: the data lives on the server, and the browser is a window into it. That is a strength for a business with several users or branches, because everyone sees the same live numbers. It is a weakness only where the connection itself is unreliable.
Self-hosting changes one thing. If ERPNext runs on a server inside your building, users on the same local network keep working when the public internet is down, because they still reach the server over the LAN. What stops ERPNext is losing the path to the server, not losing the wider internet. A cloud-hosted instance always needs a working internet connection.
Skimmable summary: ERPNext needs a live path to its server; a server on your own LAN survives an ISP outage, cloud hosting does not.
Why is ERPNext online-first by design?
ERPNext keeps one authoritative copy of every invoice, stock level and ledger entry on the server. That is what stops two people from quietly overwriting each other's work with stale offline data.
It matters most for the numbers that must agree. Stock quantities, account balances and serial or batch tracking depend on a single source of truth. If several devices each edited their own offline copy and synced later, you would get conflicting stock counts and broken ledgers, which is worse than a short outage.
ERPNext is open source under the GPL-3.0 licence, and the same code runs whether you self-host or use managed hosting. You can extend it, but the design assumption stays: the server is meant to be reachable.
Skimmable summary: one copy of the data on the server protects stock and accounts, which is why ERPNext assumes an always-on connection.
Can ERPNext POS run offline?
Not today. The history, in three steps:
| Version | What the POS did offline | Where it stands |
|---|---|---|
| Up to v12 | The old POS kept items and sales in browser storage and synced to the server later | v12 is out of support; staying on it means no security fixes |
| v13 onwards | A rebuilt POS that writes POS Invoices and consolidates them at closing; it needs the server to bill | The current POS; no offline mode |
| v13–v14 | Event Streaming (a producer–consumer sync between ERPNext sites) was offered as the offline route | Moved out of the framework in v15 into a separate app, archived on 6 December 2024 and not maintained |
So stock ERPNext POS expects to be online. Retailers who must bill through outages run an offline-first POS app at the counter and connect it to ERPNext. The app stores each sale locally, keeps billing during the outage, and pushes invoices and stock movements back once the line returns.
Community and third-party POS apps exist for this. Check, for the exact version you pick, that it bills offline, which ERPNext versions it supports and who maintains it; pricing and licences vary, so read each vendor's own page. Treat offline POS as a scoped, tested part of the project, not something that ships in the box.
| Scenario | Stock ERPNext POS | Offline-first POS app + ERPNext |
|---|---|---|
| Sells while internet is down | No | Yes, stores the sale locally |
| Syncs to the ERPNext ledger | Live, needs a connection | On reconnect, in the background |
| Setup effort | Low | Higher: scoping, conflict handling, testing |
| Fits | Reliable connectivity | Frequent or unpredictable outages |
If the counter is central to your business, read the ERPNext retail POS guide alongside this one.
Skimmable summary: offline POS ended with v12 and Event Streaming is unmaintained since v15; for real offline billing, put an offline-first POS app in front of ERPNext.
What happened to the ERPNext mobile app?
On 28 December 2021 Frappe announced on its forum that it would deprecate the native ERPNext apps for Android and iOS and delist them from both stores, because full support took too much development and maintenance. The way to use ERPNext on a phone is now the mobile browser.
The ERPNext desk works on a phone. Log in from the browser and you can view dashboards, create and edit documents, approve requests and check stock. That covers most of what a sales or operations person does on the move.
Some Frappe apps, such as Frappe CRM and Frappe HR, have their own Progressive Web App (PWA) screens that install to the home screen and feel more like an app. They are focused apps, not the full ERP, and a phone still needs a connection to reach the server.
Skimmable summary: the native apps were deprecated in December 2021; the phone browser covers most tasks on the move, with a connection.
How should Indian SMBs handle patchy connectivity?
Plan connectivity as part of the rollout. Because ERPNext is online-first, the most reliable fix for most businesses is a primary line with automatic fallback, so one outage never stops billing or dispatch. Offline POS is the answer only when outages are frequent and unavoidable.
Map where outages actually hurt
List the activities that must never stop: counter billing, dispatch, gate entry. Only those need an offline plan. Back-office work can usually wait out a short pause.
Fix the connection first
A broadband line plus a mobile-data backup that fails over on its own solves outages for most SMBs, at far less cost than building offline sync. Try this before anything custom.
Consider a server on site
If the pain is losing the public internet rather than the local network, hosting ERPNext on a server in your building keeps LAN users working during ISP outages.
Add an offline-first POS only if needed
For counters that must bill during outages, scope an offline POS app that syncs to ERPNext. Test the sync with real data before go-live.
What can you do while ERPNext is offline?
Very little inside ERPNext, because the desk cannot reach the server. What you can do is prepare, so an outage is an inconvenience rather than a standstill.
Keep a manual fallback
For critical counters, keep a paper or spreadsheet backup so staff can record sales during a rare outage and enter them afterwards.
Use an offline POS for billing
Where continuous billing matters, an offline-first POS app keeps the counter selling and syncs the invoices to ERPNext later.
Export reports before travel
Field staff can export the lists and reports they need before heading into low-signal areas.
Use the phone browser
When any connection is available, even mobile data, staff can work from the ERPNext web view on a phone.
Frequently asked questions
+Does ERPNext work offline?
No. ERPNext is a browser-based web application, so it needs a live connection to its server, and current versions have no built-in offline mode. For offline needs such as counter billing, pair ERPNext with an offline-first POS app that syncs when the connection returns.
+Is there an offline mode in the ERPNext POS?
Not in current versions. The old browser-cache offline POS existed up to version 12. The POS rebuilt for version 13 needs the server to bill, and Event Streaming, the sync once offered as the offline route, has been unmaintained since version 15. To bill during outages, use an offline-first POS app that stores sales locally and syncs them to ERPNext.
+Can I use ERPNext on my phone without the app?
Yes. Frappe deprecated the native ERPNext apps in December 2021 and points users to the mobile browser. The desk works on a phone, so you can view dashboards, create documents and approve requests. You still need a connection.
+Does self-hosted ERPNext keep working if my internet goes down?
Partly. If ERPNext runs on a server inside your building, users on the same local network keep working during an internet outage, because they still reach the server over the LAN. Cloud-hosted ERPNext always needs a working internet connection.
+Is ERPNext free for offline setups too?
ERPNext has no licence fee, under GPL-3.0, whether you self-host or use managed hosting. Offline billing is a separate question from cost: an offline POS app may be a paid third-party product, so check its own page for the licence.
+What is the best way to handle unreliable internet with ERPNext?
Fix the connection first: a broadband line with automatic mobile-data fallback removes most outages cheaply. Consider a server on site if you mainly lose the public internet. Add an offline-first POS only for counters that must bill during outages, and test the sync before go-live.
For what ERPNext covers beyond the counter, see the ERPNext platform page. For the newest interface changes, the ERPNext v16 workspace guide shows how the desk is changing.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 20 July 2026
Worked with us? Leave a Google review