Case study 2 of 13 · system
Rodosuper
A logistics ecosystem with a web application, an offline-first Flutter app and a Socket.io gateway to support goods checking and operational data synchronization.
01 · Context
Before designing the interface, we understand the environment.
The operation connects physical goods checking, a legacy ERP and different data formats in environments where network access is not always available.
02 · Challenge
What needed to be solved
Goods checking depended on a legacy MySQL ERP with heavy queries that stalled operations at critical times, alongside recurring counting bugs that caused rework between physical goods and recorded data.
On the factory floor, total dependence on the network made operations fragile: connection drops interrupted scans, while manual paper processes reduced traceability and increased human intervention.
The environment also involved different layouts, delimiters, XML files and barcodes, requiring an adaptable solution decoupled from the legacy system.
03 · Decisions
Project decisions
- 01
Separate the operational hub, the goods-checking app and the synchronization gateway to reduce coupling with the legacy system.
- 02
Prioritize offline mobile operation and incremental synchronization when connectivity returns.
- 03
Centralize interpretation of different layouts in an extensible parser strategy.
04 · Outcome
The outcome
This case study documents a web and mobile ecosystem designed for offline goods checking and integration with heterogeneous operational data.
Interface highlights
The product in detail
Consistently framed images to compare hierarchy, components and flows.