A warehouse system that replaced a legacy desktop program
A desktop warehouse application that deliberately mirrors the layout of the legacy system it replaces, so staff do not have to relearn their job.
- Client
- A warehousing operation
- Sector
- Logistics
- Shipped
- 2025
- Practice
- Product and platform engineering
A warehouse management application delivered as a desktop build, covering deposit and delivery recording with dashboards over the resulting data. Its defining design decision is that the navigation mirrors the client's legacy program: the same dual-sidebar shape, simplified, so the people who had used the old system for years could find everything without retraining.
The problem
The operation ran on an old desktop program its staff knew by muscle memory. Every modern replacement they had been shown reorganised the navigation, which meant retraining a workforce that was busy, and the rollout risk of that retraining was the real reason the replacement kept being postponed.
What we built
- 01
Mirror the legacy navigation deliberately rather than improving it, so existing muscle memory still works.
- 02
Simplify inside each screen, where a change is invisible from the outside and costs nobody anything to learn.
- 03
Deposit and delivery recording as the core transactional surface.
- 04
Dashboards with bar and pie charts over the recorded movements, so supervisors stop exporting to a spreadsheet.
- 05
A desktop build through Tauri, so it installs and behaves like the application it replaces rather than asking staff to work in a browser tab.
What it does now
- Staff who knew the old program could use the new one without a training programme.
- Movements are recorded once and reported on directly.
- The system installs as a desktop application, matching how the operation already works.
What people ask about this work.
Should a replacement system copy the old system's layout?
Often yes, at the navigation level. The cost of a replacement is rarely the software; it is retraining and the mistakes made during it. Keeping the shape people already know, and improving what happens inside each screen, buys adoption cheaply. Reorganising navigation is a change worth making later, separately, once the system is trusted.
Why build a desktop application rather than a web app?
Because the operation already worked that way. Where staff expect an installed program, a local printer, and a window that opens with the shift, a desktop build removes friction rather than adding it. Tauri lets us ship one with web technology and a small footprint.