Amazon Compliance Chargeback Codes, Mapped

Amazon's compliance chargebacks are penalty deductions for supply-chain process defects, and they come in roughly 40+ types organized into six categories that map to the fulfillment lifecycle: Purchase Order, ASN, Preparation, Packaging (SIPP), Transportation, and Receive Process. Every code on your remittance belongs to one of these families, and each family has its own trigger logic, fee basis, and winning dispute evidence.

This is the taxonomy reference. If you want the business case for working these deductions, start with Amazon deductions explained; this article is for the finance or ops person staring at a remittance line and asking what the code actually means.

How are Amazon chargeback codes organized?

Six categories, mapped to where in the fulfillment lifecycle the defect occurred. One structural fact worth knowing before the table: ASN errors are the most common root cause across categories, because most codes ultimately compare what you shipped against what your Advance Ship Notice said you shipped.

Treat every fee above as indicative, not gospel: Amazon revised several of these in 2025 and 2026, most figures circulating publicly come from recovery-vendor content, and the authoritative schedule is login-gated. The source of record is your own Vendor Central, under Reports and Operational Performance.

What changed in 2025 and 2026?

Two restructures matter for reading current remittances:

In Full Delivery (enforced July 21, 2025) consolidated the quantity defects into one chargeback with three subtypes: Not Filled (invoicing fewer units than confirmed: 5% of COGS on the shortfall, cut from 10%, and waived entirely when your trailing 12-week fill rate stays above 95%), Down Confirmed (reducing confirmed quantities later than 5 business days after ship-window start: 3%, no waiver), and Overage (invoicing more than ordered: 100% on the excess, no waiver). Not on Time remains a separate chargeback.

Receive Accuracy (effective January 19, 2026) consolidated the former label and ASN receive-side codes, surfaces root causes in Vendor Central, and processes deductions in roughly 7 to 14 days, down from 30 to 60. Faster processing means less time between defect and deduction, which makes upstream evidence capture more important, not less.

How does the dispute process work now?

The mechanics are unforgiving but symmetrical: you have roughly 30 days from the deduction notification to file, a refusal opens a second 30-day window, and the same chargeback can be disputed twice. Two rounds, then the money is gone.

Since September 2025, those rounds have had a machine in front of them. Amazon has been rolling out DisputeGPT, an AI review layer inside Vendor Central, starting with In Full Delivery chargebacks in the US and expanding across chargeback types into 2026, per supplier-side documentation of the rollout. Instead of writing a dispute justification, you attach your proof documents; DisputeGPT scans them against what Amazon's systems already record for the PO and shipment, and returns a Dispute Analysis within about a minute recommending either proceeding or attaching more or different documentation. It does not approve or deny anything on its own, but it decides what a human reviewer sees first.

The operational consequence: the first reader of your dispute now checks alignment, not persuasion. A well-written narrative can no longer carry a package with a missing document, because there is no narrative; the attachments are the dispute. First-submission completeness decides the outcome, and the analysis feedback is effectively a free pre-check: if the tool says gather more documentation, fix the package before spending one of your two rounds on it.

What evidence reverses each code?

The burden of proof sits with the supplier; Amazon's system is presumed correct until your documents say otherwise. Disputes need attachments, the window is short (about 30 days from the charge), and audit-quality proof is the difference: submissions with stamped, verified proof-of-delivery and matching documents are reported to push approval rates above 70 percent, while thin or mismatched attachments get denied.

The evidence that wins, by family:

1. PO on-time codes: the Carrier Central appointment screenshot or POD showing delivery requested or made inside the window.
2. In Full Delivery codes: EDI confirmation logs plus proof of delivery showing units and timing.
3. ASN and carton content codes: the actual EDI 856 file, SSCC-18 scan logs, and timestamped carton photos proving physical matched the notice.
4. Prep, packaging, and labeling codes: photos of open and closed cartons at ship time showing compliant prep and scannable labels.
5. Transportation codes: carrier booking confirmations, gate logs, and the signed BOL.

The operational rule underneath all five: evidence must be captured at ship time as a by-product of the outbound process. A carton photo or routing screenshot cannot be recreated a month later when the deduction posts, and disputes are lost to missing evidence more often than to weak merit. Vendor Central helps more than most teams realize: each chargeback shows a Recommended Dispute Proof card telling you what Amazon wants to see.

Which codes deserve prevention versus recovery effort?

A practical split: SIPP and packaging codes are one-time fixes (certify the SKU, the charges stop), so prevention dominates. Transportation flat fees are large per incident, so even modest dispute rates pay for the effort. ASN-family codes reward process investment because the fee tier itself drops as your trailing compliance rate rises: getting from below 70% to above 95% compliance cuts the fee from 6% of COGS to 2% before you dispute anything. And In Full Delivery is new enough that adjudication is still settling, which makes documentation discipline unusually valuable right now.

If your remittances carry codes you can't map, or mapped codes nobody has disputed inside their windows, that's the gap the Margin Recovery Audit quantifies: which categories are hitting you, what's recoverable, and which prevention fix stops the biggest line. It starts with a free scan, and the process side is what our chargeback prevention service implements.