ⓘ This chargeback was previously published as “ASN accuracy”. Amazon reorganised it under “Receiving accuracy” in October 2025.
1 Definition
Late ASN — ASN is not sent before the shipment's arrival at the fulfillment center. [1]
You must submit an ASN for every shipment, regardless of freight type, size, or payment terms. The chargeback applies when your ASN has this issue at receiving. [1]
2 What triggers it & how to prevent it Final composition for this type
the ASN is transmitted after the shipment arrives at the fulfillment center [1]
For Amazon Fresh shipments, use the appointment reference number instead of an inbound shipment delivery number; do not add PO numbers — only PRO or BOL [1]
✓ How to prevent it
Make sure all information matches your actual shipment and includes every detail the Vendor manual requires on the shipping label [1]
Submit the ASN at least six hours before the shipment arrives at the fulfillment center — unless it is a local delivery, which must be submitted before the carrier leaves your location[1]
Best practice — submit within 30 minutes after the carrier picks up your shipment [1]
Submit each notification individually rather than in batches to prevent submission delays [1]
After submitting, check Shipments to confirm transmission — if you see "Late ASN", your notification has not been sent [1]
When using a third-party service, give them accurate shipment information promptly so they can submit without delay [1]
For EDI submissions, monitor certification and ASN transmission status on the Operational Analytics dashboard; contact your EDI team immediately if certification is expiring or a transmission failed, then re-submit promptly [1]
If you modify an ASN already submitted, resubmit the entire updated ASN; over EDI, mark the BSN segment with the "05" qualifier to denote a replacement [1]
Make sure the PRO and BOL in the ASN are the same as the ones the carrier uses; if the carrier changes the PRO, resubmit the ASN with the most up-to-date PRO [1]
Designer note (internal)
D-type timeline, authored once with sibling data-region groups (NA / EU) in every slot that differs — each tab shows only its own region, and the NA/EU contrast lives in the internal note above, not in the artwork.
Carrier pickup → +30 min (green ideal submission band) → … → FC arrival − 6h (yellow latest line) → FC arrival. 🟢 ASN lands inside the green band or before the yellow line; 🔴 ASN lands after FC arrival → Late ASN. Exception card: Local delivery — submit before the carrier leaves your location. Status card: Shipments → "Late ASN" = never sent. Rate card: tiered PCOG on the 12-week compliance rate.
3 Chargeback fee
Receiving accuracy chargebacks are calculated from your 12-week defect rate, and the percentage applies to the total cost of all defective products in the shipment. [1]
Internal note — not shown in product2026-09-07 全 EU 六市场实测 G201741480(ASN accuracy 页)与 GRWSA8S934RXN6UX(Receiving accuracy 页)的结论: PL / SE —— G201741480 可访问(6029 字节,PL/SE 正文一致),明文写有 ASN On-time Compliance 规则(30 分钟 / 6 小时口径),但通篇无费率表、通篇用 defect 而非 chargeback(SE 页 "chargeback" 出现 0 次);GRWSA8S934RXN6UX 在 PL/SE 均为空页(199 字节)。故 PL/SE 判定为「有规则、无公布费率」,与 D1 同款处置。 UK —— 表中 £0.25 已确认:avc-snapshots/current/UK/GRWSA8S934RXN6UX.md(2026-09-02 快照,9789 chars)完整列出 15 行费率,Label 0.12 / ASN 0.25 / expiry 0.06、1.50。(2026-09-07 那次抓取的 202 字节空页为单次抓取失败,不作凭据)。同时 UK 的 G201741480 明文列有 ASN on-time compliance = €0.30,与 DE / IT 一致。(UK cookie 于 2026-09-08 已过期,本次未能复测) FR —— 两页给出两个不同数值:G201741480 写 €0.33(另有 Missing BOL €0.12,及 trailing-4-week ≥95% 整周豁免),GRWSA8S934RXN6UX 写 Late ASN 0.30 EUR。 DE / IT —— 两页一致,均 €0.30(DE 与 IT 正文除域名外基本相同,仅子缺陷排序略有出入)。 ⚠️ 待 owner 裁定:本单元库内 raw 是 asn_otnc(On-Time Non-Compliance),字面对应的是 ASN accuracy 页的 "ASN on-time compliance" 行,而不是 Receiving accuracy 页的 "Late ASN" 行 —— 后者定义为「ASN 在货到之后才收到」,比前者的 30 分钟 / 6 小时窗口宽松,两者并非同一缺陷。若改按 ASN accuracy 页取数,UK 应为 €0.30(非 £0.25)、FR 应为 €0.33(非 €0.30)。本次只补 PL / SE,UK / DE / IT / FR 维持原值不动。 📝 2026-09-07 按 AVC 原文重写正文:NA 与 EU 的 GRWSA8S934RXN6UX不是同一篇文档的翻译件,是两篇独立正文(US 14683 / CA 15153 / DE·IT 9807 / FR 9522 字节,连章节标题都不同)。实测差异 6 处,已逐条按 NA / EU 分区落进正文: ① 定义:NA "ASN is not sent before the shipment's arrival at the fulfillment center" 以到仓为界;EU "An ASN was received after the receipt of shipment" 以签收为界。 ② 判定时点表述:NA "your ASN has one of the following issues at receiving";EU "the ASN is invalid at the time of receiving"。 ③ 提交时限措辞:NA 以 shipment arrives at the FC 为基准、例外写 local delivery;EU 以 carrier appointment 为基准、例外写 if the fulfillment center is close to your location。 ④ Shipments 面板状态串:NA 显示 "Late ASN";EU 显示 "pending submission" —— EU 页通篇没有 "Late ASN" 这个状态串,沿用 NA 文案会让欧洲 vendor 在面板上找不到对应状态。 ⑤ Dispute 证据:NA 要 EDI 856(X12)传输副本、强调 showing submission time;EU 要 EDI DESADV(EDIFACT),且要求含 ASN details、BOL/PRO reference、PO line item unit count 三项。注意 EU 页在"规范下载"处仍指向 Retail X12 856 zip,属 Amazon 自身表述不一致,此处照录、不做统一。 ⑥ Dispute 时限:NA 页明写 within 30 days of receiving the chargeback notification;EU 页未给时限,只写所需材料"取决于 chargeback 上的 notes"。
◻ Official exemptions — not displayed: Amazon publishes no exemption for this type
5 Documents required for dispute
ASN submission evidence with timestamp — a Vendor Central screenshot, or the XML / text copy of the EDI 856 transmission, showing submission time[1]
Appointment confirmation showing the PRO or BOL number and your purchase order information [1]
Submit your dispute within 30 days of receiving the chargeback notification. [1]
6 Evidence examples
✓ Approved submission
ⓘ Example shared across the ASN accuracy defects
✕ Denied submission
ⓘ Example shared across the ASN accuracy defects
1 Definition≠ Differs from North America
Late ASN — An ASN was received after the receipt of shipment. [2]
ASNs are required for every shipment, regardless of freight type, size, or payment terms. The chargeback applies when the ASN is invalid at the time of receiving. [2]
2 What triggers it & how to prevent it Final composition for this type
the ASN is received after the receipt of the shipment[2]
✓ How to prevent it
Your ASN must be accurate and reflect what you actually shipped to us, include all required information outlined in the vendor manual, and be submitted before your shipment arrives at a fulfillment center[2]
Submit the ASN within 30 minutes of the carrier's departure from your premises, or at least six hours before the carrier appointment at the fulfillment center; if the fulfillment center is close to your location, send the ASN before the carrier departs with your shipment [2]
Do not submit ASNs in batches, as this delays the submission process — submit each ASN in real time[2]
After submitting, confirm it was sent by going to Shipments — if the ASN is listed as "pending submission", it has not been submitted [2]
When using a third-party service, give them accurate shipment information promptly so they can submit without delay [1]
For EDI submissions, monitor certification and ASN transmission status on the Operational Analytics dashboard; contact your EDI team immediately if certification is expiring or a transmission failed, then re-submit promptly [1]
If you modify an ASN already submitted, resubmit the entire updated ASN; over EDI, mark the BSN segment with the "05" qualifier to denote a replacement [1]
Make sure the PRO and BOL in the ASN are the same as the ones the carrier uses; if the carrier changes the PRO, resubmit the ASN with the most up-to-date PRO [1]
Designer note (internal)
D-type timeline, authored once with sibling data-region groups (NA / EU) in every slot that differs — each tab shows only its own region, and the NA/EU contrast lives in the internal note above, not in the artwork.
Carrier pickup → +30 min (green ideal submission band) → … → Carrier appointment − 6h (yellow latest line) → Shipment received. 🟢 ASN lands inside the green band or before the yellow line; 🔴 ASN arrives after Shipment received → Late ASN. Exception card: FC nearby — send before the carrier departs. Status card: Shipments → "pending submission" = never submitted. Rate card: flat per unit, no tiers.
3 Chargeback fee≠ Differs from North America
The chargeback is a flat amount per unit — the EU table publishes no compliance-rate tiers. [2]
❌ No fee published — the Polish page states the on-time rule but publishes no rate [3]PL
SE
❌ No fee published — the Swedish page states the on-time rule but publishes no rate [3]SE
Internal note — not shown in product2026-09-07 全 EU 六市场实测 G201741480(ASN accuracy 页)与 GRWSA8S934RXN6UX(Receiving accuracy 页)的结论: PL / SE —— G201741480 可访问(6029 字节,PL/SE 正文一致),明文写有 ASN On-time Compliance 规则(30 分钟 / 6 小时口径),但通篇无费率表、通篇用 defect 而非 chargeback(SE 页 "chargeback" 出现 0 次);GRWSA8S934RXN6UX 在 PL/SE 均为空页(199 字节)。故 PL/SE 判定为「有规则、无公布费率」,与 D1 同款处置。 UK —— 表中 £0.25 已确认:avc-snapshots/current/UK/GRWSA8S934RXN6UX.md(2026-09-02 快照,9789 chars)完整列出 15 行费率,Label 0.12 / ASN 0.25 / expiry 0.06、1.50。(2026-09-07 那次抓取的 202 字节空页为单次抓取失败,不作凭据)。同时 UK 的 G201741480 明文列有 ASN on-time compliance = €0.30,与 DE / IT 一致。(UK cookie 于 2026-09-08 已过期,本次未能复测) FR —— 两页给出两个不同数值:G201741480 写 €0.33(另有 Missing BOL €0.12,及 trailing-4-week ≥95% 整周豁免),GRWSA8S934RXN6UX 写 Late ASN 0.30 EUR。 DE / IT —— 两页一致,均 €0.30(DE 与 IT 正文除域名外基本相同,仅子缺陷排序略有出入)。 ⚠️ 待 owner 裁定:本单元库内 raw 是 asn_otnc(On-Time Non-Compliance),字面对应的是 ASN accuracy 页的 "ASN on-time compliance" 行,而不是 Receiving accuracy 页的 "Late ASN" 行 —— 后者定义为「ASN 在货到之后才收到」,比前者的 30 分钟 / 6 小时窗口宽松,两者并非同一缺陷。若改按 ASN accuracy 页取数,UK 应为 €0.30(非 £0.25)、FR 应为 €0.33(非 €0.30)。本次只补 PL / SE,UK / DE / IT / FR 维持原值不动。 📝 2026-09-07 按 AVC 原文重写正文:NA 与 EU 的 GRWSA8S934RXN6UX不是同一篇文档的翻译件,是两篇独立正文(US 14683 / CA 15153 / DE·IT 9807 / FR 9522 字节,连章节标题都不同)。实测差异 6 处,已逐条按 NA / EU 分区落进正文: ① 定义:NA "ASN is not sent before the shipment's arrival at the fulfillment center" 以到仓为界;EU "An ASN was received after the receipt of shipment" 以签收为界。 ② 判定时点表述:NA "your ASN has one of the following issues at receiving";EU "the ASN is invalid at the time of receiving"。 ③ 提交时限措辞:NA 以 shipment arrives at the FC 为基准、例外写 local delivery;EU 以 carrier appointment 为基准、例外写 if the fulfillment center is close to your location。 ④ Shipments 面板状态串:NA 显示 "Late ASN";EU 显示 "pending submission" —— EU 页通篇没有 "Late ASN" 这个状态串,沿用 NA 文案会让欧洲 vendor 在面板上找不到对应状态。 ⑤ Dispute 证据:NA 要 EDI 856(X12)传输副本、强调 showing submission time;EU 要 EDI DESADV(EDIFACT),且要求含 ASN details、BOL/PRO reference、PO line item unit count 三项。注意 EU 页在"规范下载"处仍指向 Retail X12 856 zip,属 Amazon 自身表述不一致,此处照录、不做统一。 ⑥ Dispute 时限:NA 页明写 within 30 days of receiving the chargeback notification;EU 页未给时限,只写所需材料"取决于 chargeback 上的 notes"。
◻ Official exemptions — not displayed: Amazon publishes no exemption for this type
5 Documents required for dispute≠ Differs from North America
Evidence of timely ASN submission — Vendor Central screenshots or the EDI DESADV transmission, showing ASN details, the BOL / PRO reference, and the PO line-item unit count[2]
A screenshot or email of the appointment confirmation containing the progressive number (PRO) or bill of lading (BOL) and the purchase order information [2]
Which supporting documents are required depends on the notes attached to the chargeback. [2]
6 Evidence examples
✓ Approved submission
ⓘ Example shared across the ASN accuracy defects
✕ Denied submission
ⓘ Example shared across the ASN accuracy defects
7 References
[1] Receiving accuracy chargebacks — Amazon Vendor Central: US ↗ · CA ↗
[1][2] Receiving accuracy chargebacks — Amazon Vendor Central: UK ↗ · DE ↗ · IT ↗ · FR ↗
[3] About advance shipment notification accuracy — Amazon Vendor Central: UK ↗ · DE ↗ · IT ↗ · FR ↗ · PL ↗ · SE ↗
Effect page auto-generated from 03-per-type-content/ · content and page never drift apart · PIN-3468