NM Company
A portfolio and enquiry site for events firm NM Company
A visual portfolio and enquiry website for an event management and supplies firm — presenting a full...
Read itRetail & restaurant billing systems
POS / Point-of-Sale Development
Cloud POS with offline-first billing that never stops when the internet drops — GST e-invoicing, live multi-outlet inventory, UPI and card payments, and full hardware integration for retail and restaurant floors.
- Offline-first billing — the till keeps working when the internet drops, then reconciles
- GST-correct invoices: HSN, CGST/SGST/IGST, e-invoice IRN and e-way bill
- One live stock pool across every counter, outlet and online channel
- UPI, cards, wallets and dynamic QR — payments verified before the bill closes
What this is
The till is the business. Build it so it never stops.
A point-of-sale system is judged in the two seconds between a customer handing over a card and the printer cutting the receipt. Nobody praises a POS that works. They only ever notice the one that freezes mid-bill on a Saturday evening with eleven people in the queue, or the one that oversold the last unit of a fast-moving SKU because the counter and the website were reading two different stock numbers.
We build POS software for retailers, restaurants and multi-outlet chains that have outgrown a spreadsheet, a shrink-wrapped desktop package from 2014, or an app-store billing app that cannot talk to their inventory. Cloud where it helps — one catalogue, one price list, one live view across every till and every branch — and offline-first where it matters, so a dropped broadband line or a dead 4G tower slows nobody down. Billing keeps running on the local device and reconciles the moment the connection returns.
This is the right service if the till is the heart of the operation: a grocery or kirana chain weighing loose stock, a QSR firing tickets to a kitchen display, a pharmacy tracking batch and expiry, a franchise owner who needs yesterday's numbers from forty outlets before the morning call. If a hosted retail app off the shelf already fits you, we will say so rather than sell you a build you do not need.
- Offline-first billing — the counter never waits on the network
- Cloud back office — one catalogue and one live stock view across every outlet
- GST invoicing, payments and hardware handled as first-class concerns, not add-ons
Sound familiar
Where the old till lets you down.
These are the exact complaints that bring retailers and restaurateurs to us. None of them show up in a shiny product demo.
-
It freezes the moment the internet drops
A cloud-only app that needs a live connection to print a bill. On a congested tower or a flaky broadband line, the queue at the counter becomes a queue out of the door.
-
The counter and the website oversell each other
The last unit of a fast-moving SKU gets sold twice — once at the till, once online — because each channel reads a different stock number and nobody reserves anything.
-
The invoices will not survive an audit
GST computed by hand, no e-invoice IRN above the threshold, credit notes that do not tie back to the original bill. Reconciliation is a monthly firefight in a spreadsheet.
-
Every outlet is an island
Forty branches, forty separate databases, and head office waits until the fifth of the month to find out what sold. Stock transfers are phone calls and guesswork.
-
Payments and the bill disagree
A UPI collection succeeds on the customer's phone but the callback never lands, so the bill sits open and the cashier reconciles refunds by hand every morning.
-
The hardware only half works
The scanner double-scans, the cash drawer will not kick, the weighing scale needs a proprietary driver, and the kitchen misses tickets on a busy night.
What it does
Everything a real counter needs.
Not a billing screen with extras bolted on. These are first-class parts of the system, in every build.
Fast, forgiving billing
Keyboard-driven billing built for speed — scan, search, quantity, discount, hold and recall a bill, park and resume. Works the same whether you are online or off.
Inventory, purchase & stock
Live stock with reservations, purchase orders and GRN, supplier ledgers, stock transfers, batch and expiry tracking, and low-stock and reorder alerts.
GST e-invoicing & e-way bills
HSN-driven tax, CGST/SGST/IGST by place of supply, IRP e-invoice IRN and signed QR above the threshold, e-way bills and audit-clean credit notes.
Payments that reconcile
UPI intent and dynamic QR, cards, wallets and split tenders through Razorpay, PhonePe, Pine Labs or Ezetap — verified server-side before the bill closes.
Loyalty & promotions
Points, membership tiers, coupons and gift cards, plus BOGO, bundle, tiered and happy-hour offers driven by rules rather than manual overrides at the till.
Role-based access
Cashier, supervisor, manager and owner roles with granular permissions — void and discount limits, drawer access, and an audit trail on every privileged action.
Multi-outlet & franchise
Central catalogue and pricing, outlet-level stock and staff, inter-branch transfers, and consolidated head-office reporting with per-franchise settlement.
Reporting & analytics
Day-close and Z-reports, sales by item, hour, cashier and outlet, margin and dead-stock analysis, and a live dashboard you can read from your phone.
Offline-first sync
A local database on every till, durable write queues, per-terminal invoice numbering and idempotent reconciliation so nothing is lost and nothing is billed twice.
Offline-first
The tower is down. The queue is not.
Offline-first is where most Indian POS software quietly fails. The demo is flawless on office fibre; the reality is a market-street shop on a congested tower, a basement food court with no signal, or a broadband link that drops for ninety seconds every afternoon. A till that shows a spinner during those ninety seconds is a till that stops taking money.
We treat the local device as the source of truth for the billing session and the cloud as the thing it reconciles with. Bills, payments and stock movements are written to an on-device database first and served instantly, then streamed to the server through a durable queue that survives an app restart or a power cut. Sequential invoice numbers are reserved per terminal so two offline tills can never mint the same bill number. When the link returns, sync is idempotent and conflict rules are ones we agree with you in discovery — not whatever a library happened to default to. The cashier always sees what has synced, what is pending and what needs attention, because silence at the counter is worse than a queue.
Two floors, one system
Retail mode. Restaurant mode. Real hardware.
Restaurant mode
Table and floor layout, dine-in, takeaway and delivery in one flow. KOTs route to the right kitchen printer or kitchen display screen; modifiers, combos and course firing are built in. Split, merge and share bills, apply service charge correctly, and pull Swiggy and Zomato orders straight onto the same board so the kitchen works one queue, not three.
Retail mode
Barcode-first billing, SKU variants for size and colour, matrix entry for apparel, batch and expiry for pharma and FMCG, and weighed items with price-embedded barcodes for loose grocery.
Hardware, tested for real
Barcode scanners, 58mm and 80mm ESC/POS thermal printers, cash drawers kicked through the printer, weighing scales over serial or USB, customer display poles and label printers — validated on your actual devices.
Customer & loyalty
A single customer record across every outlet and both formats — purchase history, points, wallet balance and feedback — so a member is recognised at the store and the café alike.
Day close that actually closes
Cash-in and cash-out logging, expected-versus-counted drawer reconciliation, tender-wise settlement against UPI and card statements, and a Z-report the owner can trust — generated per terminal and rolled up per outlet, so the morning starts with numbers instead of arguments.
How we build
From counter walk-through to go-live.
We start on your shop floor, not in a slide deck. Every phase ends in something you can bill on, print from, or read.
-
01
Floor discovery and scope
1–2 weeksWe stand at your counter and watch a real rush. We map the billing flow, the payment mix, the exact hardware, the GST cases, and how many outlets and formats you run. You leave with a written scope, a device list, a connectivity plan for the worst-signal branch, and a number we will stand behind.
-
02
Billing UX and data model
2–3 weeksThe billing screen is designed for keyboard speed and one-handed use under pressure, with the empty, held and offline states drawn up front. We model the catalogue, variants, tax, pricing and stock so the schema fits your business rather than the other way round.
-
03
Offline engine and sync
3–5 weeksThe part most quotes skip. On-device storage, durable write queues, per-terminal invoice numbering and idempotent reconciliation with a conflict rule we agree explicitly. We test it by pulling the network cable mid-bill, killing the app, and cutting the power — then checking that nothing was lost or duplicated.
-
04
Payments, GST and hardware
3–5 weeksUPI, card and wallet integration with server-side verification, GST computation with IRP e-invoicing and e-way bills, and hardware brought up on your real scanners, printers, drawers and scales. Each is signed off against a live transaction, not a mock.
-
05
Pilot in one outlet
2–3 weeksWe go live in a single branch first, sit behind the counter through the busy hours, and fix what real trading exposes before anyone else touches it. Staff are trained on the floor, and we agree the rollback plan before we agree the rollout date.
-
06
Rollout, hypercare and handover
30 days, then ongoingOutlet-by-outlet rollout with the dashboards open, defects fixed at no charge for the first month, and handover of runbooks, the admin and the training material — or we stay on a support retainer with a defined response SLA.
The stack
Proven, offline-capable, hireable.
Chosen so the till survives a dead network and so you can staff the system in India later without a rescue.
Flutter
React
TypeScript
SQLite (on-device)
ESC/POS printing
Electron / Android
Laravel 12
PHP 8.3
PostgreSQL
Redis
WebSockets
Laravel Horizon
Razorpay
PhonePe / UPI
Pine Labs / Ezetap
GST IRP e-Invoice
e-Way Bill API
GitHub Actions
Docker
Sentry
Grafana
The difference
Cloud POS vs the legacy box under the counter.
| Legacy / on-prem POS | PRS cloud POS | |
|---|---|---|
| Works when the internet drops | Only if fully local; then no cloud at all | Offline-first, then reconciles |
| Live view across all outlets | No | Yes |
| GST e-invoicing & e-way bills | Manual or add-on | Built in |
| Software updates | A USB stick and a site visit | Pushed centrally, staged |
| Data backup | Whatever is on that one PC | Continuous, off-site |
| New outlet setup | Days of on-site install | Log in and go |
| You own the code and data | Licensed, often locked in | Yours from the first commit |
Our release bar
Targets we build to.
These are engineering gates we hold ourselves to on every POS build — not sales figures we are promising you. If a till misses them on the mid-range hardware in our test matrix, it does not roll out. Holding this line is what keeps the counter fast on a busy evening and honest at day close.
Talk about your counter
0%
Billing available offline
Cash, credit and prepaid bills need zero connectivity
0
Bills lost or duplicated
Per-terminal numbering, idempotent sync
0%
Cloud backend uptime
Rolling target for the back-office and sync
<2
Scan to printed bill
On mid-range counter hardware
Proof
All case studies
Counters running in the real world.
Retail floors and restaurant kitchens that stay up through Indian network conditions and a Saturday-evening rush.
FealDeal
E-commerce — Ethnic Fashion
A high-catalogue ethnic-wear storefront for FealDeal
A Shopify storefront for a Surat ethnic-wear label — 200+ SKUs of lehengas, sarees and suits organised by type, colour, fabric and work, wit...
Shopify
Platform
0+ SKUs
Catalogue
Turant Logistics
Logistics & Supply Chain
Cutting order-to-dispatch by 62% for a 400-truck 3PL
A fleet, ePOD and route-optimisation platform built offline-first for drivers in low-connectivity corridors — because the two off-the-shelf...
0% faster
Faster order-to-dispatch on the ops floor
0% shorter
Shorter POD-to-invoice cycle (8.4 days to 19 hours)
Collection by Rehan
E-commerce — Watches & Accessories
A brand-led watch and eyewear store for Collection by Rehan
A Shopify storefront for a Surat watch and eyewear retailer — browsable by gender, brand, style and combo, with predictive search, COD check...
Shopify
Platform
Brand & style
Browse by
Yes, and it is the first thing we build, not the last. Every till runs a local database and serves bills, payments and stock updates from it instantly, so the counter never waits on the network. Invoice numbers are reserved per terminal so two offline tills cannot collide, and everything queues durably and reconciles to the cloud the moment the link returns — surviving an app restart or a power cut in between. Card and UPI settlement obviously needs connectivity at the moment of payment, but cash, credit and prepaid bills carry on regardless, and the cashier can always see exactly what is still pending sync.
Tax is computed from the HSN or SAC code and the place of supply, so an intra-state sale splits into CGST and SGST while an inter-state one becomes IGST, with no one editing a template. For businesses above the e-invoice turnover threshold we integrate the Invoice Registration Portal to pull the IRN and signed QR onto the invoice, and the e-way bill portal for consignments above the value limit. Returns generate credit notes against the original bill so your books, your GSTR-1 and the counter agree. B2B bills capture the customer GSTIN; B2C bills carry the dynamic QR where required.
That is a core use case. A central catalogue, price lists and promotions push down to every outlet, while each branch can hold outlet-level pricing, its own stock and its own staff roster. Head office gets a live, consolidated view — sales, stock, cash position — across every location, plus inter-outlet stock transfers with dispatch and receipt confirmation. For franchise models we add per-outlet royalty and settlement reporting and role scoping so a franchisee sees only their own numbers.
The everyday retail and restaurant kit: USB and Bluetooth barcode scanners as keyboard-wedge or HID input, 58mm and 80mm thermal receipt printers over the ESC/POS command set, cash drawers kicked through the printer port, RS232 and USB weighing scales including price-embedded barcodes for loose grocery, customer-facing display poles, and label printers for shelf and product labels. On the restaurant side, kitchen printers and kitchen display screens for KOT routing. We confirm your exact make and model in discovery and test against the real device, not an emulator.
Both, and the mode changes what the software does. Retail mode is built around barcodes, SKU variants such as size and colour, batch and expiry for pharma and FMCG, and weighed items. Restaurant mode is built around table and floor management, KOT routing to the kitchen, modifiers and combos, course firing, split and merge bills, and integration with delivery aggregators. A chain running both formats — a store and a café under one brand — can operate them from a single back office with shared customers and loyalty.
A single-format till with billing, inventory, GST invoicing, payments and a back-office dashboard is typically 12 to 18 weeks and lands in the ₹9L to ₹22L range. A multi-outlet platform with offline sync, restaurant and retail modes, loyalty and consolidated reporting runs 20 to 30 weeks and prices accordingly. The parts that are easy to underestimate — offline reconciliation, hardware quirks and GST edge cases — are exactly the parts we scope explicitly up front, so the number we give after discovery is the number you pay.
Bring us the counter that grinds to a halt on your busiest evening.
Tell us your formats, your outlets, your hardware and the branch with the worst signal. A senior engineer replies within one business day with scope, risk and a number — no discovery call needed for a straight answer.
Proof
Shipped, measured, still running.
Swasthya Sarathi
A healthcare-companion platform for Swasthya Sarathi
A multi-service healthcare platform that helps people find hospitals, doctors, labs, medical stores,...
Read itMV Tech Education
A course and admissions platform for MV Tech Education
A course-catalogue and admissions website for a Bihar vocational institute — leading with industrial...
Read itRelated services
Web Development
Production web applications built on Laravel, Next.js and Postgres — typed, tested, observ...
ExploreMobile App Development
Flutter, React Native and native apps that hold up offline, on old hardware and on a metro...
ExploreEcommerce Development
Commerce platforms where the checkout converts and the back office reconciles — multi-ware...
ExploreLet's talk pos / point-of-sale development
Bring us the hard version of the problem.
A senior engineer reads every enquiry. You'll get a real answer — scope, risk and a number — within one business day.