A point-of-sale suite spanning 21 domain packages, with a Flutter terminal that keeps selling when the network drops.
- domain packages
- 0domain packages
- terminal platforms
- 0terminal platforms
- offline-tolerant selling
- 0%offline-tolerant selling
Name withheld under agreement — full walkthrough available on a call
Retail software fails at the counter, not in the demo. The terminal has to keep taking money when the internet does not, then reconcile without creating duplicate sales. We built the sync layer first and the till screen second.
The system is decomposed into 21 domain packages — registers, payments, fiscal, inventory and inventory operations, hardware, loyalty, promotions, accounting, employees, reporting, sync, omnichannel, messaging, webhooks and more. That boundary discipline is what lets a hospitality deployment and a fashion-retail deployment share a codebase without either one becoming a special case.
The terminal is Flutter, so the same build runs on the cheap Android hardware most floors actually use and on iPad where the customer prefers it. Hardware integration covers receipt printers, cash drawers and scanners.
Stack
- Flutter
- Node.js
- PostgreSQL
- Prisma
- Next.js
Benchmark
Square / Lightspeed
Same category, same scope of problem. Built by us, end to end.
Offline-first selling with conflict-safe reconciliation
Receipt printer, cash drawer and scanner integration
Fiscal and accounting module for compliant reporting
Loyalty, promotions and gift cards
Omnichannel — the same stock as the online store
Employee shifts, permissions and till accountability
Want something in this category?
We have built it once already. That means the architecture conversation starts from experience rather than from a whiteboard.
Free 30-minute technical consult. No obligation, no sales script. · We reply within one business day · You own everything we build