Designing an Inbound Visibility System for Seller Operations at Scale

Amazon (FBA Seller Experience)
Designing an Inbound Visibility System for Seller Operations at Scale

I defined a system for inbound visibility across Amazon’s FBA network, enabling sellers to understand, track, and act on inventory shipments throughout the entire lifecycle.

Inbound logistics is one of the most critical parts of the seller experience, yet it was fragmented across tools, unclear in status, and difficult to act on. This resulted in millions of support contacts and operational inefficiencies at scale.

This work reframed the problem from improving individual tracking features to designing a visibility system that enables decision-making across the shipment lifecycle.

Overview

My Contribution

I led the design of a system that connects shipment tracking, operational workflows, and performance monitoring into a unified experience.

This included:

  • defining a lifecycle model for inbound shipments (creation → tracking → receiving → availability)
  • designing the Shipment Events system to surface real-time status and milestones
  • transforming the Shipping Queue into an operational control center
  • defining a North Star dashboard for monitoring inbound performance
  • establishing reusable UX patterns adopted across multiple teams

Rather than redesigning isolated screens, I focused on creating a scalable system for visibility and action across seller operations.

Research
Strategy
UX/UI Design
Prototyping
Usability Testing

The Problem

Sellers lacked clear answers to critical operational questions:

  • Where is my shipment?
  • What is happening right now?
  • When will inventory be available?
  • What action do I need to take?

Research with 50+ sellers showed that the issue was not lack of data, but lack of usable visibility. Sellers could not understand shipment state, interpret performance, or determine next steps .

This resulted in:

  • high support dependency
  • operational delays
  • increased errors in shipment handling

The problem was not missing features—it was the absence of a system that supports decision-making under uncertainty.

Defining the System

The system was designed as a unified visibility layer across the shipment lifecycle.

It consists of three core components:

  • Shipment Events: A structured timeline translating backend logistics data into clear, actionable states (e.g., in transit, delayed, action required)

  • Shipping Queue: An operational hub where sellers manage shipments, resolve issues, and take action directly within context

 

  • North Star Dashboard: A performance layer providing visibility into inbound health across shipments

These components are connected through a shared model of status, alerts, and actions, ensuring consistency across experiences.

This transforms inbound logistics from a fragmented set of tools into a cohesive system for monitoring and decision-making.

Key Decisions & Tradeoffs

I introduced a status-driven model to simplify complex logistics data, prioritizing clarity over granularity.

I embedded actions within context, reducing the need for cross-navigation but increasing design complexity across systems.

I redefined the shipping queue from a passive table into an operational control center, prioritizing decision-making over data display.

I designed mobile as a primary operational surface rather than a secondary experience, ensuring sellers could manage shipments in real time.

These decisions consistently prioritized actionability and clarity over system simplicity.

Handling Uncertainty & Failure

Inbound logistics involves constant variability, including delays, missing inventory, and processing inconsistencies.

The system addresses this by:

  • surfacing clear shipment states and transitions
  • highlighting issues requiring action
  • providing visibility into delays and processing timelines
  • enabling recovery through contextual actions

By making uncertainty visible and actionable, the system reduces reliance on support and improves operational control.

Example System Behavior

A seller tracking a shipment can:

  • view its current state within a structured timeline
  • identify delays or issues requiring action
  • resolve problems directly within the shipping queue
  • monitor overall inbound performance through the dashboard

This allows sellers to move from reactive support dependency to proactive management.

Demo:

Impact & Adoption

This work reduced support demand by 5.83 million contacts, driving a 10% decrease in volume and delivering $2.3M in annual savings.

It established a unified visibility system across inbound logistics workflows, improving clarity and reducing operational overhead at scale.

The design introduced reusable patterns for status, alerts, and actionability that were adopted across multiple teams, extending the impact beyond a single product area .

Broader Implication

Operational systems fail when users cannot make decisions.

This work demonstrates how visibility systems can transform complex workflows by shifting from:

  • fragmented tools to unified systems
  • data presentation to decision support
  • reactive workflows to proactive management

At scale, this is not just a UX improvement—it is a system-level transformation of how operations are managed.

Closing

I focus on designing systems that enable decision-making in complex, high-variability environments.

If you are building operational platforms that need to scale across workflows and teams, I can help define how those systems should work.

Let’s collaborate

Related case studies

Designing a Safety-Critical AI System for Crisis Response
AI Design
Research
Designing an Inclusive Payment System for Global Commerce
Research
Strategy
Concept Design