Case study · Logistics & supply chain · 2026
A web dashboard for logistics operations teams who monitor hundreds of shipments a day. The job: help people see what needs attention right now and act on many shipments at once, without losing their place.
Operations teams start every day with the same question: how are we doing, and what needs me right now? The original dashboard tried to answer everything at once. It showed more than 40 metrics on one screen, charts in different styles and no visual hierarchy, so nothing stood out.
When everything looks equally important, people scan the whole screen every time. The one delayed shipment that actually needs action gets lost among numbers that don’t.
I started from the decisions people make, not from the data that was available. That left three numbers that answer the morning question: total shipments, on-time delivery rate and active issues. Each one shows its change against the previous period.
Under them sits one main chart, shipments over time with delivered and delayed lines, plus a status breakdown, recent alerts and the latest shipments. Everything else moved to the pages where it is actually used.
Operations teams rarely deal with one shipment. On a busy day they create, update and resolve dozens at a time, so the whole product is built around working in bulk, not one row at a time.
The Create shipment form lets people add several shipments in one flow. Each shipment collapses into a single line when it’s done, smart defaults fill in the obvious fields, and one button creates them all.
After creating shipments, a side panel opens straight away. It shows the details, the tracking timeline and any issue that needs action, such as a customs delay waiting for documents. People can move between the selected shipments (1 of 5, 2 of 5…) without leaving the page or losing their scroll position.
The full shipments view combines filters by status, carrier and date with multi-select and bulk actions: edit, change status, export and delete. Status badges are interactive, so a shipment can move from In transit to Delayed with one click, right in the table.
Operations don’t stop at 6pm. FLUX follows the system theme or lets people switch manually, and the dark theme was designed as a real theme with its own contrast checks, not simply inverted colours.
Logistics rarely goes exactly to plan, so empty, loading and error states were designed as part of the product, not left for later. A new account explains what to do first, loading uses skeletons in the shape of the real content, and errors say what happened and offer a way forward: Try again or Contact support.
A small, strict system keeps dense screens readable:
A dashboard is not a place to show all the data. It’s a place to decide what to do next.
Have a project like this?
Tell me what you’re working on, and I’ll send you a short brief made for your project.
Start a project