How the A-to-z Guarantee actually works

The A-to-z Guarantee is a promise Amazon makes to the buyer. If a customer pays for something on Amazon and the transaction goes wrong, Amazon steps in and puts it right, usually by refunding the buyer directly. That is why the program exists: it lets a stranger buy from a seller they've never heard of and trust that Amazon will cover them. It helps conversion rates. It does less for your blood pressure when a claim lands in your inbox.

A claim falls into one of three buckets, and the bucket decides which evidence matters.

  • Item not received. The order never showed up, or the buyer says it didn't, and there's no tracking or delivery confirmation to settle it.
  • Item not as described, damaged or defective. What arrived doesn't match the listing, arrived broken, or doesn't work as advertised.
  • Return or refund mishandled. The buyer sent something back or asked for a refund, you didn't process it correctly or quickly enough, and Amazon did it for you.
A buyer protection first

A claim being filed doesn't mean you did anything wrong. It means the buyer felt something went wrong. Plenty of claims come from buyers who are confused or impatient, and occasionally from buyers gaming the system. A claim only becomes a real problem for your account if it's decided against you and you don't fight it.

Why sellers treat this metric like a live wire

A-to-z claims differ from a normal customer service headache because they feed directly into your Order Defect Rate, and ODR is one of the handful of numbers Amazon uses to decide whether you can keep selling. A claim decided against you, an unresolved chargeback and negative feedback all count toward the same rate. Cross the threshold and you won't get a strongly worded email. You'll get a plan of action request with a listing suspension or account deactivation attached.

The number sellers cite most often as the danger line is roughly one valid claim per 100 orders. Treat that as an industry rule of thumb repeated in seller forums and by consultants, and don't read it as a figure Amazon publishes and guarantees for claims alone. Amazon doesn't give you a precise formula for when enforcement starts, and it can vary by category and account history. What Amazon's ODR help page does state is a target for the rate as a whole: keep ODR under 1%, with claims, negative feedback and chargebacks all counting toward it. Directionally, that is close enough to plan around. At any real order volume, a small handful of mishandled claims can push a thin-margin account into review territory fast.

A claim rate hovering around 1% of orders is the benchmark most experienced sellers and consultants treat as the point where Amazon's automated systems start paying closer attention to an account.

Here is an illustrative example to make the arithmetic concrete. A seller with 300 orders in the period Amazon measures has room for very few defects. Two A-to-z claims lost and one 1-star feedback make three defective orders, which is already 1%. The same three defects on 3,000 orders barely register. Smaller accounts feel every claim, which is one more reason to dispute the ones you can win.

Many sellers, including some who have been at this for years, are surprised to learn that a claim Amazon decides in your favor after you dispute it does not count against your metrics. This changed a while back and is one of the more seller-friendly policy shifts Amazon has made. A denied or reversed claim doesn't touch your ODR. So disputing every claim you have real evidence for does more than win back an individual $30 refund. It keeps your account health number clean. Sellers who absorb claims quietly because "it's not worth the hassle" take the damage twice: they lose the money, and they leave a defect on their record that didn't have to be there.

You can see your current rate in Seller Central under Performance, then Account Health, in the customer service performance section, where the Order Defect Rate breaks down into its parts. Check the claims line there weekly. A rising number of claims usually shows up before the overall rate moves.

The root causes you're probably creating yourself

Most A-to-z claims are not random bad luck. They trace back to a few habits that are entirely within a seller's control.

  • Weak listing photos and vague descriptions. If the buyer has to guess dimensions, materials or what's in the box, some of them will guess wrong and file "not as described" when the product doesn't match their assumption.
  • Slow replies to buyer messages. Amazon expects a response within 24 hours, and buyers get anxious well before that. A buyer who has messaged twice with no reply and sees the order hasn't moved is primed to file a claim instead of waiting for a third message to go unanswered.
  • FBM shipping without trackable, reliable carriers. Shipping first class with no scan events, or using a regional carrier that updates tracking inconsistently, invites "item not received" claims. You can't win a dispute you can't prove.
  • Sitting on return requests. Ignoring a return authorization request until the buyer gets frustrated and escalates to Amazon is one of the most avoidable causes on this list. Amazon has a clear expectation for how fast returns are processed, and buyers who feel stonewalled go straight to a claim.
  • Packaging that doesn't match how fragile the product is. Glassware, electronics and anything with moving parts, packed without thought for the handling it will get in transit, turn into damage claims that five extra dollars of packaging would have prevented.

A prevention checklist worth actually using

None of this is complicated. It is the kind of operational discipline that slips easily once volume picks up.

  • Photograph and measure honestly. Show the item from several angles, state exact dimensions and materials, and call out anything a buyer might reasonably assume is included but isn't.
  • Answer buyer messages the same day. Treat the 24-48 hour window as a limit you never reach, and don't plan to use all of it.
  • Use trackable shipping on every FBM order, with no exceptions. The few dollars saved on an untracked method are worth far less than an unresolvable "item not received" claim.
  • Require signature confirmation on high-value items. Anything where a lost-package dispute would be expensive to lose deserves proof that it reached a specific person.
  • Process return requests within the window Amazon sets, every time. Don't wait for the buyer to get annoyed enough to escalate. Authorize the return, issue the refund once the item is back or once policy allows, and close the loop quickly.
  • Keep a dated photo of the item right before it ships. This one habit settles more "damaged" and "not as described" disputes than almost anything else here, because it proves the condition at the moment the item left your hands.
  • Pack for the product. If it's fragile, pack it as fragile, even when a cheaper box is sitting on the shelf.

When to refund before a claim is filed

Some orders are better settled before they become claims. If a buyer messages to say an FBM parcel hasn't arrived, the tracking has stalled for days, and the carrier can't locate it, a prompt refund or replacement usually costs less than the claim that follows. Fighting a claim you can't document wastes time and can still leave a defect on your record.

A simple rule: if you have the evidence that wins the dispute (delivery scan, signature, pre-shipment photo, a buyer message confirming receipt), let the process run and dispute any claim. If you don't, and the problem is real, solve it with the buyer directly and quickly. The cases to watch are the ones in between, such as a "delivered" scan with a buyer insisting nothing arrived. For a low-value order, many sellers refund. For a high-value order with signature confirmation on file, dispute it.

What to do the moment Amazon notifies you of a claim

You get a notification through Seller Central, along with a short window, often just a few days, to respond before Amazon rules without your input. Claims also appear on the A-to-z Guarantee claims page under the Performance menu. Don't let that window lapse. A claim with no seller response resolves in the buyer's favor almost automatically, and that is the outcome that hurts your metrics.

Go to the case in your Seller Central case log and gather whatever applies to this claim type:

  • The tracking number and full delivery status. "Shipped" isn't enough; you need the scan history showing movement and final delivery confirmation.
  • Signed delivery confirmation for anything high-value. If you required a signature, this is your strongest evidence in an "item not received" dispute.
  • Screenshots of buyer messages, especially any where the buyer confirmed receipt, described the item's condition, or said something that contradicts the claim.
  • Pre-shipment photos: the dated photo showing the item's condition before it left your facility, matched against the listing.
  • Proof of return processing. For refund and return claims, include your timestamped record of when you authorized the return, when the item came back and when the refund was issued.
  • The listing content as it appeared at the time of sale. In a "not as described" claim, what the listing promised at that point matters.

Submit everything as one clear, organized response. Amazon's reviewers work through a queue, and a submission that's easy to follow gets a fairer read than a wall of unlabeled screenshots.

A response that works well has a short structure: one sentence stating the order and claim type, two or three sentences on what happened with dates, then a labelled list of attachments. For example: "Order shipped on the 3rd with signature required. Carrier tracking shows delivery and signature on the 6th (attachment 1). The buyer messaged on the 7th confirming the item arrived (attachment 2)." Keep the tone factual. Arguing about the buyer's honesty adds nothing that the evidence doesn't already show.

Appealing a claim that was decided against you unfairly

Sometimes you do everything right and it still goes the wrong way. The reviewer misses a piece of evidence, misreads the timeline, or the automated system rules before a human looks closely. You can do more than accept it.

Start in the same case log where the original claim lives. Most claim decisions have a follow-up path where you can submit additional information or explicitly request reconsideration. Use it straight away. Reference the evidence you already submitted and point out exactly what the decision appears to have missed. A vague "please review again" gets a vague result, while a specific message gets read.

If that doesn't change anything, check your Account Health page. Besides showing your metrics, it is often where you can escalate account-level disputes and see whether the claim is contributing to your ODR the way you think. For a case that is truly stuck, the seller forums have a Manager escalation path where an Amazon Seller Support manager, outside the frontline queue, reviews cases that have already gone through a standard appeal and been denied incorrectly. That path exists for exactly this situation. It shouldn't be your first move, but it is the right one when the normal channel has failed and the evidence is clearly on your side.

Document the decision as well as the order

When you escalate, include the case ID of the original claim, the case ID of any prior appeal, and a one-paragraph timeline of what happened and when. Reviewers move faster through cases they don't have to reconstruct.

FBA claims are a different animal, and sellers forget that

If Amazon fulfilled the order, an A-to-z claim tied to a fulfillment failure, such as a package lost in Amazon's network or damage in a warehouse, is about Amazon's own logistics chain. The seller should win these almost every time, provided you actually dispute them and don't write FBA claims off as unwinnable or not worth the effort.

Many sellers treat every A-to-z claim the same way regardless of fulfillment method, or don't dispute FBA claims at all because they assume Amazon will do what it wants anyway. When one arrives, check the order's fulfillment and shipping method first. If it's FBA and the failure is clearly on Amazon's side, whether lost inventory, a delivery that never scanned, or damage inside an Amazon facility, say so explicitly in your response and cite the fulfillment method as evidence. These disputes tend to resolve cleanly because Amazon's own records usually confirm what happened. Leaving an FBA-caused claim unresolved against your account when the fault isn't yours costs you account health for no reason.

Common mistakes in claim handling

  • Responding from memory. A reply that says "we definitely shipped this" without the tracking history attached is weaker than silence plus evidence.
  • Uploading evidence for the wrong claim type. Delivery proof does little for a "not as described" claim, where the listing content and pre-shipment photos matter.
  • Checking claims only when an email arrives. Notification emails get filtered or missed, so put the claims page on a daily or every-other-day check.
  • Refunding outside Amazon's system. A refund sent by another payment route leaves no record Amazon can see when it reviews the claim.
  • Letting the dispute window close on a weekend. Assign someone to cover claims when the usual person is away.

Treat this as account health

It's easy to look at a single A-to-z claim as a $25 refund fight and decide it isn't worth disputing. That calculation misses what is at stake. Every claim that goes against you unfairly and unfought is a small mark on a metric that, past a certain point, decides whether you can keep selling on the platform. And since a denied claim doesn't count against you, disputing well-documented claims costs you little: you either win the money back or at least keep your metrics clean, and either is better than absorbing it silently.

Sellers who stay out of trouble here still get claims. Nobody at real volume avoids them entirely. What they have done is build the dull habits (trackable shipping, fast replies, honest listings, quick returns, dated pre-ship photos) into their normal operating rhythm, so when a claim arrives the evidence is already there to submit. Prevention and response use the same discipline at different points in the order lifecycle, and doing both well is what keeps your account health, and your business, out of the danger zone.

Frequently asked questions

Does an A-to-z claim still hurt my account if I win the dispute?

No. If you dispute a claim and Amazon decides in your favor, it does not count against your Order Defect Rate. That is why disputing every claim you have real evidence for is worth the time. Sellers who quietly absorb claims lose the refund money and leave a defect on their record that did not have to be there.

How many A-to-z claims can I get before Amazon suspends my account?

Amazon does not publish a precise threshold for claims alone, and enforcement can vary by category and account history. The number sellers cite most often is roughly one valid claim per 100 orders, about a 1% claim rate. Treat that as a widely repeated rule of thumb from seller forums and consultants, and keep in mind that Amazon's stated target of an ODR under 1% covers claims, negative feedback and chargebacks together.

What evidence do I need to win an item not received claim?

Full tracking with the complete scan history and delivery confirmation; a "shipped" status is not enough. Signature confirmation is your strongest proof on high-value orders. Add screenshots of any buyer messages that contradict the claim, plus the listing content as it appeared at the time of sale. Submit it as one organized response, never a pile of unlabeled screenshots.

Is it worth disputing an A-to-z claim on an order Amazon fulfilled?

Dispute it. When the failure is on Amazon's side, such as a package lost in their network, a delivery that never scanned, or damage inside a facility, the seller should win almost every time. Check the order's fulfillment method first, then state explicitly in your response that it was FBA and reference that as part of your evidence.

Should I refund a buyer before they file an A-to-z claim?

If the problem is real and you can't document your side, yes, usually. A quick refund or replacement through Amazon's order tools often heads off a claim altogether. If you hold evidence that wins the dispute, such as a signature on delivery, there is no need to refund early; respond to any claim with that evidence.

Fighting an A-to-z claim right now?

SellerVine helps sellers build the documentation habits and dispute strategy that keep claim rates low and account health scores clean, before a claim turns into a suspension.

Get a free account health audit