Answer every Amazon A-to-z claim with the evidence ready, before the deadline runs out
Updated · By Ecomsellertool editorial team
Open a case the moment Amazon's claim email arrives, pull the order's ship date, tracking, delivery scan, buyer messages, return request and refunds into one packet, and match the claim to a decision table. A person then refunds, responds with evidence or waits. Amazon gives 72 hours to answer its information request and 30 calendar days to appeal a granted claim.
- Amazon says the A-to-z Guarantee covers orders fulfilled by the seller, for timely delivery and the item's condition (checked November 13, 2026).
- A customer must first give you a chance to fix the problem: you have 48 hours to answer a delivery message or a return request, and a delivery claim waits until 3 days past the latest estimated delivery date.
- If you do not answer Amazon's request for more information within 72 hours, Amazon says it may grant the claim and debit your account.
- A granted claim can be appealed within 30 calendar days; after that, its effect on your Order Defect Rate cannot be reversed.
- Order Defect Rate counts claims over 60 days and must stay under 1%; a refund issued after the claim is filed still counts.
- We found no SP-API notification or report that lists A-to-z claims one by one; the seller performance report gives claim counts only.
The step map: who runs each step
Trigger: Amazon's claim email reaching a shared mailbox, plus a check of the Manage A-to-z claims page twice a day for anything the email missed.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | Rules read each claim email in the shared mailbox, take the order ID, open one case per claim and stamp the time it arrived. A person checks the Manage A-to-z claims page twice a day and adds any claim with no case. | Rule |
| 2 | Rules pull the evidence into the case: the order's ship-by date and delivery window, the label, carrier, first scan, delivery scan and proof of delivery, the return request and its status, and every refund already issued. | Rule |
| 3 | A person attaches the buyer-message thread from Seller Central, or the helpdesk copy if your messages already flow there, so the packet shows when the customer first wrote and when you answered. | Person |
| 4 | Rules match the case to a row of the claim-reason decision table, set the best action and the owner, and work out every deadline: Amazon's 72-hour reply clock once it asks, and the 30-day appeal date if it grants. | Rule |
| 5 | An AI model writes a dated timeline and a draft response from the packet only, citing the tracking events and messages it used. It never submits, refunds or messages the customer. | AI model |
| 6 | The owner decides: refund the customer, respond to Amazon with the evidence, or wait for Amazon's request. They edit the draft and submit it in Seller Central themselves. | Person |
| 7 | Rules watch the case until it closes, alert at 24 and 60 hours on any open information request, and open an appeal case with its 30-day date when a claim is granted against you. | Rule |
| 8 | Each week rules compare the closed cases with the claim counts in the seller performance report and list claims by reason, carrier and SKU, so the causes get fixed, not only the claims. | Rule |
5 rule steps · 1 AI model step · 2 person steps. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Every refund, and whether to ask for the item back first
- Every response and every appeal submitted to Amazon, written or approved by a person
- Every message to the customer, including asking them to reverse a refund
- Which claims to appeal, and when a small claim is not worth the time
- The decision table itself: owners, value limits and which rows refund first
Which tools can run it
- A shared mailbox rule and a spreadsheet of cases with deadlines, for a few claims a month
- Zapier, Make or n8n reading the claim emails, pulling tracking from your shipping software and posting each case to Slack or a helpdesk
- Custom code on your accounts, for the Orders API, carrier and delivery-proof lookups, the decision table and the deadline clock
Systems it connects
- Shared mailbox for Amazon claim emails
- Seller Central A-to-z claims and Buyer-Seller Messages
- Amazon SP-API Orders API and seller performance report
- Shipping software or carrier tracking
- Manage Returns and refund records
- Helpdesk, Slack or a case queue
Build size: Medium
No Amazon API lists claims one by one, so the work is reading the claim email reliably, joining order, carrier and refund data per order, and keeping the clocks right.
A claim email lands on a Friday evening. The person who answers buyer messages is off until Monday, the tracking sits in the shipping software, the return request is in Manage Returns, and nobody remembers whether the customer was already refunded. By the time someone puts it together, Amazon's 72-hour request has passed and the claim is granted. A-to-z claims are rarely lost on the facts. They are lost on time and on scattered evidence. This recipe gives every claim one case, one packet and one owner, with the clock in front of them. It is one page of our automation library.
Which claim reasons need which evidence, and who decides?
Start with a written table, because a missing parcel and a broken item need different proof and different people. Each row below comes from the situations Amazon lists on its A-to-z Guarantee claims page and the evidence it names on its respond to a claim page (both checked November 13, 2026). The best action is a starting point for your own rules. The owner column is a suggestion; put your own names in it.
| Claim reason or trigger | Evidence to pull | Best action | Who decides |
|---|---|---|---|
| Item not received, tracking shows delivered | Carrier, tracking number, delivery scan, delivery address, proof of delivery or signature, photo delivery, buyer messages | Respond to Amazon with the proof; refund if proof is weak and the order is small | Customer service lead |
| Item not received, tracking stalled or no delivery scan | Tracking events, carrier claim status, first scan against the ship-by date, buyer messages | Refund or reship by agreement with the customer; open a carrier claim | Customer service lead, with shipping |
| Not delivered by the latest estimated delivery date | Ship date, first scan, promised window, any delay notice you sent | Usually refund; Amazon lists this as an automatic grant | Customer service lead |
| Shipped after the expected ship date | Order date, ship-by date, label date, first carrier scan | Refund; fix the cause in the warehouse | Operations lead |
| No valid tracking on the order | Label record, carrier, the tracking ID entered in Manage Orders | Refund; Amazon resolves delivery claims for the customer without tracking | Operations lead |
| Delivered to a different address | Order address, label address, carrier delivery location | Refund; find out why the label differed | Operations lead |
| Item not as described or damaged | Return request, your reply time, listing and condition, photos from the customer | Authorize the return or refund; respond only if the item matches the listing exactly | Customer service lead |
| Return request not answered within 48 hours | Return request time, your first action, Manage Returns status | Refund; Amazon grants these automatically | Customer service lead |
| Return received, refund not issued | Return tracking, receipt date at your warehouse, refund record | Refund at once; check why the refund rule did not fire | Finance or operations |
| Prepaid return lost or sent back for a bad return address | Return label, return tracking, your return address on file | Refund; correct the return address | Operations lead |
| Parcel undeliverable, refused or returning to you | Carrier status for the return to sender | Usually nothing to answer: Amazon refunds, debits you and says this does not affect your Order Defect Rate | No one; log it |
| Property damage or personal injury | Everything above, plus the product's safety records | Stop the queue and hand to your insurer and counsel; Amazon runs a separate process | Owner, with counsel |
Two rows decide most outcomes. Delivered-with-proof is where a response is worth writing, because the evidence can change Amazon's decision. Late, untracked or unanswered orders are where it usually is not, because Amazon lists them among the claims it grants automatically. There, the faster move is often a refund and a fix to the cause.
What is the deadline at each step of an A-to-z claim?
The clock starts well before the claim. Amazon's prevention page and claims page (both checked November 13, 2026) set these limits. The workflow puts each date on the case, so the owner sees time left, not a policy page.
| When | What Amazon expects | What the workflow does |
|---|---|---|
| Ship-by date | The carrier's first scan on or before it, with valid tracking in Manage Orders | Flags orders with no first scan before the claim exists |
| Customer's first message about delivery | A reply in Buyer-Seller Messages within 48 hours | Alerts the support queue; see support-ticket triage |
| Return request | Authorize or respond within 48 hours (Amazon calls 24 hours best practice) | Alerts at 24 hours |
| Return request with an international return address | A prepaid label or a refund within 2 days | Alerts the same day |
| 3 days past the latest estimated delivery date | The customer can now file a delivery claim | Marks open delivery issues as claim risk |
| Return received with a prepaid label | Amazon's claims page lists no refund within 5 days as an automatic grant; its prevention page asks for two business days | Refund alert at day 1 |
| Claim filed | Amazon emails you, and the claim shows in Manage A-to-z claims | Opens the case and builds the packet |
| Amazon asks for more information | A reply within 72 hours, or Amazon may grant the claim and debit you | Alerts at 24 and 60 hours, then a second person |
| Claim granted against you | An appeal within 30 calendar days, from the Option to Appeal tab, with proof of delivery or other documents (appeal page, checked November 13, 2026) | Opens an appeal case with the date |
| Appeal under review | Any information request answered within 72 hours | Same clock as above |
The table also shows why prevention work pays off. Most of the dates come before the claim is filed. A shipping delay message from your shipping exception alerts and a 24-hour reply to the buyer close the case before it starts.
How do A-to-z claims affect your Order Defect Rate?
Amazon's Order Defect Rate page (checked November 13, 2026) says the rate is the share of orders over 60 days with negative feedback, an A-to-z claim or a service chargeback. It applies only to seller-fulfilled orders, and sellers must keep it under 1%. A rate above that may lead Amazon to suspend your seller-fulfilled selling privileges or deactivate offers.
The page splits claims into two groups. Claims that count: granted to the buyer with you at fault, refunded by you after the claim was filed, orders that you or Amazon canceled, and claims pending an appeal. Claims that do not count: those Amazon finds were not your fault, those denied to the buyer, those the buyer withdraws, and property damage or personal injury claims. A claim reversed on appeal with you found not at fault comes off the rate.
That changes the refund decision. A refund after the claim is filed closes the case but still counts. So "refund or respond" is a real choice only when you have evidence that you were not at fault. When the evidence is weak, refunding fast saves time, not the rate. When it is strong, a response or an appeal is how the rate gets protected. Our account health agent watches the rate itself; this queue works the claims that move it.
As an illustration only (not client data): a brand with 2,000 seller-fulfilled orders in 60 days reaches 1% at 20 defective orders. If negative feedback already accounts for 8, there is room for 11 more claims or chargebacks before the line. That is why the weekly report counts claims per reason, carrier and SKU.
Where does the claim data come from, if no API lists claims?
We checked Amazon's SP-API notification types and its performance report types on November 13, 2026. We found no notification for a new A-to-z claim, and no report that lists claims by order ID. The seller performance report has an Order Defect Rate section, split into Amazon-fulfilled and merchant-fulfilled orders, with counts of claims, chargebacks and negative feedback. That is useful for checking your own count, not for opening cases.
So the trigger is Amazon's own email. Amazon says you get an email when a customer files a claim and that you are responsible for monitoring your claims. A mailbox rule sends those emails to the workflow, which reads the order ID. Because an email can be missed or filtered, a person also checks the Manage A-to-z claims page twice a day. The evidence comes from systems that do have APIs: the order from the Orders API (see our SP-API glossary entry), and labels, scans and proof of delivery from your shipping software or carriers.
Does Buy Shipping change which claims are worth fighting?
It changes the metric, not always the money. Amazon's prevention page says that when you ship on time with Buy Shipping, granted delivery-related claims do not affect your account health or Order Defect Rate, as long as you answer customer messages within 48 hours. You may still have to reimburse the customer. Our carrier rate shopping recipe covers how that protection enters the label decision.
The packet records whether each label came from Buy Shipping and whether the 48-hour reply was met. For a protected delivery claim, the owner can often refund and move on, because the rate is safe. For an unprotected one, the evidence decides. Offers in Seller Fulfilled Prime carry weekly delivery lines too, so a late carrier shows up in both places.
What should stay with a person?
Every action that spends money or speaks to Amazon or the customer. Rules can read the email, gather tracking and refunds, pick the row and count the hours. A person decides each refund and submits each response and appeal in Seller Central. Amazon asks for relevant, compelling information about the transaction and your account of events, and that account has to be true. A model can draft the timeline from the packet. It cannot know what your warehouse saw.
A person also decides when not to appeal. A low-value claim with weak proof may cost more time than it returns. If a late order was delivered and the customer is happy, a person can ask them to reverse the refund: Amazon says it cannot reverse a refund on a seller-fulfilled order without the customer's consent. Shopify disputes follow a different path, run by the card network, in our chargeback evidence recipe. Defective-product cases may belong in a warranty claims workflow first.
Which tool should run the queue?
The simplest one that can read the email and see your shipping data.
| Level | Fits when | What to watch |
|---|---|---|
| Mailbox rule and a case spreadsheet | A few claims a month, one shipping tool | Someone has to paste tracking and watch the 72-hour clock by hand |
| Zapier, Make or n8n | One shipping tool with an API, modest volume | Parse the order ID strictly, keep one case per claim, and log every run; see our Zapier vs Make vs n8n comparison |
| Custom code on your accounts | Several carriers or warehouses, Seller Fulfilled Prime, many claims | Can run on Ecomsellertool Growth OS beside the order and shipping data it needs |
Our guide to automating Amazon operations shows where this queue fits with the rest of the seller-fulfilled work.
Who builds an A-to-z claim queue for Amazon sellers?
Ecomsellertool builds claim queues on your own Seller Central account, shipping software and helpdesk. We have built on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. We map your claim reasons and owners with you first, then build the email trigger, the evidence pulls, the decision table and the deadline clock. Send a project brief, or read how our workflow automation service works.
None of our published case studies is a claim queue on its own, so here is the closest work we have shipped:
- Carrier data in one place. Ecom Global was built for 100M+ products, 20+ marketplaces and 13+ carriers, with carrier types, coverage and routing rules held in one shipping master. Tracking and proof of delivery are the core of most claim packets.
- Alerts on account events that need a response. For AccountDr we built rule-based automation that notifies Amazon sellers about performance metrics, negative seller comments, hijackers and listing faults, by push and email, so a person acts on the specific item.
You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you. If you are not sure claims are your biggest leak, the free 24-hour diagnostic looks across the account first.
Get your claim queue built
Send us how A-to-z claims reach your team today
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
How long do I have to respond to an Amazon A-to-z claim?
Amazon's help pages say that when it asks you for more information during an investigation, you have 72 hours to reply, or it may grant the claim to the customer and debit your account. Before any claim, you have 48 hours to answer a customer's delivery message or return request. If a claim is granted, you have 30 calendar days to appeal.
Does refunding an A-to-z claim remove it from my Order Defect Rate?
No. Amazon's Order Defect Rate page lists claims you refunded after the claim was filed as claims that count. Claims that count also include those granted with you at fault, orders you or Amazon canceled, and claims pending an appeal. Claims denied to the buyer, withdrawn by the buyer, or found not your fault do not count. Refunding before a claim is filed is what protects the rate.
How do I win an A-to-z Guarantee claim for item not received?
There is no way to promise a win, but the evidence Amazon asks for is clear: shipping method, tracking number, proof of delivery, the delivery address, signature confirmation if you bought it, carrier details and your messages with the buyer. Answer the buyer within 48 hours, ship by the ship-by date with valid tracking, and attach signed proof of delivery where you have it.
Can I get A-to-z claims through the Amazon SP-API?
We did not find a way on November 13, 2026. Amazon's SP-API notification list has no claim notification, and the seller performance reports give claim counts inside the Order Defect Rate, not claims by order ID. So the workflow starts from Amazon's claim email and the Manage A-to-z claims page, and uses the report to check its own count each week.
Does Buy Shipping protect me from A-to-z claims?
It protects your metrics, not always your money. Amazon says that when you ship on time with a Buy Shipping label, granted delivery-related claims do not affect your account health or Order Defect Rate, as long as you answer customer messages within 48 hours. You may still have to reimburse the customer.
How do I appeal an A-to-z claim Amazon granted to the buyer?
In Seller Central, open Performance, then A-to-z Guarantee claims, then the Option to Appeal tab, find the claim and choose Appeal decision. Upload proof of delivery or other documents that support your reason. You have 30 calendar days from the grant, and Amazon may ask for more information, which you must answer within 72 hours.
Do A-to-z claims apply to FBA orders?
Amazon describes the A-to-z Guarantee as covering orders fulfilled by the seller, and its Order Defect Rate page says the rate applies only to seller-fulfilled orders. This queue is for merchant-fulfilled and Seller Fulfilled Prime orders. The seller performance report still splits claim counts into Amazon-fulfilled and merchant-fulfilled sections, so check both.
