Source of this page: Appointment accuracy — Amazon Vendor Central: US ↗ · MX ↗ · BR ↗
1 Definition
You will receive a chargeback for Appointment Accuracy if your carrier fails to meet the confirmed appointment commitment. These defects cause inaccurate promises for Amazon's customers and waste reserved dock space, labor, and equipment.
Three root causes : Late Appointment Cancellation · Late Appointment Reschedule · Arrival Outside Grace Period
2 What triggers it & how to prevent it Final composition for this type
✕ What triggers it
Root cause
Trigger
Late Appointment Cancellation
The carrier cancels after the cancellation deadline — 24 hours before the scheduled arrival time
Late Appointment Reschedule
The appointment is moved to a later time after the rescheduling deadline — also 24 hours before scheduled arrival. Every such change counts as a separate defect
Arrival Outside Grace Period
The carrier's actual arrival falls outside the arrival grace period — before the earliest allowed or after the latest allowed arrival time
Grace period (by fulfillment center and appointment load type) :
Appointment type
Grace period
DROP
Equal to the drop window before the scheduled arrival time
LIVE at 1DC
± 30 minutes
LIVE at non-1DC
± 60 minutes
Charge granularity : charged at Appointment ID granularity — multiple defects on the same appointment produce individual chargebacks.
✓ How to prevent it
Ensure your carrier arrives within the grace period — neither before the earliest nor after the latest allowed arrival time
Have carriers confirm appointments only when committed to delivering at the scheduled arrival time or within the arrival grace period
Do not cancel after the 24-hour cancellation deadline
Do not reschedule to a later time after the 24-hour rescheduling deadline
Know your FC's appointment load type — DROP / LIVE, and whether it is a 1DC site — since that sets the grace period
Designer note (internal)Internal note — not shown in productA4 状态机型（本族唯一）：预约生命周期横轴 Appointment confirmed → T-24h（黄色双截止线，标 Cancellation & Reschedule deadline）→ Scheduled arrival。 三条分支从状态节点分出： - 🔴 Cancel after T-24h → $250 TL / $90 LTL - 🔴 Reschedule later after T-24h → 同额（并标 每次改期单独计费） - 🔴 Arrive outside grace band → 同额 宽限带分两类画（AVC 明写 DROP 的 latest arrival = scheduled arrival，窗口非对称，不可与 LIVE 同画法）： - LIVE @1DC / LIVE @non-1DC：以 Scheduled arrival 为中心的对称灰带，分别标 ±30 min / ±60 min - DROP：单边灰带，左端 = Scheduled arrival − drop window，右端截止于 Scheduled arrival；右缘标红 late tolerance = 0 三条带上下并列、共用同一条 Scheduled arrival 竖线，让读者一眼看出 DROP 没有晚到容忍。两侧带外区域标 → outside grace period（早到侧同样计费）。 豁免徽标：Amazon-initiated → exempt、Prepaid only。
3 Chargeback fee
Penalty
TL$250/LTL$90
flat fee per Appointment ID
Compliance required
100%
no automatic waiver
$250 flat per defect (TL) ｜ $90 flat per defect (LTL)
On the Mexican and Brazilian marketplaces Amazon publishes the United States and Canadian pages unchanged, so these amounts appear in US dollars, as printed, and no peso or real amount is published. Read them as printed and check your Vendor Central billing for the amount you are actually charged .
All three root causes carry the same rate, and the rate card marks each of them Requires 100% compliance .
Internal note — not shown in product2026-09-09 新市场实测（账本筛 node=GNCKUVTZ39CX2SJS）—— MX 是 US 逐字副本、BR 是 CA 逐字副本（equivalence.csv#GNCKUVTZ39CX2SJS/MX:US、/BR:CA，class=identical），两站 Amount 行与 rate card 三行都照搬 $250 / $90（F-MX-GNCKUVTZ39CX2SJS-15-1/-2、F-BR-GNCKUVTZ39CX2SJS-15-1/-2），未本地化为 MXN / BRL，故只加一条 NA: 说明，STAT 不分叉、不得换算。库内 MX / BR 本单元均 0 笔（US 2,168 / CA 104，db/db-applicability.csv#A4）—— 本类型 2026-07 才上线，0 笔不等于不收费。 ⏳ 待 owner 裁定：本单元 🟦 NA only 的两条依据之一是"EU 页面为未本地化复制品"，但 2026-09-09 实测推翻了这一条 —— GNCKUVTZ39CX2SJS 的 UK 版与 US 版做域名归一化后，唯一的实质差异就是把 $250 / $90 全部改写成 £250 / £90（Amount 行 + rate card 三行共 4 处；其余只有空白与一处表头大小写），DE / IT / FR 同样改写为 €250 / €90（F-UK-GNCKUVTZ39CX2SJS-15-1/-2、F-DE-…、F-IT-…、F-FR-…，localization_flag 均为 localized）。把金额完整改写成本币是维护动作，不是复制残留 —— 对照 A2 的子页只把 LTL 换成 £55 / €55、TL 仍留 $500，那才是半本地化的残留形态。本单元另一条依据（库内 EU 零数据）不受影响，故 EU 适用性未改、BE / TR 未加行，只在族级总表标 ⏳。（证据 temp/chargeback-analysis/market-expansion/open-questions.md#B17）
4 Official exemptions
Late Cancellation: no chargeback when Amazon deletes the appointment
Late Reschedule: no chargeback when Amazon reschedules the appointment
All three: the chargeback applies only to prepaid shipments — it does not currently apply to collect or direct import shipments
5 Documents required for dispute
Every Appointment Accuracy dispute is built the same way: one shared set of attachments, plus the evidence for the specific defect you were charged for .
Always required
Attach these to every Appointment Accuracy dispute, whichever defect was charged
The Inbound Shipment Appointment ID and your vendor ID
A Carrier Central appointment page screenshot showing the fulfillment center, appointment load type, scheduled arrival time, earliest and latest allowed arrival times, the edit history, and which party made each change
+Then add the evidence for your defect — pick the column below that matches the defect on your chargeback, and attach whichever of its arguments fits your case
Late Appointment Cancellation
Evidence that no cancellation occurred and the carrier arrived — Carrier Central screenshot of the recorded actual arrival time
Evidence the cancellation happened before the deadline — timestamp relative to scheduled arrival
Evidence the cancellation was initiated by Amazon — cancellation request history showing the initiating party
Late Appointment Reschedule
Evidence the arrival time was not moved later (e.g. moved earlier) — original and updated times
Evidence the reschedule was before the deadline
Evidence the reschedule was Amazon-initiated
Arrival Outside Grace Period
Evidence the actual arrival was within the grace period — Carrier Central or gate check-in record relative to earliest/latest allowed times
Evidence the grace period applied was wrong and you arrived within the correct one (e.g. wrong fulfillment center shown)
◻ Evidence examples — not displayed: no reference images available yetInternal note — not shown in product内部待办 —— 本类型自 2026-07 起才产生数据，CS 尚未沉淀 Approved/Denied 示例。建议积累若干真实申诉后补图。
Contact supportOur team will help you prepare and submit the dispute.