You must submit an ASN for every shipment, regardless of freight type, size, or payment terms. A receiving accuracy chargeback for an ASN compliance defect occurs when your ASN has one of the following issues at receiving. [1][2]
2 What triggers it & how to prevent it Final composition for this type
More than one ASN matches directly to the same pallet or box. Each pallet/box must have only one ASN; multiple POs on one pallet must be consolidated into one ASN[1]
2
LP label reused within the same ASN
The content label was provided multiple times within the same ASN. Each content label must be unique and mapped to a single container. Exception: LP labels may repeat if you use EDI, the container holds multiple ASINs or POs, and the ASN is in consolidated format — then one LP label can appear in different POs within the ASN [1]
3
Late ASN
ASN not sent before the shipment arrives at the FC [1]
4
Pending ASN submission
ASN left in draft status, or created but never submitted [1]
5
ASN structure or quantity mismatch
ASN structure doesn't match the physical labeling when automation is used — package LP labels must be at package level, pallet LP labels at tare/pallet level. Or ASN quantities don't match the physical items received [1]
Expiration date at receipt is in the past, or less than 30 days away [1]
8
Expiration date is too close to expiration
Expiration date is between 30 and 90 days away [1]
9
Expiration date is too far in the future
Expiration date is beyond the maximum future horizon — thresholds differ by region, see below [1][2]
10
Pallet or box scannable label does not match ASN
Label information doesn't match the ASN SKU due to typos or missing characters [1]
11
Missing ASN
No ASN received for the shipment, or content label information missing from the ASN [1]
Expiration windows (sub-defects 7–9) are measured from the ASN creation date[1]
Too-far-in-the-future thresholds — 3 or more years (1,095 days) for Grocery, Pantry, Drugstore, Sports, SDP Miscellaneous, Office Products, Lawn and Garden, Outdoors; 5 or more years (1,825 days) for Baby, BISS, Kitchen, Health and Personal Care, Personal Care Appliances, Pet Supplies, Tools & Building Supplies, Home, Home Improvement, Beauty, Luxury Beauty [1]
Direct Import — upload SSCC label information to the CDS portal at least five days before shipment. Responsibility by shipment type: GXD + GPE → GXD generates and uploads; all other combinations → the vendor generates and uploads [1]
Amazon Fresh — use the appointment reference number instead of an inbound shipment delivery number; do not add PO numbers, only PRO or BOL [1]
Amazon treats all product date indicators as expiration dates — sell by, use by, best by, best before, best if used by [1]
Internal note — not shown in productCS Excel 只列了 10 个子缺陷，漏 LP Label Reused Within The Same ASN（校验报告 P3-5）。
✓ How to prevent it
Submit an ASN for every shipment, regardless of freight type, size, or payment terms [1][2]
Submit at least six hours before the shipment arrives — or before the carrier leaves your location for local deliveries [1][2]
Best practice: submit within 30 minutes after the carrier picks up your shipment [1][2]
Submit each ASN individually, not in batches; then check Shipments to confirm transmission — a "Late ASN" status means it was not sent [1][2]
Assign only one ASN per carton or pallet; consolidate multiple POs into one ASN [1]
When updating a submitted ASN, resubmit the entire ASN; for EDI use the "05" qualifier in the BSN segment to mark a replacement [1][2]
Ensure the carrier's PRO and BOL match your ASN; resubmit if the carrier updates the PRO [1][2]
Include item-level expiration dates; keep catalog expiration requirements up to date; never ship expired or nearly expired products [1][2]
If using EDI, review your EDI 856 map against the current specification [1][2]
Monitor EDI certification and transmission status on the Operational Analytics dashboard[1][2]
Designer note (internal)Internal note — not shown in productG6/G7 匹配型 · ASN 侧。中心为 ASN 文档卡，四周挂 11 个子缺陷标记（EU 版 12 个），按性质分三组着色： - 提交时效组（Late / Pending / Missing）—— 配时钟，标 ≥ 6h before arrival / ≤ 30 min after pickup - 结构组（Multiple ASNs / LP reused / Structure mismatch / Label mismatch）—— 配托盘-箱-ASN 三层结构图 - 效期组（NA 4 个 / EU 5 个）—— 配日期轴，标 < 30 days（红，费率不分档）、30–90 days、NA ≥ 3 yr / ≥ 5 yr、EU > 10 yr 费率区按大区切换渲染（NA 三档表 / EU 固定额表）。
Above 95% → 2% PCOG; 70–95% → 4% PCOG; below 70% → 6% PCOG. Exception: Expiration Date Is Less Than 30 Days = 100% PCOG + $2/unit in all three tiers — it does not scale with compliance [1]
For missing ASN information — Vendor Central screenshot or EDI 856 XML/text showing the label barcode information (SSCC or AMZNCC) and submission time[1][2]
For appointment verification — appointment confirmation showing PRO or BOL and PO information [1][2]
For expiration date issues — a screenshot showing the expiration date in your ASN, or documentation proving the product does not expire [1][2]
The "does not expire" documentation is required only for the Missing Expiration Date sub-type [1]
6 Evidence examples
✓ Approved submission
✕ Denied submission
1 Definition≠ Differs from North America
You must submit an ASN for every shipment, regardless of freight type, size, or payment terms. A receiving accuracy chargeback for an ASN compliance defect occurs when your ASN has one of the following issues at receiving. [1][2]
2 What triggers it & how to prevent it Final composition for this type
More than one ASN matches directly to the same pallet or box. Each pallet/box must have only one ASN; multiple POs on one pallet must be consolidated into one ASN[1]
2
LP label reused within the same ASN
The content label was provided multiple times within the same ASN. Each content label must be unique and mapped to a single container. Exception: LP labels may repeat if you use EDI, the container holds multiple ASINs or POs, and the ASN is in consolidated format — then one LP label can appear in different POs within the ASN [1]
3
Late ASN
ASN not sent before the shipment arrives at the FC [1]
4
Pending ASN submission
ASN left in draft status, or created but never submitted [1]
5
ASN structure or quantity mismatch
ASN structure doesn't match the physical labeling when automation is used — package LP labels must be at package level, pallet LP labels at tare/pallet level. Or ASN quantities don't match the physical items received [1]
Expiration date at receipt is in the past, or less than 30 days away [1]
8
Expiration date is too close to expiration
Expiration date is between 30 and 90 days away [1]
9
Expiration date is too far in the future
Expiration date is beyond the maximum future horizon — thresholds differ by region, see below [1][2]
10
Pallet or box scannable label does not match ASN
Label information doesn't match the ASN SKU due to typos or missing characters [1]
11
Missing ASN
No ASN received for the shipment, or content label information missing from the ASN [1]
Expiry windows are measured beyond the receiving date; the too-far-in-the-future threshold is more than 10 years; and "Expiry date is in the past" is tracked as a separate, twelfth sub-defect [2]
Internal note — not shown in productCS Excel 只列了 10 个子缺陷，漏 LP Label Reused Within The Same ASN（校验报告 P3-5）。
✓ How to prevent it
Submit an ASN for every shipment, regardless of freight type, size, or payment terms [1][2]
Submit at least six hours before the shipment arrives — or before the carrier leaves your location for local deliveries [1][2]
Best practice: submit within 30 minutes after the carrier picks up your shipment [1][2]
Submit each ASN individually, not in batches; then check Shipments to confirm transmission — a "Late ASN" status means it was not sent [1][2]
Assign only one ASN per carton or pallet; consolidate multiple POs into one ASN [1]
When updating a submitted ASN, resubmit the entire ASN; for EDI use the "05" qualifier in the BSN segment to mark a replacement [1][2]
Ensure the carrier's PRO and BOL match your ASN; resubmit if the carrier updates the PRO [1][2]
Include item-level expiration dates; keep catalog expiration requirements up to date; never ship expired or nearly expired products [1][2]
If using EDI, review your EDI 856 map against the current specification [1][2]
Monitor EDI certification and transmission status on the Operational Analytics dashboard[1][2]
Designer note (internal)Internal note — not shown in productG6/G7 匹配型 · ASN 侧。中心为 ASN 文档卡，四周挂 11 个子缺陷标记（EU 版 12 个），按性质分三组着色： - 提交时效组（Late / Pending / Missing）—— 配时钟，标 ≥ 6h before arrival / ≤ 30 min after pickup - 结构组（Multiple ASNs / LP reused / Structure mismatch / Label mismatch）—— 配托盘-箱-ASN 三层结构图 - 效期组（NA 4 个 / EU 5 个）—— 配日期轴，标 < 30 days（红，费率不分档）、30–90 days、NA ≥ 3 yr / ≥ 5 yr、EU > 10 yr 费率区按大区切换渲染（NA 三档表 / EU 固定额表）。
UK — most sub-defects £0.25; missing expiry date and too-far-in-the-future £0.06; too-close-to-expiry £1.50; expiry < 30 days and expiry in the past = £1.50 per unit + 85% PCOGS[2]. DE and IT — the same table in euros: €0.30 / €0.07 / €1.70 / €1.70 per unit + 85% PCOGS[2]. FR — €0.30 for the ASN sub-defects only; its rate table publishes no expiry rows at all [2]
For missing ASN information — Vendor Central screenshot or EDI 856 XML/text showing the label barcode information (SSCC or AMZNCC) and submission time[1][2]
For appointment verification — appointment confirmation showing PRO or BOL and PO information [1][2]
For expiration date issues — a screenshot showing the expiration date in your ASN, or documentation proving the product does not expire [1][2]
Evidence of timely ASN submission — Vendor Central screenshots or the EDI DESADV transmission showing the ASN details, the BOL/PRO reference and the PO line-item unit count [2]
It is required for all expiry-date-related sub-types [2]
