You get a notification: a customer has filed an A-to-z Guarantee claim against one of your orders. On its own, that sounds minor — a refund dispute between you and one buyer. It isn't. A-to-z claims feed directly into your Order Defect Rate, and your Order Defect Rate is one of the few metrics Amazon will suspend your entire account over. One claim is an inconvenience. A pattern of claims, especially ones that were never your fault, is an existential threat to your selling privileges.
Most private label sellers only learn how the A-to-z process works after their account health has already taken a hit. This guide explains what the guarantee actually covers, which claims you can and can't dispute, and the exact process for contesting one before it damages your account.
Don't ignore a claim notification. Amazon gives you a short window — typically a few days — to respond with evidence before the claim is automatically granted in the buyer's favour. A granted claim almost always counts against your Order Defect Rate, whether or not you were actually at fault.
What Is the A-to-z Guarantee?
The A-to-z Guarantee is Amazon's buyer protection programme. It promises customers a full refund if an order from a third-party seller arrives damaged, defective, significantly different from its description, very late, or not at all — and the seller doesn't resolve it directly first. For Amazon, it's a trust mechanism: buyers feel safe ordering from any seller on the platform because Amazon itself backs the transaction.
For sellers, it means Amazon — not you — decides whether a claim is valid, usually based on the buyer's account of events and whatever evidence you submit. If Amazon can't reach you, or your response doesn't satisfy the reviewer, the claim is granted by default and the money comes out of your account.
When a Claim Is Usually Valid (and When It Isn't)
⚠️ Likely to Be Upheld
Item genuinely never arrived and tracking shows no delivery; item was materially different from the listing (wrong size, wrong variant sent); item arrived damaged or defective through your fault as the seller; you failed to respond to the buyer's return or refund request within the required window.
✅ Worth Disputing
Tracking shows successful delivery but the buyer claims non-receipt; buyer's remorse dressed up as "item not as described"; the issue is a carrier failure (lost in transit) that falls under Amazon's own shipping guarantees rather than your performance; the buyer never contacted you before filing, in breach of Amazon's own policy requiring buyers to try seller resolution first.
The key distinction is this: Amazon's policy requires most buyers to attempt to resolve the issue with you directly before filing an A-to-z claim. When a buyer skips straight to a claim without contacting you, or misrepresents what happened, you have real grounds to dispute — but only if you respond with evidence before Amazon's deadline.
Why A-to-z Claims Matter More Than a Bad Review
A one-star review stings but doesn't touch your selling privileges. An A-to-z claim is different because it's one of the three inputs to your Order Defect Rate (ODR), alongside negative feedback and chargebacks. Amazon's target is to keep ODR under 1%. Because most sellers process relatively few orders per week per ASIN, it can take surprisingly few granted claims to push a struggling account over that line — and ODR breaches are one of the most common triggers for account suspension.
There's a second cost too: granted claims paid out of your account can include the full order value, and in cases involving FBA inventory loss or damage, Amazon may not separately reimburse you for the product even though the customer already received a refund.
How to Dispute an A-to-z Claim: Step-by-Step
Once you're notified of a claim, move quickly. Amazon's review window is short and claims default to the buyer if you miss it.
Open the Claim in Seller Central
Go to Performance → A-to-z Guarantee Claims. Read exactly what the buyer alleged and what resolution they're asking for. Note the response deadline — this is non-negotiable.
Pull Your Evidence Immediately
Tracking showing confirmed delivery with timestamp and signature where available; your message history with the buyer (or proof they never contacted you); proof of the item sent (SKU, batch, photos at time of dispatch); your returns and refund policy as stated on the listing.
Submit a Clear, Evidence-Led Response
State plainly what happened, reference your evidence by name, and address the buyer's specific claim point by point. Avoid generic templates — reviewers see those constantly and they carry less weight than a response that engages with the actual complaint.
If Granted Unfairly, Request a Reconsideration
If the claim is granted despite strong evidence, you can appeal through Seller Support by opening a case referencing the claim ID and resubmitting your evidence with a concise explanation of why the decision should be reversed. Reconsiderations aren't guaranteed, but documented, policy-based appeals get overturned more often than vague ones.
Track the Outcome Against Your ODR
Check Account Health after the claim resolves to confirm whether it was counted against your Order Defect Rate. If you believe a granted claim was recorded in error even after appeal, you can request a metric review, though this is a separate process from the claim dispute itself.
What Evidence Actually Moves the Needle
Generic statements get ignored. Specific, verifiable evidence gets read. Before you respond to any claim, gather:
How to Reduce A-to-z Claims Going Forward
- Respond to buyer messages within 24 hours. Most claims happen when a buyer feels ignored after trying to resolve an issue directly — a fast, helpful reply often stops a claim before it's filed.
- Keep listings accurate. Mismatched images, vague sizing, or missing variant information are the single biggest driver of "item not as described" claims. This overlaps directly with reducing your return rate generally.
- Use trackable shipping for every order, including FBM, so you always have delivery proof on file.
- Resolve legitimate issues proactively with a refund or replacement before the buyer escalates — a claim you pre-empt never gets filed.
- Monitor your Account Health dashboard weekly so a cluster of claims is caught early, before it compounds into an ODR breach.
- Audit FBA inventory handling — damaged-in-warehouse claims are often an Amazon fulfilment failure, not a seller one, and are usually the most winnable disputes.
Facing an A-to-z claim or a shaky account health score?
StoreStride manages account health alongside PPC and listing optimisation for private label sellers — disputing unfair claims, tightening listings to cut defect rates, and keeping your ODR clear of trouble. Get in touch today.
Get Free Amazon PPC Audit →Common Questions About A-to-z Guarantee Claims
How long do I have to respond to a claim?
Amazon typically gives you a few days from notification to submit your evidence, with the exact deadline stated on the claim itself in Seller Central. Miss it and the claim is usually granted by default. Respond as soon as you're notified rather than waiting until the deadline.
Does a granted A-to-z claim always hurt my account?
Granted claims are generally counted toward your Order Defect Rate, though Amazon does distinguish between claim types in some cases. Either way, treat every granted claim as something to review and, if the facts support it, appeal rather than assume it will have no impact.
Can buyers file a claim without contacting me first?
Amazon's policy asks buyers to attempt resolution with the seller first in most cases, but enforcement isn't absolute and some claims do get filed directly. When a buyer skips that step entirely and you have no message history from them, that's a strong basis for a dispute.
What happens if I lose too many claims?
Repeated granted claims push your Order Defect Rate toward Amazon's threshold. Crossing it can trigger a performance notification, a request for a Plan of Action, and in sustained cases, suspension of your selling privileges until the account health issue is resolved.