FinBook
Dual-Runtime Business Accounting & Offline-First POS Architecture
“Bridging offline counter reality with real-time financial reconciliation—without losing a single transaction to dropped packets.”
Executive Overview
FinBook is an integrated business bookkeeping, inventory management, and POS ecosystem designed for high-velocity retail. It deploys a dual-runtime architecture: an offline-first native Android POS client for frontline billing and Udhaar tracking, alongside a React/Vite analytics portal for backoffice multi-store audits.
The Problem: Spotty Connectivity on the Frontline
Small-to-medium retail storefronts across regional markets face intermittent 3G/4G connectivity that paralyzes cloud-only SaaS billing systems.
- Shopkeepers cannot wait 4 seconds for a cloud API response while customers wait at the register.
- Network outages cause checkout lines to freeze, resulting in lost sales and unrecorded credit.
- Conversely, pure desktop spreadsheets trap financial records on a single register, preventing owners from monitoring revenue remotely.
The Constraints: Instant Counter Speed with Cloud Auditability
The system needed to guarantee instant sub-millisecond local billing with eventual consistency cloud synchronization.
Offline-First SQLite Architecture
All invoice entries, stock decrements, and customer credit entries write directly to local Room SQLite. The counter operates with 100% functionality even during complete ISP outages.
Dirty-Flag Reconciliation Queue
Offline mutations are queued with monotonic timestamps and dirty-flag row indicators (is_synced: false). When connectivity recovers, mutations sync to Supabase PostgreSQL.
Dual-Runtime Synchronization Pipeline
┌────────────────────────────────────────────────────────┐
│ FRONTLINE RETAIL (ANDROID POS) │
│ Native Kotlin · Room SQLite · Local Write: < 4ms │
└───────────────────────────┬────────────────────────────┘
│ (Async WebSocket Sync)
▼
┌────────────────────────────────────────────────────────┐
│ CENTRAL CLOUD RECONCILIATION │
│ Supabase PostgreSQL · Row-Level Security │
└───────────────────────────┬────────────────────────────┘
│ (Real-time Pub/Sub)
▼
┌────────────────────────────────────────────────────────┐
│ BACKOFFICE PORTAL (REACT / VITE) │
│ Inventory Audits · Double-Entry Ledger · Analytics │
└────────────────────────────────────────────────────────┘Native Android Architecture
Engineered with Kotlin, MVVM, Dagger-Hilt dependency injection, and Room SQLite ORM. Strictly decoupled domain, repository, and presentation layers.
Web Management Console
React 18, Vite, and Tailwind CSS subscribing to Supabase PostgreSQL real-time change streams for automated P&L statements.
Double-Entry Integrity & Zero-Compute PDF Invoicing
Bookkeeping cannot tolerate floating-point rounding errors or partial writes. Every invoice is executed within atomic SQLite and PostgreSQL transactions using integer minor units (paise), enforcing that debits and credits sum to zero.
Rather than deploying expensive cloud serverless functions running headless Chromium (Puppeteer) to generate PDF invoices, FinBook renders invoice layouts client-side using jspdf and html2canvas in under 350ms with zero hosting compute overhead.
“By decoupling frontline point-of-sale execution into an offline-first native SQLite runtime and federating asynchronous ledger updates to Supabase PostgreSQL, FinBook achieved sub-millisecond checkout velocity while preserving strict double-entry accounting integrity across distributed retail endpoints.”