Case study

Turning a seller’s first A-to-z claim into a learning moment

When a third-party order goes wrong, the seller’s first A-to-z email often felt like a penalty. I redesigned that notification so it could teach.

Role: UX Designer, Amazon Seller Central
Scope: First-claim email experience and partner alignment on tenets
Key decision: Treat the first claim as a covered learning event, not only a defect
Outcome: Sixty-day U.S. results reported higher seller confidence, lower A-to-z call volume, and more seller-initiated refunds (deck-stated, unverified)

Support contacts showed what sellers did not understand

When a customer’s order from a third-party seller goes wrong and the seller does not respond in time, Amazon steps in. The customer gets a refund. The seller gets an A-to-z claim, a hit to Order Defect Rate, and an email that often felt like discipline.

I reviewed a sample of 250 Seller Support contacts tied to A-to-z. Appeals, disputes, and status questions made up large shares of the volume, and many of those contacts were marked preventable on the analysis. Sellers were not only unhappy—they were stuck.

Mapping and interviews made the gap concrete

I worked with stakeholders and domain experts to map how messaging, eligibility, disputes, and appeals connected. Seller interviews added the human version: people felt helpless, could not see what to do next in the communications they received, cared deeply about ODR, and doubted they could avoid the next claim.

Before we redesigned anything, I aligned partners on three tenets: the first claim is a learning opportunity; notifications should inform rather than discipline; avoiding future claims helps the customer and the seller.

The first-claim email had to explain, cover, and coach

The pivotal decision was to treat the first claim as a covered learning event. The email led with claim details, explained what an A-to-z claim is and how ODR works, stated that Amazon would cover the customer refund on the first claim, and listed concrete practices for avoiding another one. The stakes stayed visible. The tone changed.

I designed that notification. Shipping it and funding first-claim coverage were team and program moves; I do not claim them as solo outcomes.

First-claim email mock annotated with its four jobs: claim details, set expectations, cover the claim, and help the seller — Redesigned first-claim email, annotated with its four jobs: claim details up front, what happens next, first claim covered, and practices that prevent the next claim. Sample seller and order data.

Outcome

Sixty days in the U.S.

Sixty days after the update was live in the U.S., the deck reports that 88% of sellers who opened the email said they were confident or very confident they could avoid future claims, A-to-z-related call volume fell 14% (+2% week over week), and seller-initiated refunds trended toward a 30% year-over-year increase. Those figures are stated on the results slide and remain unverified in my career record.

My takeaway: when the company is willing to absorb a first failure, the notification should spend that goodwill on specifics and a short path to better behavior—not on softer adjectives.