Offline billing means the app stores items, customers, and invoices on the device, so you can scan, bill, and update stock with no internet at all; changes sync when the connection returns. Test it before you rely on it: bill in airplane mode, restart the app offline, then reconnect and check that invoice numbers, stock, and payments synced correctly.
In many markets, shop internet is unreliable — a weak mobile signal inside a concrete building, a router that drops at peak hours, or a power cut that takes the Wi-Fi with it. With a cloud-only billing tool, each of those means a stalled counter and a line of waiting customers. Offline billing removes that dependency.
Offline-first vs "has an offline mode"
| Cloud-only | Limited offline mode | Offline-first | |
|---|---|---|---|
| Where data lives | Server | Server, with a partial local cache | On the device, synced to the cloud |
| Billing with no internet | Stops | Some features work | Everything works |
| Adding new items offline | No | Often not | Yes |
| Reports offline | No | Rarely | Yes |
| After reconnecting | — | Queued bills upload | Two-way sync |
A five-minute test before you rely on it
- Turn on airplane mode.
- Create a new item and a new customer.
- Bill three sales, including one on credit.
- Close and reopen the app — are the bills still there?
- Reconnect and check on a second device (or the web) that invoices, invoice numbers, stock, and payments all match.
How sync and conflicts work
With one device, there's nothing to conflict — the device is the source of truth. With several devices billing offline at once, two things need care:
- Invoice numbers: each device needs its own series (for example, prefix A- and B-) so two offline devices never issue the same number. GST rules require numbers to be unique in the financial year.
- Stock: two devices selling the last unit offline can briefly push stock negative. Good sync merges the movements and shows the true balance once online.
What offline billing can't do
- Generate an e-invoice IRN — that needs the Invoice Registration Portal, so B2B e-invoices are registered once you're back online (within the 30-day window if your turnover is ₹10 crore or more)
- Generate e-way bills
- Process card or UPI payments that need a network (record them as pending and confirm later)
A fallback plan for the counter
- Keep the billing device charged and on a power bank during outages.
- If the device itself fails, write sales on a numbered paper pad and enter them the same day.
- Back up your data regularly — a local export at minimum.
- Keep a mobile hotspot as a backup for UPI and syncing.
StashBill (launching soon) is offline-first: every core feature — scanning, billing, stock — works with zero signal, and Pro syncs across devices when you reconnect. See offline-first.
Frequently asked
Are invoices made offline legally valid?
Yes, if they contain all required fields. The only exception is B2B e-invoices for businesses above the e-invoicing threshold, which need an IRN from the government portal.
Will I lose data if my phone breaks while offline?
Anything not yet synced or backed up could be lost, so sync or export regularly — daily is a sensible habit.
Can I accept UPI payments offline?
UPI needs the customer's phone to have a connection, not yours. Record the payment against the bill and confirm it when your device is back online.