Walmart

2025

What if suppliers knew what changed before it became a charge?

Walmart’s transportation suppliers manage 50 to 100 shipments a day. When a pickup time, carrier, or delivery date changes and no one catches it, it can turn into a charge.

The only place to see those changes was a desktop portal. Freight moves 7 days a week. Supplier teams work 5. Alerts said something had changed, but not what, so suppliers had to log in to find out.

Role

Senior UX Designer (lead)

Timeline

November 2025 to January 2026

Team

2 product managers, 5 engineers, 1 UX writer

Deliverables

Primary research · MVP scope · High-fidelity native designs · Working prototype · Product vision

Role

Senior UX Designer (lead)

Timeline

November 2025 to January 2026

Team

2 product managers, 5 engineers, 1 UX writer

Deliverables

Primary research · MVP scope · High-fidelity native designs · Working prototype · Product vision

Overview

Why I started with one job, not the whole app.

No one owned mobile for these suppliers, so I started it. Instead of putting the whole portal on a phone, I scoped the MVP to the one job research said mattered most: catching critical changes.

I led it from research to a working prototype and tested it with 7 suppliers. The project was paused during an org restructure, before build.

Impact

0 → 1

Started Walmart’s first mobile track for transportation suppliers

0 → 1

Started Walmart’s first mobile track for transportation suppliers

Transportation first

Chose the suppliers where a missed change costs the most

Transportation first

Chose the suppliers where a missed change costs the most

Scoped to one supplier type so it could ship first

One job instead of a full app, so a working prototype reached 7 suppliers sooner

Scoped to one supplier type so it could ship first

One job instead of a full app, so a working prototype reached 7 suppliers sooner

Problem

When a missed change became a charge

Every alert said something changed, but not what or on which load. To find out, suppliers had to log in to the desktop portal and search for the load themselves. Urgent changes looked the same as routine updates.

There was no mobile experience to improve, so research had to decide what to build. 3 sessions with 7 suppliers to see how they caught changes today and where things slipped.

01

It cost suppliers time

Every alert meant another login, across 50 to 100 shipments a day.

02

It turned missed changes into charges

A change no one saw in time became a cost to the supplier.

03

It let urgent changes slip

Urgent updates looked routine, and on weekends no one was at a desk to see them.

Design Decisions

Design decision 01

One tap to everything needed to act

Before, getting the details meant going back to the desktop portal and finding the load. That’s the step suppliers couldn’t take when they were away from their desk.

I designed the alert detail to show everything on one screen: the change history, PO, carrier, and dates. For anything else, suppliers can search by PO or load, the way they already look things up.

Trade-off: Starting with transportation only meant updates from other areas stayed on web for now. Because the categories already matched web, adding them later wouldn’t need a redesign.

"The subject line just says 'pickup time change.' I still have to log in to find out what actually changed."

Interview participant

Transportation supplier (paraphrased from session notes)

Design decision 02

Suppliers choose what reaches them

Every supplier’s operation is different, so one alert setting for everyone wouldn’t work. Suppliers pick which updates matter, whether they get push or in-app alerts, and how often.

I kept the categories consistent with web notifications, so suppliers have one system to learn, not two. Mobile starts with transportation only, and shows more detail than web, because suppliers read it away from their desk.

Trade-off: View now, act later. Suppliers could see everything on their phone, but taking action, like updating or disputing a load, still happened on desktop. That kept the MVP small.

Design decision 03

Rewriting the alerts with our UX writer made them easier to scan

On a phone, the alert is the whole experience. Most suppliers would read it and decide in seconds, without opening anything else. Research showed suppliers think in loads and PO numbers, not notification types. So I partnered with the UX writer to rewrite every alert from the supplier’s side. Each alert leads with what changed, then which load.

Before: Pickup window updated - Load 88901771
After: Pickup updated Load 88901771

  1. What changed: the update comes first, in plain words

  2. Which load: the number suppliers already search by

  3. Status icon: an icon shows the type of update at a glance. The blue info icon marks a routine change like this one. Urgent changes get a warning icon, so they stand out from routine updates.
    New dot: the red dot sits next to the time, so suppliers can see what's unread without it competing with the update.

Reflections

Small and proven beats big and planned.

Starting narrow built trust.

One working job, tested with real suppliers, said more than a full app concept.

Words are design too.

The biggest fix was what the alert said, not how it looked.

A paused project still counts.

The research, the MVP, and the vision for what comes next are ready if it picks up again.

Next, I’d measure it

Missed critical changes and logins per shipment would show if the MVP worked.

© 2026 Akanksha Kulkarni Portfolio