Walmart

2025-26

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

Role

Senior UX Designer, Lead designer

Timeline

June 2025 to February 2026

Team

2 product managers, 1 UX writer, 7 engineers, 11 stakeholders

Deliverables

Design research, interaction design, treemap component (net new to the design system), web platform

Role

Senior UX Designer, Lead designer

Timeline

June 2025 to February 2026

Team

2 product managers, 1 UX writer, 7 engineers, 11 stakeholders

Deliverables

Design research, interaction design, treemap component (net new to the design system), web platform

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

7 → 2 clicks

Straight to the evidence

Reaching the item behind a charge now takes two clicks, in under 45 seconds.

7 → 2 clicks

Straight to the evidence

Reaching the item behind a charge now takes two clicks, in under 45 seconds.

8 of 11

Defects got easier to spot

Suppliers found defects more easily in testing

8 of 11

Defects got easier to spot

Suppliers found defects more easily in testing

40%

Reduced chargebacks tickets

The neverending loops of chargebacks reduced significantly due to earlier defect prevention

40%

Reduced chargebacks tickets

The neverending loops of chargebacks reduced significantly due to earlier defect prevention

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.

01

Sorted by an old rule, not by cost.

No one knew why the order was set that way, so suppliers scanned the whole board to find their biggest defect.

01

Sorted by an old rule, not by cost.

No one knew why the order was set that way, so suppliers scanned the whole board to find their biggest defect.

02

Seven clicks to the evidence, and no way back.

Reaching one item ended on a separate page, so suppliers started over every time and most gave up.

02

Seven clicks to the evidence, and no way back.

Reaching one item ended on a separate page, so suppliers started over every time and most gave up.

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

Before: Seven clicks to the item, on a separate page with no way back.

Before: Seven clicks to the item, on a separate page with no way back.

After: Two clicks, with the scorecard, item, and evidence on one screen.

After: Two clicks, with the scorecard, item, and evidence on one screen.

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.

11 users

Suppliers

11 users

Suppliers

60 minutes

Moderated sessions focused on 2 workflows

60 minutes

Moderated sessions focused on 2 workflows

2 tasks

find what drives the most charges, and find the item behind one charge

2 tasks

find what drives the most charges, and find the item behind one charge

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.

01

One view instead of two.

People didn’t understand switching between views, so I merged them.

01

One view instead of two.

People didn’t understand switching between views, so I merged them.

02

Labels that show the group.

Tiles now show which group they belong to, even several levels deep.

02

Labels that show the group.

Tiles now show which group they belong to, even several levels deep.

03

Clear edges.

Tiles got stronger borders, reviewed with the accessibility team.

03

Clear edges.

Tiles got stronger borders, reviewed with the accessibility team.

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.

01

Dropdowns above the table.

Suppliers set the path once instead of on every pass.

01

Dropdowns above the table.

Suppliers set the path once instead of on every pass.

02

Evidence in the row

Comparing defects became a choice, not a scroll.

02

Evidence in the row

Comparing defects became a choice, not a scroll.

03

One table, not three.

Easier data interpretation

03

One table, not three.

Easier data interpretation

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.

© 2026 Akanksha Kulkarni Portfolio