Zero-Internet Operations & Sync Resilience
NespoCASH is built on an Offline-First architectural core. You can run counter checkouts, stock counts, and journal postings without active internet connectivity.
[IMAGE - Network status indicator showing offline mode badge and pending sync queue counter]
How Offline Storage Works
- All product catalogues, customer accounts, and historical ledgers are stored securely in local browser IndexedDB.
- When offline, every sale transaction is signed locally and placed in the Action Queue.
- Upon reconnection, the background sync engine pushes queued operations to Firestore automatically.
Offline-First Engine Architecture & Sync Lifecycle
| Subsystem Component | Storage Technology | Sync Trigger | Conflict Strategy |
|---|---|---|---|
| Catalog & Price Lists | Browser IndexedDB | Instant Local Read (0ms) | Cloud-Authoritative with Local Cache Fallback. |
| Sales Cart & POS Checkout | IndexedDB Transaction Store | Immediate Execution | Committed locally first; queue synced on internet return. |
| Pending Action Queue | Persistent Mutation Log | Network Reconnection Event | Sequential FIFO execution with cryptographic replay validation. |
| Cloud Firestore Sync | Secure RPC Endpoints | Continuous Background Thread | Server-authoritative timestamping prevents duplicate invoices. |
Note: Local transactions balance immediately within your local ledger and synchronize cryptographically upon cloud reconnection.