Chargebacks Analysis Report ▸ ASN Unit Count Mismatch guide drawer　｜　← B3 · All types · D2 →
← All types
ASN Unit Count Mismatch
Manual dispute
✕
ASN accuracy · unit D1
North America
Europe
Source of this page: About advance shipment notification accuracy — Amazon Vendor Central: US ↗ · CA ↗

1 Definition

An advance shipment notification accuracy chargeback is triggered when either of the following occurs: required information in your advance shipment notification was missing or inaccurate, or Amazon did not receive an advance shipment notification before your shipment physically arrived at a fulfilment centre.

Unit count mismatch sub-type

  • The units, quantity, product identifier quantity, and item type quantity in the ASN must match the purchase order. For example, if Amazon's purchase order is for 2 cases and you send an ASN with 16 each, you'll be subject to this chargeback. An incorrect hierarchical loop in EDI 856 will also make the ASN non-compliant.
Internal note — not shown in product2026-09-07 分区彻底化：按「NA tab 只显 NA、EU tab 只显 EU」，四字段枚举（units / quantity / product identifier quantity / item type quantity）、2 cases → 16 each 例子、UOM mismatch 与 EDI 856 hierarchical loop 均改为 NA 专属 —— 这四项只出自 US 页，UK 页无任何对应措辞；且 EU 走 EDIFACT DESADV 而非 X12 856，"hierarchical loop" 在 EU 根本不是一个概念。EU 侧仅保留 UK 明文的单一定义：ASN 数量 ≠ PO confirmed quantity，按 PO-ASIN 判定。影响：EU tab 的 What triggers it 只剩 1 条 —— 这是 UK 页本身就这么写，不是漏写；若要在 EU 侧补 UOM mismatch，必须标 ⓘ Not published by Amazon。
Internal note — not shown in product2026-09-07 补充：EU 口径取自 UK G201741480（2026-08-27 抓取）—— 正文段落与费率表 "ASN unit count mismatch" 行，两处均为 Amazon 明文。两个市场的例子指向不同失败模式：US 为计量单位口径错（cases → each），UK 为同单位下数量虚报（10 → 16）；合起来才是 D1 的完整画像。UK 另明确了两个 US 页未说的口径：比对基准为 confirmed quantity（非原始订购量），判定粒度为 PO-ASIN。

2 What triggers it & how to prevent it Final composition for this type

POASNASN transmissionFC receivingQuantities do not match
ASN Unit Count Mismatch — the ASN quantity must match the purchase order Amazon action Vendor action Purchase order Amazon (PO) 2 cases ASN / EDI 856 Vendor (EDI 856) Quantity fields — must match the purchase order Units Quantity Product identifier qty Item type qty EDI 856 transmission Vendor Receiving count at the fulfillment center Amazon (receipt) ✗ Quantities do not match PO: 2 cases  vs  ASN: 16 each Unit of measure mismatch Incorrect hierarchical loop in EDI 856 Even if totals agree Chargeback rate — scaled by the trailing four-week ASN accuracy compliance rate below 70% → 5% of product cost 70% – 95% → 3% above 95% → 1% A percentage of the combined cost of every ASIN in the shipment
✕ What triggers it
  • ASN units / quantity / product identifier quantity / item type quantity do not match the PO
  • Unit of measure mismatch — e.g. PO in cases, ASN in eaches
  • Incorrect hierarchical loop in the EDI 856 transmission
✓ How to prevent it
  • Be accurate and reflect what you actually shipped to us
  • Include all required information outlined in the Vendor Manual
  • Be submitted before your shipment arrives at a fulfillment center
  • Submit the ASN within 30 minutes of the carrier's departure from your premises, or at least six hours prior to the carrier appointment at the fulfillment center. If the fulfillment center is in close proximity to your location, send it before the carrier departs with your shipment.
  • Do not submit ASNs in batches, as this can cause a delay in the submission process. Instead, submit each ASN in real time.
  • If you use a third-party service to submit your ASNs, ensure that they have accurate information for each shipment in a timely manner so they can submit without delay
  • When you submit your ASN, ensure that it was sent successfully by going to Shipments. If it is listed as "pending submission," it hasn't been submitted.
  • If you send ASNs via EDI, regularly monitor your EDI certification and ASN transmission status on the Operational Analytics dashboard; if your certification is expiring soon or a transmission has failed, contact your EDI technical team immediately and re-submit once the issue is resolved
  • If you need to modify an ASN that's already been submitted, resubmit the entire updated ASN; via EDI, update the BSN segment with the "05" qualifier denoting a replacement
  • If you use EDI, review the current EDI 856 specification to ensure that your map aligns with our requirements
Designer note (internal)

D data-flow diagram, one shell shared by both region tabs: PO → ASN → ASN transmission → FC receiving → red ✕ Quantities do not match.

Everything the two marketplaces word differently is authored as sibling data-region="NA" / data-region="EU" groups in the same slot, so each tab shows only its own marketplace's wording and the cross-region comparison stays in the internal note.

Values below are deliberately not in backticks: the generator harvests backticked spans from this section into the visible chip row, so a region-specific value written in backticks would leak that region's wording into the other tab's chips. Keep backticks for the region-neutral flow steps above only.
SlotNA group (US page)
PO card value2 cases
ASN card titleASN / EDI 856 · Vendor (EDI 856)
ASN card bodyquantity field group — four chips: units / quantity / product identifier qty / item type qty
Transmission cardEDI 856
🔴 Example bubblePO: 2 cases vs ASN: 16 each → Unit of measure mismatch
Second branchIncorrect hierarchical loop in EDI 856 · Even if totals agree
Bottom bartrailing 4-week compliance scale, three tiers >95% → 1% / 70–95% → 3% / <70% → 5%

The second-branch box is aligned to the EDI column — same x and width as the transmission card, never stretched across two slots.

Shared by both tabs: the diagram title, the Amazon / Vendor legend, the outer shells of the PO / transmission / receiving-count cards, the arrows, and the red ✕ outcome card.

3 Chargeback fee

MarketRate
USTiered by the trailing 4-week ASN accuracy compliance rate: above 95% → 1% of the cost of the product · 70%–95% → 3% · below 70% → 5% [1]US
CASame tiers as US: 1% / 3% / 5% of the cost of the product, on the trailing 4-week rate [1]CA

"The cost of the product" refers to the cost of all the ASINs within a shipment — a shipment containing 1 ASIN is charged the relevant percentage of that ASIN's cost; a shipment containing five ASINs is charged on the combined cost of all five ASINs

Internal note — not shown in product2026-09-07 全欧抓齐（G201741480 on DE/IT/FR/PL/SE，见 temp/chargeback-analysis/vc-docs-*/）。DE/IT 页与 UK 页逐字相同（同为 8101 chars），Use case "1. ASN accuracy"（ASN on-time compliance / ASN unit count mismatch / Missing BOL）统一 €0.30/unit —— 所以旧文案里"UK 页面以欧元报价"那句解释性备注已删，它把一个欧元区通用费率误写成了 UK 的怪癖。FR 是另一版页面（5908 chars）：只有 ASN on-time compliance €0.33 与 Missing BOL €0.12 两行，无 unit count mismatch，且有 UK/DE/IT 都没有的 trailing-4-week ≥95% 整周豁免。PL/SE 是第三版（5794 chars）：通篇 "defect" 不用 "chargeback"，无费率表。
另注 —— 新的 Receiving accuracy 页（GRWSA8S934RXN6UX）自己也有一套 ASN compliance 费率（UK £0.25、DE/IT/FR €0.30），但该页不含 unit count mismatch，其 "ASN structure mismatch" 指 SOPI/SOTI/SOPTI 报文层级与实收货物不符，与数量无关，不可用作 D1 的替代来源。因此 UK 站同时存在 €0.30（ASN accuracy 页，D1 用这个）与 £0.25（Receiving accuracy 页，D2 用这个）两个数，二者各有归属、并不冲突。
◻ Official exemptions — not displayed: Amazon publishes no exemption for this type

5 Documents required for dispute

  • Screenshot of the ASN in Vendor Central, or the XML (or text copy) of the EDI 856 transmission, showing the ASN was submitted before the shipment was received
  • Screenshot or email showing the PRO or BOL number and purchase order information ⓘ Not published by Amazon
Internal note — not shown in product2026-08-28 复核：AVC G201741480（US，2026-08-25 抓取）现已包含 "Dispute this chargeback" 小节，第 1 条据此改标 （旧备注"该页未列出 dispute 材料清单"作废）。PRO/BOL 截图或邮件那条仍非该页明文条目，保留 advice 标记，来源为 CS Excel。2026-09-07 更新：UK dispute 小节要求的 EDI DESADV 副本（含 BOL/PRO reference 与 PO 行项目 unit count） 已从"旁证"提升为 EU 专属正式条目 —— NA 侧要 EDI 856 副本，EU 侧要 DESADV 副本，两者是不同的报文标准，不可互换。通用 dispute 流程见 G201047200。

6 Evidence examples

✓ Approved submission
✓ Approved submission
ⓘ Example shared across the ASN accuracy defects
✕ Denied submission
✕ Denied submission
ⓘ Example shared across the ASN accuracy defects
Effect page auto-generated from 03-per-type-content/ · content and page never drift apart · PIN-3468