Mobile
Flutter
Build Android and iOS apps from one shared codebase, so you launch on both platforms faster with a consistent experience.
Used for
- Mobile apps
- Delivery apps
- E-commerce apps
- Booking apps
POS software
POS software development for retail stores, restaurants and multi-outlet chains
Fast billing at the counter, even when the internet drops, with payments, stock and reports flowing to head office.
At a glance
The short version
What it is
Custom point-of-sale software with offline billing, UPI QR payments, GST invoices, hardware integration and central control for multiple outlets.
- What you get
- Billing counter
- Restaurant floor
- Store manager
- Head office
- How it works
- Billing counter
- Thermal printer
- Kitchen display or stock ledger
- Background sync
- 1 more
- Runs on
- Desktop
- Android
- Web app
- Admin
- Who it's for
- Cost depends on
- Target devices
- Offline depth
- Hardware models
Flutter and the related logo are trademarks of Google LLC. We are not endorsed by or affiliated with Google LLC.
How to start
Tell us what you need in your own words. You talk to the developers who would build it and get a written, line-item estimate.
Get a project estimateBilling that keeps going when the network does not
Counter staff cannot wait for a slow API while a queue forms. Our POS apps store products, prices and recent customers on the device, generate invoices offline from a counter-specific number series, and sync sales to the server when the connection returns.
Around that core we add what your format needs: kitchen order tickets and table management for restaurants, weighing-scale barcodes for grocery and sweets, customer credit ledgers for neighbourhood stores, and approvals for voids and discounts.
Challenges
Counter problems a custom POS solves
Billing stops when the internet does
Cloud-only POS screens freeze during outages, and customers walk out of the queue.
Payments that don't match the till
Cash, card and UPI collections are reconciled by hand at day end.
Leakage through voids and discounts
Without approvals and logs, cancelled bills and manual discounts are hard to question.
Chains without central control
Each outlet edits its own prices and menus, so head office cannot enforce consistency.
What is included
POS modules
Platform: Windows or Android app
Billing counter
- Barcode and weighing-scale label scanning
- GST invoices with HSN and B2B customer GSTIN
- Split payments across cash, card and UPI
- Offline billing with automatic sync
Platform: Android app
Restaurant floor
- Captain app for table orders
- Kitchen order tickets and kitchen display
- Table transfers, merges and split bills
Platform: Web app
Store manager
- Shift open and close with cash counts
- Stock receipts and inter-store transfers
- Void and discount approvals
Platform: Admin dashboard
Head office
- Central products, menus, prices and schemes
- Outlet-wise sales and payment mode reports
- Loyalty points and customer history
How it works
How a sale moves from the counter to head office
Billing happens on the device first, so the queue keeps moving whatever the network is doing.
- Billing counter
Step 1: Items scanned
The cashier scans barcodes or weighing-scale labels; prices, schemes and GST come from the local catalogue, even offline.
- Billing counter
Step 2: Customer pays
A UPI QR for the exact amount appears on the customer screen; card, cash and split payments also work.
- Thermal printer
Step 3: Invoice printed
The GST invoice prints from a number series reserved for that counter, so offline bills never clash.
- Kitchen display or stock ledger
Step 4: Kitchen or stock updated
In restaurants, a kitchen order ticket goes to the kitchen; in stores, stock reduces as each bill closes.
- Background sync
Step 5: Sync to the server
When the connection returns, bills, payments and stock movements sync in order, without the cashier doing anything.
- Store manager and head office
Step 6: Day close and reports
The shift closes with a cash count, and head office sees outlet-wise sales, payment modes and voids.
Platforms
Where the POS runs
Counters run on Windows PCs or Android POS terminals, captains use phones, and managers and head office use the web.
- Desktop
Desktop app
Windows and macOS apps for billing counters, kiosks and offline-heavy work, where a browser isn't enough.
- Mobile
Android app
Apps for Android phones and tablets, tested on budget and mid-range devices and published on Google Play or privately.
- Web
Web application
Browser-based applications with logins, roles and workflows, such as customer portals, SaaS products and internal tools.
- Back office
Admin dashboard
Back-office panels for operations, support and finance teams: orders, users, content, reports and permissions.
Technology
Technology for billing that keeps working offline
Chosen so the counter bills without internet, syncs safely later and connects to printers, scanners and payment devices.
Web
React
Builds interactive screens in the browser, such as dashboards, admin panels and portals, that respond instantly as your team works.
Used for
- Web apps
- Admin panels
- Dashboards
- Customer portals
Backend
Node.js
Runs the server side of apps: fast, scalable back ends that power your app, website and integrations.
Used for
- App back ends
- Live order tracking
- Chat and notifications
- Payment processing
Data
PostgreSQL
A reliable database for the records your business runs on: orders, payments, bookings and stock, kept accurate and easy to report on.
Used for
- Orders and customers
- Payments and ledgers
- Stock and inventory
- Bookings
Cloud & DevOps
Firebase
Ready-made building blocks for mobile apps, such as push notifications, phone OTP login and crash reports, so you launch sooner.
Used for
- Push notifications
- Phone OTP login
- Crash reports
- Real-time updates
Payments & maps
Razorpay
Lets customers in India pay by UPI, cards, netbanking or wallets, and handles subscriptions, refunds and payouts to sellers or partners.
Used for
- UPI payments
- Cards and netbanking
- Subscriptions
- Payment links
Flutter and the related logo are trademarks of Google LLC. We are not endorsed by or affiliated with Google LLC.
Integrations
Payments, hardware and channel integrations
Payments
Dynamic UPI QR via Razorpay, Paytm or PhonePe
Bill-specific QR codes with automatic payment confirmation.
Card terminals
Amounts pushed to terminals from providers such as Pine Labs where billing integration is offered.
Hardware
Thermal printers and cash drawers
ESC/POS receipt and KOT printing over USB, network or Bluetooth.
Weighing scales
Labels with embedded weight or price read at billing.
Online orders
Swiggy and Zomato
Orders injected into the POS through their partner integration programmes, where eligible.
Accounting
TallyPrime or Zoho Books
Day-end sales, tax and payment summaries posted to accounts.
Plain-English glossary
POS terms, in plain English
- KOT (kitchen order ticket)
- The slip or kitchen-screen message that tells the kitchen what to prepare for each table. Sending it from the captain's phone avoids handwritten orders and missed items.
- Offline-first billing
- The counter app keeps products and prices on the device and bills without internet, then syncs when the connection returns, so queues keep moving.
- Dynamic UPI QR
- A QR code created for the exact bill amount. When the customer pays, the POS marks the bill paid automatically, so staff do not check payment screenshots.
- ESC/POS
- The common command language of thermal receipt printers. Supporting it lets the POS print bills and KOTs on most printer brands.
- Void
- A bill or item cancelled after it was entered. Requiring manager approval for voids, with a log, is one of the simplest ways to stop leakage at the counter.
Product preview
Billing counter, captain app and head-office view
Billing counter. Cashiers scan packaged and weighed items in seconds, with prices, schemes and GST applied from the local catalogue even when the internet is down. 
Customer screen. Customers pay by UPI QR, card or cash; UPI payments are confirmed on the bill automatically, so staff stop checking phones. 
Captain app. Captains take table orders on a phone; each item goes to the kitchen as a KOT and appears on the bill automatically. 
Head office. Head office sees sales, payment mix and voids for every outlet as bills sync, and pushes price changes back out centrally.
Illustrative preview
Sample screens: names, prices and figures are examples, not client data.
Industries
Counters we build POS for
Cost drivers
POS cost drivers
Target devices
Windows desktops, Android POS terminals and tablets each need testing; supporting several adds effort.
Offline depth
Offline billing with stock, credit and loyalty is more complex than offline invoices alone.
Hardware models
Each printer, scale and terminal needs integration and on-site testing.
Format-specific flows
Restaurant, grocery and apparel billing differ enough to be separate workflows.
Number of outlets
Central management, franchise permissions and consolidated reports grow with the chain.
Estimates are written from your scope, with the effort and assumptions behind each line item.
How pricing worksServices
Services involved
The disciplines a project like this draws on.
Custom software development
Software shaped around how your business runs, from approvals and inventory to billing and reports, replacing spreadsheets and disconnected tools.
Flutter development
Android and iOS apps from one Dart codebase, built by engineers who know when Flutter is the right call and when native code is needed.
Android app development
Native Android apps in Kotlin and Jetpack Compose, designed for entry-level phones, patchy networks and the background limits of popular Android brands.
API development
Secure, documented REST and GraphQL APIs, plus integrations that connect your apps to payment, logistics, GST, messaging and business systems.
Admin panel development
Back-office dashboards built around your team's daily tasks: order queues, approvals, catalogue management, payouts, reports and audit logs.
FAQ
Frequently asked questions
Will billing keep working if the internet goes down?
Yes, that is a core design requirement. The POS app keeps products, prices, taxes and recent customers on the device, and invoices are numbered from a series reserved for that counter, so offline bills do not collide with other counters. Card and UPI payments still need connectivity on the payment device, but cash billing continues. When the connection returns, sales, stock movements and payments sync to the server in order.
Which printers, barcode scanners and weighing scales are supported?
Most thermal receipt printers that accept ESC/POS commands work over USB, network or Bluetooth. USB and Bluetooth barcode scanners generally behave like keyboards and need little integration. For weighing scales, we usually read the barcode labels the scale prints, which embed weight or price, rather than connecting to the scale directly. We confirm your exact models and test on them before rollout.
Can customers pay by UPI with automatic confirmation at the counter?
Yes. The POS requests a dynamic QR code for the exact bill amount from your payment gateway, shows it on a customer-facing screen or prints it, and marks the bill paid when the gateway confirms. Staff no longer check phones for payment screenshots. Static QR codes and soundbox devices also work, but matching those payments to bills is less direct, so they suit smaller stores.
Can a chain manage menus and prices centrally but allow outlet-level changes?
Yes. Head office maintains the master catalogue, prices, taxes and schemes and pushes them to outlets on a schedule or immediately. You decide which fields outlets may override, such as local specials or availability, and every override is logged. Franchise outlets get their own reporting views, while head office sees consolidated sales, payment modes and margins.
Related
Keep exploring
Next step
Design a POS for your counter
Tell us your store format, hardware and billing volume. We will propose the POS scope and send a line-item estimate.