Context
Extending a mature web-based ERP supply chain platform into environments with little to no connectivity required a different operating model. The system supported critical health commodity supply chain operations, including forecasting, procurement, inventory distribution, and last-mile delivery.
The requirement was not to replace the parent platform, but to create an offline-capable extension that could operate independently while remaining aligned with the core system.
The Root
- Offline-first Architecture
- Lightweight Synchronization
- Cross-platform Deployment
- Delta-based Distribution
- Low-connectivity Operational Support
The Challenge
The original platform was designed around online access. The new requirement changed the operating model. The offline solution needed to:
- Support disconnected field operations
- Synchronise safely with the parent cloud platform
- Minimise impact on the existing ERP ecosystem
- Work across multiple desktop operating systems
- Preserve familiar workflows to reduce retraining
- Support updates in low-bandwidth environments
The real challenge was designing a practical offline operating model around an existing mature platform without creating instability in the parent system.
What Was Done
Lightweight Synchronization Layer
Designed a lightweight HTTP-based synchronization layer between the offline desktop application and the parent cloud platform. The goal was to allow offline operations while keeping the parent system stable, extensible, and minimally affected by the new deployment model.
Cross-Platform Desktop Architecture
Chose a web-based desktop application model with local SQLite storage, avoiding separate native implementations for each operating system. This improved code reuse, delivery speed, cross-platform consistency, and long-term maintainability, while also matching the existing team’s capability and learning curve.
Low-Bandwidth Application Updates
Introduced a custom update distribution mechanism using binary diffing, allowing users to download only application deltas instead of full installers. This supported greater use in low-connectivity areas by reducing update bandwidth requirements by approximately 90%.
Delivery Under Time Constraints
The first operational version was delivered in approximately 12 weeks. That required keeping scope, architecture, synchronization design, and delivery sequencing tightly aligned from the start.
Outcome
The platform extended critical supply chain functionality into offline-capable environments while remaining connected to the broader ERP ecosystem. Key outcomes included:
- Delivery of the first version within approximately 12 weeks
- Offline operation for low-connectivity environments
- Cross-platform desktop deployment with strong code reuse
- Approximately 90% reduction in update bandwidth through delta-based distribution
- Support for health commodity supply chain workflows across South Asia, Southern Africa, and Southeast Asia
- Use in national and government-level health supply chain environments
What This Represents
Offline-first systems fail when real operating conditions are treated as edge cases. In this environment, connectivity, deployment, synchronization, retraining, bandwidth, and parent-system impact all had to be considered together. Experiences like this shape how Rootstone approaches systems that must operate under constraints, not just under ideal technical conditions. Because operational continuity is not achieved by code alone. It comes from architectural and delivery decisions that reflect the environment the system must operate in.
With the right architecture, data can become useful without compromising performance, privacy, or long-term system sustainability.
Note: This example reflects founder experience gained through prior engineering and technology leadership roles before Rootstone. It is not presented as work delivered by Rootstone as a company. Client names and identifying details have been omitted to preserve confidentiality, while focusing on the type of systems, constraints, and decisions that shape Rootstone’s approach today.
