🟨 Copy changed — AVC re-verification 2026-10-22 — text on a yellow background (body copy and diagram labels, on either region tab) is what changed. Temporary review aid; it disappears when HIGHLIGHT_COPY_CHANGES is switched off in gen_type_pages.py.
1 Definition
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 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
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
3
Late ASN
ASN not sent before the shipment arrives at the FC
4
Pending ASN submission
ASN left in draft status, or created but never submitted
5
ASN structure or quantity mismatch
ASN structure doesn't match the physical labeling when automation is used — package LP labels at package level, pallet LP labels at tare/pallet level. Or ASN quantities don't match the physical items received
6
Missing expiration date
Missing expiration date for items that expire
7
Expiration date is less than 30 days
Expiration date at receipt is in the past, or less than 30 days away
8
Expiration date is too close to expiration
Expiration date is between 30 and 90 days away
9
Expiration date is too far in the future
Expiration date is beyond the maximum future horizon — thresholds differ by category, see below
10
Pallet or box scannable label does not match ASN
Label information doesn't match the ASN SKU due to typos or missing characters
11
Missing ASN
No ASN received for the shipment, or content label information missing from the ASN
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 Century Distribution Systems (CDS) portal at least three business days on or before the actual cargo delivery date. 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）。 2026-10-22 AVC 改版（EU GRWSA8S934RXN6UX 整页重写，六站同构，费率金额不变）：EU 子缺陷 #3 Late ASN 新增硬时限 "at least 30 minutes before your physical shipment is being delivered"；#5 结构口径由 SOPI / SOTI / SOPTI 改为 SPI / SPCI / SCI / Blended SPI-SPCI；新增"每票货一个 ASN、超过一整车则每车一个 ASN"；EDI 规范由 X12 856 改为 EDIFACT DESADV（含 API Shipment Confirmation）；替换 ASN 改用 BGM 功能码 4。2b 原先 [1] 共用的"至少提前 six hours / 提货后 30 min 内""BSN 05""EDI 856 map"三行对 EU 已不成立，拆为 NA / EU 两行。子缺陷 #1、#9 措辞细化但口径未变，未改。 ⚠️ EU 两个 Amazon 源现在互相矛盾（待 owner 知悉）：本页（Receiving accuracy）只要求 "at the latest 30 minutes before delivery"；而未改版的 ASN accuracy 页 G201741480（D2 的 EU 源）仍写 "within 30 minutes of departure from vendor premises OR at least six hours before the carrier appointment time"。两者各管各的 chargeback 类型，本单元按本页写，D2 按 G201741480 写；后者更严，按后者执行即两者都满足。
✓ How to prevent it
Submit an ASN for every shipment, regardless of freight type, size, or payment terms [1]
Submit at least six hours before the shipment arrives — or before the carrier leaves your location for local deliveries [1]
Best practice: submit within 30 minutes after the carrier picks up your shipment [1]
Submit each ASN individually, not in batches; then check Shipments to confirm transmission — a "Late ASN" status means it was not sent [1]
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]
Ensure the carrier's PRO and BOL match your ASN; resubmit if the carrier updates the PRO [1]
Include item-level expiration dates; keep catalog expiration requirements up to date; never ship expired or nearly expired products [1]
If using EDI, review your EDI 856 map against the current specification [1]
Monitor EDI certification and transmission status on the Operational Analytics dashboard[1]
Designer note (internal)Internal note — not shown in productG6/G7 匹配型 · ASN 侧。中心为 ASN 文档卡，四周挂 11 个子缺陷标记（EU 版 12 个），按性质分三组着色： - 提交时效组（Late / Pending / Missing）—— 配时钟，NA 标 ≥ 6h before arrival / ≤ 30 min after pickup；EU 标 ≥ 30 min before delivery（2026-10-22 改版，<g data-region> 分区） - 结构组（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 固定额表）。
Same tiers as the United States, as printed — Amazon reproduces the US and Canadian pages unchanged here [1]MX
BR
Same tiers as the United States, as printed — Amazon reproduces the US and Canadian pages unchanged here [1]BR
ⓘ One exception sits outside the tiers.Expiration Date Is Less Than 30 Days is charged at 100% PCOG + $2/unit in every tier — it does not scale with your compliance rate [1].
Internal note — not shown in product校验报告 P4-4 悬案已解决 —— CS 的 "85% PCOGS" 出处即 EU（UK）页，EU 是 85% PCOGS + GBP 1.50/unit，NA 是 100% PCOG + $2/unit。Internal note — not shown in product2026-09-09 六新市场实测（GRWSA8S934RXN6UX）—— BE 与 IT 逐字相同、TR 与 UK 逐字相同（TR 按 TRY 计费，金额印英镑，故标 as printed）、MX / BR 与 US / CA 逐字相同；NL / PL / SE 为 404。库内 receiving accuracy → asn_defect：NL 27,120 · BE 18,440 笔，末次 2026-08-27/28（db/db-applicability.csv#G7）。
◻ Official exemptions — not displayed: Amazon publishes no exemption for this type
For missing ASN information — Vendor Central screenshot or EDI 856 XML/text showing the label barcode information (SSCC or AMZNCC) and submission time[1]
For appointment verification — appointment confirmation showing PRO or BOL and PO information [1]
For expiration date issues — a screenshot showing the expiration date in your ASN, or documentation proving the product does not expire [1]
The "does not expire" documentation is required only for the Missing Expiration Date sub-type [1]
6 Evidence examples
✓ Approved submission
✕ Denied submission
Contact supportOur team will help you prepare and submit the dispute.
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 What triggers it & how to prevent it Final composition for this type
More than one ASN submitted for the same license plate (LP) label on a pallet or box
2
Missing ASN
No ASN received at the time the shipment was receipted
3
Late ASN
The ASN arrived after the shipment was receipted — ASNs must be transmitted at least 30 minutes before the shipment is delivered
4
Pending ASN submission
A Vendor Central ASN was created but never submitted — left in draft or Excel_draft state
5
ASN structure mismatch
The pack hierarchy in the ASN does not match how the shipment was physically packed and labelled — use SPI (pallet → item), SPCI (pallet → carton → item), SCI (floor-loaded carton → item) or a blended SPI-SPCI structure
6
LP label reused within the same ASN
The same LP label appears twice in one ASN — it must not be repeated for both a pallet and a box within the same ASN
7
Missing expiry date
The expiry date is missing in the ASN for an item that expires
8
Expiry date is less than 30 days
At receipt the expiry date is in the past, or less than 30 days beyond the receiving date
9
Expiry date is too close to the expiry
At receipt the expiry date is between 30 and 90 days beyond the receiving date
10
Expiry date is too far in the future
At receipt the expiry date is more than 10 years beyond the receiving date
11
Expiry date is in the past
The expiry date given in the ASN is earlier than the receiving date
12
Pallet or box scannable label does not match the ASN
The label scanned at receiving is not mapped to any ASN in the system
Expiry windows are measured from the receiving date, not from the ASN creation date [1]
Internal note — not shown in productCS Excel 只列了 10 个子缺陷，漏 LP Label Reused Within The Same ASN（校验报告 P3-5）。 2026-10-22 AVC 改版（EU GRWSA8S934RXN6UX 整页重写，六站同构，费率金额不变）：EU 子缺陷 #3 Late ASN 新增硬时限 "at least 30 minutes before your physical shipment is being delivered"；#5 结构口径由 SOPI / SOTI / SOPTI 改为 SPI / SPCI / SCI / Blended SPI-SPCI；新增"每票货一个 ASN、超过一整车则每车一个 ASN"；EDI 规范由 X12 856 改为 EDIFACT DESADV（含 API Shipment Confirmation）；替换 ASN 改用 BGM 功能码 4。2b 原先 [1][1] 共用的"至少提前 six hours / 提货后 30 min 内""BSN 05""EDI 856 map"三行对 EU 已不成立，拆为 NA / EU 两行。子缺陷 #1、#9 措辞细化但口径未变，未改。 ⚠️ EU 两个 Amazon 源现在互相矛盾（待 owner 知悉）：本页（Receiving accuracy）只要求 "at the latest 30 minutes before delivery"；而未改版的 ASN accuracy 页 G201741480（D2 的 EU 源）仍写 "within 30 minutes of departure from vendor premises OR at least six hours before the carrier appointment time"。两者各管各的 chargeback 类型，本单元按本页写，D2 按 G201741480 写；后者更严，按后者执行即两者都满足。
✓ How to prevent it
Submit an ASN for every shipment, regardless of freight type, size, or payment terms [1]
Make sure the ASN is transmitted at the latest 30 minutes before the shipment is delivered to the fulfilment centre — an ASN received after that is recorded as a Late ASN[1]
Submit each ASN individually, not in batches; then check Shipments to confirm transmission — a "Late ASN" status means it was not sent [1]
Submit one ASN per shipment, whether it is a single box or a full truckload; if a delivery needs more than one full truck, submit a separate ASN for each truck [1]
When updating a submitted ASN, resubmit the entire updated DESADV with the same ASN ID (BGM+351) and supplier ID (NAD+SU) and the BGM message function code "4" (change); for API ASNs, resubmit the whole shipment confirmation with shipmentConfirmationType = Replace and the same shipmentIdentifier [1]
Ensure the carrier's PRO and BOL match your ASN; resubmit if the carrier updates the PRO [1]
Include item-level expiration dates; keep catalog expiration requirements up to date; never ship expired or nearly expired products [1]
If using EDI, review your map against the current EDIFACT DESADV specification; if using the API, check it against the Submit Shipment Confirmation API documentation [1]
Monitor EDI certification and transmission status on the Operational Analytics dashboard[1]
Designer note (internal)Internal note — not shown in productG6/G7 匹配型 · ASN 侧。中心为 ASN 文档卡，四周挂 11 个子缺陷标记（EU 版 12 个），按性质分三组着色： - 提交时效组（Late / Pending / Missing）—— 配时钟，NA 标 ≥ 6h before arrival / ≤ 30 min after pickup；EU 标 ≥ 30 min before delivery（2026-10-22 改版，<g data-region> 分区） - 结构组（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 固定额表）。
❌ No fee published — this chargeback type has no published page on the Dutch marketplace. Amazon publishes no rate here, but this chargeback is raised against Dutch accounts — check your Vendor Central billing for the amount actually charged.
£0.25, as printed [1]TRⓘOn the Turkish marketplace Amazon publishes the United Kingdom page unchanged, so the amounts appear in pounds sterling and no lira amount is published. Read them as printed and check your Vendor Central billing [1]TR.
❌ No fee published — this chargeback type has no published page on the Polish marketplace. Amazon publishes no rate here, but this chargeback is raised against Polish accounts — check your Vendor Central billing for the amount actually charged.
SE
❌ No fee published — this chargeback type has no published page on the Swedish marketplace. Amazon publishes no rate here, but this chargeback is raised against Swedish accounts — check your Vendor Central billing for the amount actually charged.
ⓘ One exception sits outside the per-unit rates.Expiry < 30 days and Expiry in the past add 85% PCOGS on top of the per-unit amount, whatever your compliance rate [1].
Internal note — not shown in product校验报告 P4-4 悬案已解决 —— CS 的 "85% PCOGS" 出处即 EU（UK）页，EU 是 85% PCOGS + GBP 1.50/unit，NA 是 100% PCOG + $2/unit。Internal note — not shown in product2026-09-09 六新市场实测（GRWSA8S934RXN6UX）—— BE 与 IT 逐字相同、TR 与 UK 逐字相同（TR 按 TRY 计费，金额印英镑，故标 as printed）、MX / BR 与 US / CA 逐字相同；NL / PL / SE 为 404。库内 receiving accuracy → asn_defect：NL 27,120 · BE 18,440 笔，末次 2026-08-27/28（db/db-applicability.csv#G7）。
◻ Official exemptions — not displayed: Amazon publishes no exemption for this type
5 Documents required for dispute≠ Differs from North America
Submit within 30 days :
For missing ASN information — Vendor Central screenshot or EDI 856 XML/text showing the label barcode information (SSCC or AMZNCC) and submission time[1]
For appointment verification — appointment confirmation showing PRO or BOL and PO information [1]
For expiration date issues — a screenshot showing the expiration date in your ASN, or documentation proving the product does not expire [1]
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 [1]
The "does not expire" documentation is required for all expiry-date-related sub-types [1]
6 Evidence examples
✓ Approved submission
✕ Denied submission
Contact supportOur team will help you prepare and submit the dispute.
