Enterprise Dashboard
Making supply chain data easier to act on.
A modular analytics dashboard for enterprise buyers of perishable goods, built to replace scattered spreadsheets and disconnected reports.
~$2.4B
8
6
4
iTrade's Clients
Constraints
Complex Data
Inventory, shipments, contracts, pricing, and quality metrics, all updating constantly. The interface had to simplify without hiding what mattered.
Legacy Integration
The dashboard sat on existing ERP and supply chain infrastructure. Available data structures and API limits set the boundaries for every widget.
Time-Sensitive Work
With perishable goods, delays cost money right away. The interface had to put exceptions and urgent items ahead of passive reporting.
Spreadsheet Habits
Buyers lived in spreadsheets and legacy dashboards. The new tool had to feel modern without breaking the workflows they relied on.
What the dashboard had to do.
Before designing anything, I set three criteria the dashboard had to meet:
Show the top priority on landing.
A buyer sees their most urgent issue without exporting anything.
Cut the manual work.
Fewer spreadsheet exports, less report assembly by hand.
Earn daily use.
Something buyers return to every day, not a one-time login.
Minimal widgets, complete drilldowns.
The dashboard's core rule came from one widget: the Commodity Price Index. It took four rounds with buyers and developers to get it right, and every other widget followed what we learned.
Data tables and executive summaries buyers shared with us.
My Thoughts
Show every product in the commodity family, with toggles so buyers could explore the data without switching views.
User Feedback
The chart was on the right track, but buyers needed one high-level metric first. The detail still mattered, mostly for executive reports, but it didn't belong up front.
My Thoughts
I stripped out the secondary data. Before polishing the visuals, I wanted to confirm we were surfacing the right metric.
User Feedback
Closer. The high-level number and how it compared to the market mattered most, as long as the full data stayed reachable.
My Thoughts
I locked which KPIs to surface and set the widget's size. That size became the base unit for every widget on the grid.
User Feedback
Buyers needed to switch the comparison period. With that, this version worked.
My Thoughts
On our stack, icons and images inside widgets increased load times. I also needed to understand exactly how each metric was calculated.
Developer Feedback
Icons would require many extra backend calls and slow the product down. Engineering also needed full specs for the drilldown and the KPI calculations.
Final widget and drilldown.
Desktop-first, on purpose.
Every buyer we spoke with did this work on a desktop or laptop, and the thing they asked about most was how spreadsheets and exports would work. So the grid was designed for large screens, built around the widget size set during the Commodity Price Index iterations.
Widget Anatomy
The dashboard was built on the company design system, so the visual rules were already set. The design work was deciding what each widget needed to do, and making every widget behave the same way.
Dashboard Mockup
Widget Library
What the MVP does.
6 key features.
Widget Configuration
Data Table Demo
Subject matter experts made the domain readable.
Perishable supply chains run on jargon. Working closely with SMEs let me design for how buyers actually worked, not how I assumed they did.
Minimal widget, complete drilldown.
One clear number up front was more useful than a detailed chart. The detail still mattered. It just belonged one click deeper.
Sketch live with the people who use it and build it.
My most useful sessions were live sketching with buyers, PMs, and developers. Hearing constraints early, like the load cost of icons, shaped the design before anything was built.
