Walmart
2025-26
A scorecard redesign that gave suppliers the lead time to prevent charges, not just see them.

Overview
Walmart charges suppliers when a shipment misses its requirements, like a wrong barcode or damaged packaging. Suppliers use a scorecard to see those charges and find the item behind each one, so they can fix the cause or dispute the charge.
The old scorecard told suppliers they’d been charged, but not why. Without the item and the reason behind the charge, there was nothing to act on, so the charges kept coming.
The Impact
Problem
Suppliers struggled to find their data, so they kept asking merchants.
Finding the item behind a charge was frustrating, so the email was simply easier.

Solution
Answers suppliers can find on their own.
One screen now shows the biggest defects at a glance and the item behind each charge, in two clicks.
SOLUTION 01
See the biggest problem first.
A visual dashboard puts the largest defects top left, with details on hover and only charged items shown.
SOLUTION 02
Two clicks to the evidence.
The path is set once in dropdowns, and each row opens in place to show the item and its evidence.
Before & after
Research
Watching where suppliers got stuck.
Supplier question Merchants every day, so I ran sessions with them as stand-ins for suppliers, watching how they moved from a charge to the item behind it.
Supplier quote
"I know there is a charge, but finding the exact charge and item details takes time. We find it easier to ask for details through a downloaded report than to go on the platform."
Interview participant
Supplier
Why I restructured the information architecture
The data was all there. It was organized in a way that made finding anything harder than asking a person. Fixing the visual layer alone would not have changed that, so I reorganized around the question suppliers arrive with and brought the scorecard, the item, and the evidence onto one screen.

Key insights
Suppliers arrive with a question.
Every session started from a charge email, not from browsing.
Both scanning and reaching the item were hard.
Suppliers struggled to spot their biggest defect, then stalled again trying to reach the item behind it.
The visual showed size, but not what it was a share of.
Without that, no one could tell which defect was actually worse.
So I reorganized around the question. Fixing the visuals alone wouldn’t help. I rebuilt the structure so the scorecard, the item, and the evidence live on one screen.
Ideation
01 Finding the biggest defects fast
I built three visual directions at real data volume. The other two broke down at scale or hid the numbers, while the treemap let people compare by size at a glance. Merchants also pushed to keep it, since suppliers already knew how to read it. So the treemap stayed, and I rebuilt it.

What user testing changed.
02 Reaching one item in a dense table
I tested three table layouts. Each one drew the defect hierarchy as layout, and each broke in a different way. The fix was to make the hierarchy a control instead: set once in dropdowns, with one table of items underneath.

What user testing changed.
Reflection
Let the evidence make the hard calls.
Proxies tell you what users report, not what they do
Merchants stood in for suppliers. With direct access, I’d watch suppliers go from email to charge myself.
When two groups disagree, test it.
Design leadership wanted the treemap gone, and merchants wanted it kept. I tested the alternatives at real volume instead of arguing.
A missing component is a problem to solve, not a wall.
The treemap wasn’t in our design system, so I found a free library that used our styles and brought it to engineering as a cost question.


