ERPNext is an online-first, browser-based system: the core application needs a live connection to its server to read and write data. It does not run fully offline out of the box. There is no robust built-in offline mode today, though offline point-of-sale can be added through community and third-party apps.
Short answer
ERPNext does not work fully offline by default. It is a web application, so users need network access to reach the server. The legacy browser-cache offline POS was removed after version 12. For true offline billing, teams pair ERPNext with a separate offline-first POS app that syncs when the connection returns.
I get this question in almost every discovery call. A shop owner in a Bengaluru basement, a distributor with a patchy 4G van route, a factory floor with dead Wi-Fi corners: all of them want to know whether ERPNext keeps running when the internet drops. I run ERPNext implementations at Mith Tech, and I would rather set expectations honestly up front than sell a promise the software cannot keep. The truthful answer is that ERPNext is built to be online, and pretending otherwise leads to painful go-lives.
Does ERPNext work offline without internet?
No, ERPNext does not work offline without a network path to its server. The application is a web platform: the browser sends every read and write to a backend running Python, a database, and background workers. Cut the connection to that server and the screen simply cannot load or save records.
Think of ERPNext the way you think of internet banking. The data lives on a server, and your browser is a window into it. That design is a strength for multi-user, multi-branch businesses, because everyone sees the same live numbers. It is a limitation only when connectivity itself is unreliable.
There is an important nuance for self-hosted setups. If you host ERPNext on a server inside your own building, users on the same local network can keep working even when the public internet is down, because they still reach the server over the LAN. What breaks ERPNext is losing the path to the server, not losing the wider internet. Cloud-hosted instances, by contrast, always need a working internet connection.
Skimmable summary: ERPNext needs a live connection to its server; on-site self-hosting can survive an internet outage over LAN, but cloud hosting cannot.
Why is ERPNext online-first by design?
ERPNext follows a server-centric architecture because it is built for shared, real-time business data across users, roles, and branches. The backend holds one authoritative copy of every invoice, stock level, and ledger entry, so two people can never quietly overwrite each other's work with stale offline data.
This matters most for the numbers that must always agree. Stock quantity, 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 far worse than a short outage.
ERPNext is free and open source under the GPLv3 licence, and the same open codebase runs whether you self-host or use managed hosting. That openness lets teams extend it, but the core design assumption stays the same: the server is always meant to be reachable.
Skimmable summary: ERPNext keeps one authoritative copy of your data on the server to protect stock and accounting integrity, which is why it assumes an always-on connection.
Can ERPNext POS run offline?
Offline point-of-sale is not reliably built into current ERPNext. An older browser-cache offline POS existed up to version 12, but it was removed, and later synchronisation experiments proved fragile for real retail use. So the honest position for 2026 is that stock ERPNext POS expects to be online.
That does not leave retailers stuck. The common pattern is to run a dedicated offline-first POS application at the counter and connect it to ERPNext for syncing. The POS app stores each sale locally, so billing continues during an outage, then pushes invoices and stock movements back to ERPNext once the connection returns.
Several open-source and third-party offline POS apps exist in the ERPNext ecosystem for exactly this reason. Pricing and licensing vary by product and edition, so check each vendor's official page. My advice is to treat offline POS as a deliberate design choice, scoped and tested before go-live, not something you assume ships in the box.
| Scenario | Stock ERPNext POS | Offline-first POS app + ERPNext |
|---|---|---|
| Sells while internet is down | No | Yes, stores sale locally |
| Syncs to ERPNext ledger | Live, requires connection | On reconnect, in the background |
| Setup effort | Low | Higher, needs scoping and testing |
| Best fit | Reliable connectivity | Frequent or unpredictable outages |
If retail billing is central to your business, our deeper walkthrough of running a shop counter on ERPNext is worth reading alongside this. See the ERPNext retail POS guide for the practical setup.
Skimmable summary: Stock ERPNext POS needs to be online; for genuine offline billing, pair it with a dedicated offline-first POS app that syncs sales back to ERPNext when the connection returns.
What happened to the ERPNext mobile app?
ERPNext's official native mobile apps for Android and iOS were deprecated. Frappe, the company behind ERPNext, announced back in December 2021 that it would delist them, citing limited functionality and high maintenance cost. The recommended way to use ERPNext on a phone is now the mobile browser.
The good news is that the ERPNext desk interface is mobile-friendly. Open your ERPNext site in a phone browser, log in, and you can view dashboards, create and edit documents, approve requests, and check stock. For everyday tasks on the move, the responsive web view covers most of what a sales or operations person needs.
Separately, some Frappe products such as Frappe CRM and Frappe HR ship their own Progressive Web App (PWA) frontends, which install to the home screen and feel more app-like. These are focused apps rather than the full ERP, but they show where the mobile experience is heading. Either way, a phone still needs connectivity to reach the server.
Skimmable summary: The old native ERPNext apps were deprecated in favour of the mobile browser, which is responsive and covers most on-the-go tasks; a network connection is still required.
How should Indian SMBs handle patchy connectivity?
Plan connectivity as part of the ERPNext rollout, not as an afterthought. Because the system is online-first, the most reliable fix for most businesses is a stable primary internet line with an automatic fallback, so a single 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 exact activities that must never stop: counter billing, dispatch, gate entry. Only those need an offline strategy. Back-office work usually tolerates a short pause.
Fix the connection first
A broadband line plus a mobile-data backup that fails over automatically solves outages for most SMBs far more cheaply than building offline sync. Try this before anything custom.
Consider on-site self-hosting
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 genuinely bill during outages, scope a dedicated offline POS app that syncs to ERPNext. Test the sync path with real data before go-live.
Do not assume offline sync is free of trade-offs
Any offline-then-sync setup adds complexity: conflict handling, stock reconciliation, and testing. Only take it on when the business case is real. For many SMBs, better connectivity is the simpler, more reliable investment.
Skimmable summary: Treat connectivity as part of the project; fix the internet line with an automatic fallback first, and reach for offline POS only where outages are genuinely unavoidable.
What can you do while ERPNext is offline?
Very little inside ERPNext itself, because the desk cannot reach the server. What you can do is prepare, so an outage is an inconvenience rather than a standstill. The key is having defined manual fallbacks and an offline path only for the one or two operations that cannot wait.
Keep a manual fallback
For critical counters, keep a simple paper or spreadsheet backup so staff can record transactions during a rare outage and enter them into ERPNext afterward.
Use an offline POS for billing
Where continuous billing matters, an offline-first POS app lets the counter keep selling and syncs the invoices to ERPNext later.
Cache reports before travel
Field staff can export or screenshot the reports and lists they need before heading into low-signal areas, then act on them offline.
Rely on the mobile browser
When any connection is available, even mobile data, the responsive ERPNext web view lets staff work from a phone without a native app.
Skimmable summary: ERPNext itself does little while offline, so plan manual fallbacks, use an offline POS for billing, and pre-export what field staff need before they lose signal.
Frequently asked questions
Does ERPNext work offline?
Not fully. ERPNext is a browser-based web application, so it needs a live connection to its server. There is no dependable built-in offline mode. For genuine offline needs, such as counter billing, teams pair ERPNext with a separate offline-first POS app that syncs when the connection returns.
Is there an offline mode in the ERPNext POS?
Current ERPNext does not include a reliable built-in offline POS. An older browser-cache offline POS existed up to version 12 but was removed. To bill during outages, retailers use a dedicated offline-first POS application that stores sales locally and syncs them to ERPNext once connectivity is restored.
Can I use ERPNext on my phone without the app?
Yes. The official ERPNext native apps were deprecated, and Frappe recommends the mobile browser instead. The ERPNext desk is responsive, so you can log in from a phone browser to view dashboards, create documents, and approve requests. A network connection is still required.
Does self-hosted ERPNext keep working if my internet goes down?
It can, partly. If ERPNext is hosted on a server inside your own building, users on the same local network can 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 really free even for offline setups?
ERPNext is free and open source under the GPLv3 licence, whether you self-host or use managed hosting. Offline capability is a separate architectural question from cost. Adding offline POS may involve third-party apps whose pricing varies by edition, so check each vendor's official page.
What is the best way to handle unreliable internet with ERPNext?
Fix the connection first: a stable broadband line with an automatic mobile-data fallback removes most outages cheaply. Consider on-site self-hosting if you mainly lose the public internet. Add an offline-first POS only for counters that genuinely must bill during outages, and test the sync before go-live.
About the author
I am Manoj, an ERPNext implementation consultant at Mith Tech, an independent open-source ERPNext and Frappe studio based in Bengaluru. I help Indian SMBs deploy, customise, and support ERPNext, including retail and POS setups where connectivity and offline planning genuinely matter. I write these guides to give founders honest, jargon-free answers before they commit to a platform.
Planning ERPNext for a shop or a patchy-connectivity site? Let's scope it properly.
If you want the bigger picture of what ERPNext covers and how it fits an Indian SMB, start with our ERPNext overview. For the newest interface changes, the ERPNext v16 workspace guide shows how the desk is evolving.