Offline is the contract, not a feature
Florix Engineering · 12 May 2026 · 1 min read
Ask a field rep where they lose signal and they'll laugh: loading docks, basements, rural routes, the back office of every café on the strip. If your CRM needs bars to work, it doesn't work where the selling happens.
Degraded mode isn't good enough
Plenty of apps "support offline" — they cache a read-only view and break the moment you try to change anything. That's a demo feature, not a contract.
For Florix, the contract is simple:
- The entire rep workflow runs with zero connectivity.
- Everything queues in a durable local outbox that survives app restarts.
- On reconnect, changes reconcile conflict-free — no duplicates, no lost edits.
How reconcile stays clean
| Concern | Approach |
|---|---|
| Duplicate records | Client-generated stable IDs |
| Conflicting edits | Last-writer-wins per field, with an audit trail |
| Partial sync | Idempotent, resumable outbox |
The upshot: a rep can run a full day in a dead zone, and when the phone finds signal in the car park, everything just lands. No spinner, no cleanup, no lost work.