Orders that keep moving offline.
Employees can receive orders, prepare them and coordinate deliveries on mobile devices when the network drops.
The starting point
Employees needed to receive orders on their phones, prepare them for pickup and coordinate deliveries with vehicles.
They work on the move, in warehouses and vehicles where coverage often drops. The workflow at the loading dock needed to keep moving when the network went away.
The requirements
Keep working offline. Employees needed to use the application when they lost connectivity.
Preserve the work people have entered. A dropped connection must leave locally captured orders intact.
Design for work on the move. Employees often use a mobile device one-handed or while moving.
Keep deliveries traceable. The team needs location and route information during delivery coordination.
What we built
We designed and built the application around data storage that supports offline use.
Vue and TypeScript for a typed, maintainable codebase.
IndexedDB for structured records stored on the device.
Service workers to cache the files needed to run the application.
Google Maps integration for tracking, routing and estimated arrival times.
Interface and interaction design implemented in collaboration with client and partner teams using Figma.
The architecture decisions
Keep the application and its data available. Service workers cache the application so it can start without a connection. IndexedDB stores the orders employees capture until the records can sync.
Design synchronisation from the start. The application synchronises local orders when connectivity returns. The design needs to account for duplicate records, overwritten changes and inconsistent states after synchronisation.
Build maps into the workflow. Staff use vehicle locations and route planning to coordinate order preparation with delivery.
What the project delivered
The mobile application supports ordering and delivery wherever connectivity is unreliable. It stores records locally and synchronises them when the connection returns.
The project evidence covers offline operation, preserving locally captured records and synchronising them later. Efficiency and savings figures sit with the client.
How this informs automation
The same design question applies to an automated workflow. What should happen when a step cannot run as planned?
In AI automation, plan what to do when a model is unavailable, a document is unreadable or a step runs twice. Capture intermediate state and make it possible to recover. This project shows how we designed for interruptions in a mobile workflow.
More projects
View all case studies ›What would you simplify?
Bring a task that takes up time in your day. In the first conversation, we’ll look together at what could change.