← Back to timeline
Amazon

Amazon Seller Central

Leading research and vision work to help sellers understand payments, inventory, and business performance with more confidence.

Across Seller Central, the challenge was not a lack of data. It was that important decisions were scattered across reports, tools, terminology, and workflows that sellers had to stitch together themselves.

My work spanned detailed user research on the Seller Central payments experience and a near-to-long-term vision for inventory analytics. In both cases, the role of design was to uncover gaps, name the right opportunities, and help sellers move from raw information to clearer action.

Product question: How might we help sellers understand what is happening in their business without forcing them to become analysts, accountants, or workflow detectives?

Amazon Seller Central inventory dashboard overview
Early dashboard direction for sales and inventory overview, including units available, inbound quantity, sales trends, SKU breakdowns, and inventory performance.

Two connected opportunity spaces

Payments research

Led detailed research into the Seller Central payments experience to uncover confusion, gaps, and opportunities for clearer financial understanding.

Inventory analytics

Created a dashboard vision that helped sellers understand sales, inventory health, SKU performance, and business trends over time.

Seller confidence

Both streams pointed to the same need: make complex business systems easier to interpret, trust, and act on.

Researching Seller Central payments

The payments research looked closely at how sellers understood money movement, reconciliation, account health, and the moments where the system failed to explain itself. The goal was to find the gaps that created avoidable support needs, mistrust, or manual work.

That research helped identify opportunity areas: clearer payment status, better terminology, stronger explanation of deductions or adjustments, and more actionable paths when something looked wrong.

The questions the dashboard needed to answer

What changed over time?
Which SKUs need attention?
Is inventory healthy?
Where should I drill down?
What is actionable?
What can replace a report?

Getting the right experts in the room

For the inventory dashboard work, I brought partner product and design teams together to discuss KPIs, seller questions, and the kinds of decisions a future dashboard should support. Before the dashboard became a design artifact, it was a shared model of what sellers needed to understand.

We worked through sales vs. inventory, inventory health, SKU data, trend views, and drill-down moments. A lot of the early alignment happened in spreadsheets before it became interface design.

Amazon inventory dashboard KPI questions
The work began by clarifying which KPIs and questions mattered for different seller roles.
Amazon Seller Central dashboard prototype
The dashboard explored trends, SKU breakdowns, sales, units, orders, inventory cost, and custom date ranges.
01 Uncovered gaps

Used payments research to identify where sellers lacked clarity, confidence, or a clear next step.

02 Aligned experts

Brought product and design partners together around KPIs, seller roles, and decision questions.

03 Built the vision

Created a near-term and long-term dashboard direction within a narrow timeframe.

04 Made data usable

Moved from static reports toward trend, drill-down, and inventory-health views.

Amazon inventory health dashboard prototype
Inventory performance concept showing inventory health, IPI score, units sold by age, and trend-based breakdowns.

The design challenge was not making more data visible. It was helping sellers know what deserved attention—and what to do next.

Impact

The work created stronger opportunity framing across Seller Central payments and inventory analytics.

Research-backed gaps

The payments research clarified where sellers lacked confidence around money movement, reconciliation, terminology, account health, and next steps.

Clearer analytical vision

The inventory dashboard work moved reporting from static downloads toward trends, drill-downs, inventory health, and SKU-level action.

Better product alignment

The work gave product and design partners a clearer model for which KPIs mattered and what questions the experience needed to answer.

Learnings

Data needs a point of view

More charts do not automatically help sellers. The experience has to guide attention toward what changed, why it matters, and what to do next.

Research creates strategy

The payments work showed that detailed UX research can identify product opportunities, not just usability issues.

Different roles need different depth

Analytical, executive, and operational sellers needed different entry points into the same business truth.