Chargeback and A-to-z Defense

When to use this

• A chargeback notification arrived from Amazon.
• An A-to-z claim is open and the response window is counting down.
• The seller has been auto-losing claims and wants a real process.
• A pattern of claims on a specific SKU or carrier suggests a fix.

The framework. The Claim Type Decision Tree

Step by step

1. Collect inputs. The claim text Amazon sent, the order ID, fulfillment method (FBA or FBM), tracking number, any messaging with the buyer, and the listing details at time of sale.
2. Identify the claim type from the buyer's stated reason.
3. Assemble the evidence per type.
   • INR: carrier delivery scan with timestamp, GPS if available, signature confirmation, address validation, second-attempt notes.
   • SNAD: title, bullets, main image, and dimensions as listed at sale time. Offer return or partial refund if appropriate.
   • Fraud: pattern, IP/device, message thread, order velocity, payment-method mismatch.
4. Write the response narrative. Factual, dated, points to the evidence by exhibit. No emotion, no excuses, no buyer-blame. 3 to 5 short paragraphs.
5. Submit before the deadline. An A-to-z claim gives the seller about 3 calendar days (roughly 72 hours) to respond to Amazon's request for information. confirm the exact countdown on the case, since Amazon has shown some variation here. A card-network chargeback is a separate process on the issuer's representment timeline, often a week or more after notification. Submit well before either deadline. extensions are not granted.
6. Note the ODR impact. An A-to-z lost without response counts against the seller's Order Defect Rate, even after refund. Defending matters for the metric, not just the dollars.
7. Track the pattern. If multiple claims fit one root cause (a carrier issue, a listing mismatch, a buyer behavior), fix that root cause.
8. Run the quality check, then deliver.

Output format

## Claim Defense. [order ID]

Claim type: [INR / SNAD / Fraud]
Deadline: [date and time]

### Evidence packet
1. [exhibit] . source . what it proves
...

### Response narrative
[3 to 5 short paragraphs Amazon will read]

### Pattern check
[any recurring root cause across recent claims]

Worked example

Quality check

• The claim type is identified before any evidence is assembled.
• Evidence matches the burden of proof for that specific type.
• The response is factual and dated. no emotion, no buyer-blame.
• Submitted with time to spare before the deadline.
• Recurring patterns are flagged for a root-cause fix.

Common mistakes

• Auto-refunding. Paying the chargeback plus a fee instead of defending a defensible claim.
• Wrong evidence type. Sending listing screenshots on an INR claim, or carrier tracking on a SNAD claim.
• Emotional response. A pleading or accusatory narrative gets dismissed.
• Missing the deadline. The A-to-z window is about 3 calendar days, no extensions. confirm the exact countdown shown on the case.
• No pattern review. Fighting each claim in isolation while the same root cause keeps producing more.

Built by Jay GPT Pro