Amazon A-to-z Guarantee Claims: Reply With AI-Drafted Evidence

Respond before the deadline in Amazon's notice (its help page gives 72 hours to answer a request for information) by gathering the evidence that matches the claim type, letting AI draft a short factual reply from that evidence, and checking every sentence against your records before you submit. Never state anything you cannot prove.

A missed reply is the costliest mistake. Amazon's guidance says that if you do not respond in time the claim is decided for the buyer, your account is debited and your order defect rate is affected. So the routine below is built for speed: a ready folder, a template, a prompt that turns your records into a first draft in two minutes, and a short check that keeps the draft honest.

Follow me on Instagram@sagnikteaches

What an A-to-z claim is, and which orders it covers

The A-to-z Guarantee lets a buyer ask Amazon to step in when an order does not arrive, arrives in a different condition from the listing, or a return goes wrong. Amazon's claims page says it applies to orders you fulfil yourself. Buyers must contact you first: for a delivery problem they message you and must also wait three days past the latest estimated delivery date before filing, and for an item problem they open a return request. Either way you have 48 hours to respond, and Amazon calls 24 hours best practice for return requests. When a claim is filed, you see it in Seller Central under Performance, in the A-to-z Guarantee Claims page, and you respond from the Action Required tab.

Connect on LinkedInSagnik Bhattacharya

The outcomes, as Amazon's claims page lists them: Amazon grants the claim automatically (for example because you did not reply to the buyer within 48 hours, shipped after the expected ship date, delivered after the latest estimated delivery date or had no valid tracking), Amazon investigates and decides on the information each side provides, you refund in full and the claim closes (which still counts against your order defect rate), or the buyer withdraws it, which has no effect on that rate. One exception is worth knowing: when tracking shows a parcel undeliverable, refused or returning to you, Amazon refunds the buyer and debits you without touching the rate. That last route is why a courteous, quick message to the buyer can matter. But never push a buyer to withdraw, and keep every message inside Amazon's messaging rules; the tutorial on buyer-seller messages and AI replies within the rules sets out what is safe.

Subscribe on YouTube@sagnikteaches

The seller in this walk-through

A small seller of electrical cable accessories ships about 220 orders a month itself from a spare room. Last month it had three A-to-z claims: one "never arrived", one "arrived damaged", one "not as described". The same approach covers a plumbing-parts seller or a roofing-supplies seller; the evidence differs only in detail. Amazon measures order defect rate over a 60-day period and requires sellers to keep it under 1%. At about 440 orders in that window, three claims counted against the seller would use 0.68 points of that 1% on their own, so each one matters. The goal is to win the ones that deserve winning, refund the ones that do not, and never lose one by being late.

Build the evidence pack before you need it

Set up a folder structure now, with one subfolder per order, filled automatically or by routine at the time of dispatch. For each order keep:

• The order record: order ID, date, items, price, the promised delivery window.
• Dispatch proof: the date and time you handed the parcel to the carrier, with the carrier's receipt.
• Tracking: the number, carrier name, and a saved copy of the tracking history showing status, dates and delivery confirmation.
• Packing photos: one photograph of the packed item with the label visible, taken before sealing.
• Product details: the listing text as it was on the order date (a screenshot) and the specification you rely on.
• Messages: every buyer-seller message, in order.
• Returns: the return instructions you sent, the return address, any prepaid label, and the tracking of the returned parcel.

The photograph is the cheapest evidence you can create. Five seconds at the packing bench saves an argument about whether you sent the right thing, in decent condition. A seller who files ten photos a day and stores them by order number is in a very different position from one who is reconstructing a week-old order from memory.

What evidence suits which claim

Amazon's guidance lists different documents for different claims. The table maps them to the evidence pack and to what a strong response says.

Include only evidence that supports your account. Padding the response with unrelated documents slows the reviewer and weakens the case. If your own records show that you were wrong, the strongest move is to say so and refund.

Step one: triage in five minutes

Open the claim and read three things before touching AI: the claim reason, the date the claim was filed and the deadline, and the buyer's comment. Then ask the only question that matters: do my records support me? Sort into one of three outcomes.

1. Clear win. Tracking says delivered to the order address on a stated date and time, and nothing suggests otherwise. Respond with the evidence.
2. Clear loss. The parcel never left, or the wrong item was packed, or tracking shows a failed delivery. Refund in full and, if appropriate, reply with a short apology.
3. Murky. Tracking says delivered but to a "safe place" and the buyer says no. Respond with the evidence, offer help (a replacement or refund if the cost is small) and weigh what a loss does to your defect rate.

A cost rule for the murky cases starts from one line on Amazon's order defect rate page: a claim you refund after it was filed still counts, so a refund ends the argument but not the defect. Only a denied claim, a withdrawal or a finding that you were not at fault keeps it off the rate. Each counted claim moves the walk-through seller's rate by about 0.23 percentage points (1 divided by roughly 440 orders in the 60-day window), almost a quarter of the 1% limit. For a $12 order with thin evidence, refunding and moving on can be sensible. For a $90 order with clean tracking, respond with the evidence and give the claim its best chance of being denied.

Step two: draft the reply with AI, from facts only

The prompt gives the model the facts in a fixed shape and forbids it from adding any. Remove personal details first: use [buyer] and [order number]. The draft needs dates and statuses, not names and addresses.

I am a seller responding to an A-to-z Guarantee claim. Write a factual, polite reply of under 150 words to the marketplace's claims team, using ONLY the facts below. Do not add facts, dates or promises that are not listed. If a fact needed for the reply is missing, list it at the end under "Missing" instead of inventing it. Do not criticise the buyer. Do not use legal language.

Claim reason: item not received
Order placed: 3 March. Promised delivery: 7 to 10 March.
Dispatched: 4 March, 2:15 pm, with [carrier], tracking [number].
Tracking history: 4 March collected; 6 March out for delivery; 6 March 11:42 delivered, left in a safe place per carrier note.
Delivery address on order matches the address on the carrier label: yes.
Buyer message on 9 March: "Parcel never came."
My reply to buyer on 9 March, within 24 hours, offered to open a carrier investigation: yes. Buyer did not answer.
Evidence ready to send: tracking history, label photograph, my messages.

Sample output (illustrative):

The order was dispatched on 4 March at 2:15 pm with [carrier], tracking [number], within the promised delivery window. The carrier's tracking shows the parcel out for delivery on 6 March and delivered at 11:42 that day, left in a safe place. The delivery address on the carrier label matches the address on the order.
When the buyer told us on 9 March the parcel had not arrived, we replied the same day and offered to open a carrier investigation. We have not received a reply. We have attached the tracking history, the label photograph and our messages, and we are happy to refund or resend if Amazon prefers.
Missing: none.

Read what you would change. "Within the promised delivery window" is wrong: the parcel was delivered on 6 March, a day before the 7 to 10 March window opened, and the model added the phrase because it sounds reassuring. Change it to "ahead of the promised delivery window". Also check the closing line: "happy to refund or resend" is a commitment, so only keep it if you mean it.

A damaged-item claim, a different reply

Claim reason: item arrived damaged
Item: cable organiser box, 6 units, shipped in a double-wall carton with paper fill: yes (photo attached, taken 12 March before sealing).
Buyer message 15 March: "Two boxes cracked." No photographs supplied.
My reply 15 March: asked for a photograph of the damage and packaging; offered a replacement or refund: yes.
Buyer reply: none.

The model's draft should state the packing, the request for photographs and the open offer, and it should not claim the damage "happened in transit" or "was caused by the carrier", because you do not know that. If the draft says so, delete the sentence. Present what you did and what you offered, and let the reviewer decide.

Step three: the truth check, line by line

Treat the draft as an unchecked statement from a stranger. Before submitting, take each sentence and tick it against a record.

1. Dates and times: match them to the tracking page, not your memory.
2. Quantities and identifiers: tracking numbers, order numbers, amounts, character by character.
3. Actions you took: each must appear in your message history.
4. Adjectives and inferences: "promptly", "clearly", "the carrier damaged it", "the buyer is mistaken" are unverifiable; remove them.
5. Offers and promises: keep only the ones you will honour.

The rule for the whole routine is simple: no false statements, ever. A false statement in a claim response is worse than a lost claim. It can lose a claim you would have won, and a pattern of inaccurate responses puts the account at greater risk than a pattern of honest refunds. If the chatbot invents a detail, your check is the only thing standing in the way of it.

A return-and-refund claim, step by step

The fourth claim type is the one sellers often lose through slow admin rather than a dispute. A buyer returns an item, says no refund arrived, and files. The facts for the prompt (illustrative):

Claim reason: return sent, refund not received
Return authorised: 10 March, prepaid label sent the same day.
Return tracking: collected 12 March; delivered to my return address 17 March, signed by [staff initials].
Condition on arrival: opened, item intact, box damaged (photo taken 17 March).
Refund: issued 19 March, full item price, minus nothing. Refund record attached.
Buyer message on 20 March: "Still no refund."

The draft should simply set out the dates, point out that the refund was issued on 19 March, and attach the refund record. Often the refund really was issued and the buyer has not yet seen it in their account, which can lag the dates on your side. If your own records show the refund was issued after the claim was filed, say that plainly, because it is true and the reviewer can see it. If the record shows no refund, the chatbot has nothing to argue with and the right action is to refund now and close the claim. Watch the clock on returns, too: Amazon's claims page says a claim is granted automatically when an item sent back on a prepaid label is not refunded within 5 days of arriving, so the 19 March refund, two days after the parcel reached the seller, was inside that limit.

A reply template you can keep

Once you have written three or four of these, turn the best into a skeleton, so the AI fills in facts rather than inventing structure:

1. What was ordered, when, and the promised delivery window.
2. What we did and when: dispatch date, carrier, tracking number.
3. What the record shows: tracking events with dates and times.
4. What we did when the buyer reported the problem: message dates and offers.
5. Evidence attached or sent via messages: list.
6. What we are willing to do now: only if we mean it.

Keep each section to one or two sentences. If a section has no facts, write "none" rather than padding it, and let the reviewer see the gap honestly.

A monthly ten-minute review

At the start of each month, open the claims page and list every claim, its type, the outcome and the time you took to respond. Ask three questions: did any claim reach the deadline with no reply from you (that is a process failure to fix), which carrier or product shows up most, and how many claims did you refund that your records would have won. Many sellers discover that a small number of products or routes produce most of their claims. Fixing one packaging weakness or one slow carrier is worth more than any amount of skilful drafting.

Tone: firm, brief, no heat

The reviewer reads many claims a day. A 120-word response that lists dates, tracking status and evidence is easy to decide. A page of grievance is not. Compare these two openings:

• Before: "This buyer is obviously trying to get a free item. We have been selling for years and this is the third scam this month."
• After: "The parcel was delivered on 6 March at 11:42 according to the carrier's tracking, which we have attached."

The first adds an accusation you cannot prove and tells the reviewer nothing. If you let the chatbot soften your drafts, tell it to remove accusations and emotion and keep the facts; the instruction "do not criticise the buyer" in the prompt above does exactly that.

Submitting: where the documents go

Amazon's help page on responding sets out the route: Performance, then A-to-z Guarantee claims, then the Action required tab, where you find the claim, select Respond to Amazon, enter your comments, attach supporting documents and submit. Some seller guidance reports a response box that would not take attachments; if your claim page offers no upload, send the documents through Buyer-Seller Messages and refer to them in the response. Because interfaces change, follow whatever your claim page currently shows, and keep a copy of what you sent and when. Answering the buyer's first message or return request well inside the 48 hours is the cheapest habit in this tutorial, because it can stop the claim being filed at all.

Appeals when the decision goes against you

If a claim is decided against you and you believe it was wrong, Amazon's appeal page gives you 30 calendar days: open the Option to Appeal tab, choose Appeal decision and upload proof of delivery or other supporting documents. A successful appeal may reverse the decision in whole or in part, including the defect-rate effect or the refund, but a claim pending a decision on appeal still counts against the rate meanwhile, and any further information request during the appeal has a 72-hour limit. "New supporting information" is the key phrase: resubmitting the same text rarely helps. Use the chatbot to compare your original response with your records and list anything you did not include, such as a second tracking scan, a photograph or a message you left out. The structure of a good appeal is close to that of an account appeal drafted truthfully with AI.

Counting the effect on order defect rate

Amazon's order defect rate is the share of seller-fulfilled orders in a 60-day period with negative feedback (1- or 2-star seller ratings), an A-to-z claim or a credit card chargeback. Take the walk-through seller: 220 orders a month is about 440 in the window. Suppose the window holds last month's three claims, all counted against it, plus two orders with negative feedback and one chargeback. That is six defective orders in 440, or 1.36%, over the 1% limit. If it wins two of the three claims, or the buyers withdraw them, the count falls to four, 0.91%, just under. If the remaining claim is then reversed on appeal, it falls to three, 0.68%. Each defective order is worth about 0.23 points at that volume, which is why each claim deserves its ten minutes. Figures are illustrative; an order with two problems counts once, and your account health page shows your own numbers. The weekly review of Business Reports is the place to keep an eye on order volume, so you can see whether the rate is moving.

When the claim was right and the draft would have hidden it

Consider a realistic case. A seller's AI draft for a "not as described" claim said the item "matched the listing exactly". The facts file said the listing showed a black cable organiser and the seller had shipped grey units from a new batch because the black ones had sold out. The model had no way to know. It wrote the safest-sounding sentence, and the seller nearly submitted it.

The check caught it, because step three compares each sentence with a record, and the shipping record said grey. The reply that went out said: "We shipped a grey unit on this order because the black stock had sold out. We should have contacted the buyer first. We have refunded in full." The claim closed. The seller then fixed the listing's colour options and changed its process so a colour substitution triggers a message to the buyer first. That is the best outcome a claim can produce, and it is why honest records and an honest reply do more for the account than a clever argument.

Cutting claims at the source

Look at the last twenty claims and tag each one: carrier, packaging, listing accuracy, slow dispatch, slow reply. Paste the tags and counts (not the buyers' details) into a chatbot, and ask which two fixes would remove the most claims. Typical findings: a slow carrier on one route, a fragile product with thin packing, a listing detail that buyers misread. The tutorial on refund claims for a print on demand business uses the same tag-and-count method, and the PayPal dispute evidence pack shows how a similar folder serves a different platform. Keep the record, answer fast, and let the evidence speak.

Questions sellers ask about A-to-z claims

How long do I have to respond to a claim?

Amazon's help page gives you 72 hours to answer its request for information once a claim is being investigated; after that the claim can be granted to the buyer. Before any claim, you have 48 hours to answer the buyer's message or return request. Treat the date and time in your notice as the deadline and reply on the first day.

Does an A-to-z claim hurt my order defect rate?

Amazon's order defect rate page counts claims granted where you were at fault, claims you refunded after they were filed, claims on cancelled orders and claims pending an appeal. Claims that are denied, withdrawn or found not to be your fault do not count, and a claim reversed on appeal is removed. The rate covers seller-fulfilled orders over a 60-day period.

Should I just refund the buyer to close it?

A full refund closes the claim, but Amazon's order defect rate page counts a claim you refunded after it was filed, so refunding ends the argument, not the defect. Refund when the buyer is plainly right, or when the order is small and your evidence weak. Respond with evidence when your records clearly support you and the claim is wrong.

Can I attach files to my response?

Amazon's help page on responding says to enter your comments and attach any supporting documents, and its appeal steps include uploading proof of delivery. Some seller guidance reports a response box that would not take attachments; if yours does not, send the documents through Buyer-Seller Messages and refer to them in the response. Keep a copy of everything you send.

Is it safe to paste the buyer's details into ChatGPT or Claude?

Avoid it. Replace the buyer's name, address and order number with placeholders such as [buyer] and [order number] before pasting, and add the real ones back when you submit. The draft needs the facts of the case, not the buyer's personal details.

Further reads

• Amazon FBA Reimbursement: Spot Lost and Damaged Stock Using AI — Recover money for stock Amazon lost or damaged.
• Amazon Seller Virtual Assistant or AI: Which Tasks Go to Whom — Decide who handles claims, you, an assistant or AI.
• eBay Seller Rating Levels: Audit Defects and Late Shipments With AI — Compare how another marketplace counts defects.
• What to Do When AI Gets Something Wrong With a Customer — Prepare for AI drafts that misstate the facts.
• Amazon Review Analysis With AI: Find What Buyers Want — Spot product problems that drive claims.
• Amazon FBA vs FBM Cost: Model Your Own Products With AI — See where seller-fulfilled risk sits in the cost model.
• Xero for Amazon Sellers vs QuickBooks: Fees, Payouts and AI Features — How Xero and QuickBooks handle Amazon settlements, fee categories and AI categorisation, with plan costs and a test to run before you pick.
• Chargeback Response Template for Online Stores, Drafted With AI — Reason-code mapping, an evidence checklist and a response template you can fill with AI, plus the rule that nothing gets invented.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Amazon Seller Central help pages on A-to-z Guarantee claims, responding to a claim, appealing a claim and order defect rate (checked November 2026), plus Seller Central forum guidance; deadlines and rules change, so confirm them in the claim notice in Seller Central.