POS software that works when the internet does not
Custom POS systems for retail and hospitality — fast billing, offline resilience, inventory sync, and multi-outlet reporting.
fast at the counter · still works when the internet does not
- Fast billing
- Offline operation
- Inventory sync
- Best when
- Multiple outlets, unreliable connectivity, or pricing a packaged POS cannot express.
- Not a fit when
- One counter, and a standard product already does the job.
- First thing you get
- Billing that works offline at one outlet, then the rest.
What is POS software?
POS (point of sale) software is the system a shop or restaurant uses to bill customers and take payments, usually connected to inventory and reporting. Its one unforgivable failure is being unable to take a payment. We build custom POS offline-first: sales complete locally and sync when the connection returns, with multi-outlet reporting on top.
A point of sale system has one unforgivable failure mode: not being able to take a payment. Everything else — reporting, loyalty, inventory — matters less than billing staying fast and available while a customer waits.
So we build POS offline-first. Transactions complete locally and sync when connectivity returns, because a dropped connection should slow down your reporting, not your queue.
What this includes
- 01
Fast billing
A checkout flow optimised for speed and keyboard or scanner use, not mouse navigation.
- 02
Offline operation
Sales complete without connectivity and reconcile automatically when it returns.
- 03
Inventory sync
Stock levels updated across outlets from the same transaction data.
- 04
Payment integration
Card terminals, UPI, and split payments handled at the counter.
- 05
Multi-outlet reporting
Sales, margin, and stock across locations in one view.
- 06
Tax and compliance
GST-compliant invoicing with the formats and returns your accountant expects.
Situations we see most often
Multiple outlets without a shared view
Each location reporting separately, with consolidation happening manually and late.
Unreliable connectivity
Stores where the internet drops regularly and billing cannot depend on it.
Packaged POS does not fit
Pricing rules, combos, or workflows your industry needs that generic systems cannot express.
POS and inventory are separate
Sales recorded in one system and stock in another, reconciled by hand.
What to know before you start
Custom POS or a packaged POS: which do you need?
If you run one or two outlets with standard pricing, a packaged POS is almost always the right answer: cheap, proven and supported. Custom POS earns its cost when the packaged ones cannot express how you sell, such as unusual pricing, bundles or weights, when billing has to be tightly connected to your own inventory or ERP, or when you run enough outlets that per-terminal licences and workarounds add up.
We will tell you honestly which side of that line you are on before you spend anything on a build.
How does offline billing actually work?
Each terminal keeps a local database of products, prices and stock. A sale is completed and printed locally, with no round trip to a server, so a dropped connection never stops the queue. A sync engine sends transactions to the central system when connectivity returns and pulls down price and stock changes.
The hard part is conflicts, for example two outlets selling the last unit of an item while both are offline. Those are resolved by explicit rules agreed with you, and anything ambiguous is flagged for a person rather than silently overwritten.
How does POS connect to inventory and accounting?
Every sale decrements one authoritative stock position that the website, warehouse and other outlets also read from, so the shop floor and the online store do not disagree. Daily totals, tax breakdowns and payment settlements post into your accounting system rather than being re-keyed.
That connection is usually what makes custom POS worth it: billing, stock and the books agree without someone reconciling them at the end of each week.
What happens to the POS after launch?
A POS is never finished, because prices, products, promotions and tax rules keep changing. Those changes are made centrally and pushed to every terminal, and tax configuration is kept editable, since GST rates and rules do change.
Under a support retainer we monitor sync health across outlets, so a terminal that has stopped syncing is noticed before it causes a stock or reconciliation problem, and we handle updates, new hardware and new outlets as the business grows.
What drives the cost of custom POS software?
POS cost is driven mostly by how you sell and how many places you sell from. These factors move it most.
| Factor | Effect | Why it matters |
|---|---|---|
| Outlets and terminals | High | More outlets mean central management, consolidated reporting, and price and stock changes that must reach every terminal reliably. |
| Offline sync | High | Billing that never stops needs a local database, a sync engine and conflict rules, which is the core engineering effort in a serious POS. |
| Pricing rules | Medium | Promotions, bundles, customer-specific rates, weighed items and loyalty each add logic that must work at billing speed. |
| Inventory model | Medium | Variants, batches, expiry dates and serial numbers add tracking that a simple product list does not need. |
| Payments | Medium | Card terminals, UPI and split payments each need integration and reconciliation against settlements. |
| Accounting and ERP integration | Medium | Posting sales, tax and settlements into Tally, Zoho Books or an ERP removes manual work, but each target system has its own format. |
| Hardware range | Low | Standard printers, scanners and cash drawers are straightforward; unusual devices are confirmed during discovery. |
What a typical engagement looks like
- 011–3 weeks
Discover
Process map
- 022–4 weeks
Design
Interactive prototype
- 03two-week cycles
Build
Working software each cycle
- 04ongoing
Ship & support
Automated pipeline
What we build it with
- Terminals
- WindowsAndroidBarcode scannersThermal printers
- Offline
- Local databaseSync engineConflict handling
- Payments
- Card terminalsUPISplit payments
Questions we get asked
01Does it work without an internet connection?
Yes, and this is a core design requirement rather than a feature. Transactions complete locally and sync when the connection returns, with conflict handling for anything that changed in the meantime.
02Is it GST compliant?
Yes. Invoice formats, tax breakdowns, and reporting are built to current GST requirements and kept configurable, since rates and rules change.
03What hardware does it run on?
It is built for standard POS hardware — Windows or Android terminals, barcode scanners, thermal printers, and cash drawers. We confirm compatibility with your specific hardware during discovery.
04Can it handle multiple outlets with central reporting?
Yes. Each outlet bills independently, and head office sees sales, stock and collections across every outlet in one place, with prices and products managed centrally.
05Does it support UPI payments?
Yes, alongside cards, cash and split payments. Payments are reconciled against settlements, so the amount billed and the amount received can be matched without manual checking.
06Can the POS run on Android tablets?
Yes. It runs on Windows or Android terminals, including tablets, with barcode scanners, thermal printers and cash drawers. Mixed hardware across outlets is fine, and we confirm compatibility with your specific devices during discovery.
07How are promotions and loyalty handled?
As rules you manage centrally: discounts, bundles, time-bound offers and customer-specific pricing are applied automatically at billing, on every terminal, without slowing the queue. Loyalty points and redemptions are tracked against the customer record across outlets.
Adjacent capabilities
Tell us what you are building.
Share the problem and we will come back with an approach, a rough shape of the work, and what it would take to deliver it.