Amazon's big move on preventive shortage management: Receive Variance Dashboard (RVD)

The standard shortage dispute process is, by design, a fight you start months after the incident. Invoice due, Smart Match, file, wait — you're building a case against a delivery that happened last quarter, on evidence that survived the archive. By the time the dispute opens, the useful context for settling it cleanly is long gone.

Amazon has changed that. And I think it changes more than most vendors realise.

#Amazon opens the window early — 10 days after delivery

The Amazon Receive Variance Dashboard (RVD) flags a suspected shortage 10 days after delivery — while the receive is still being processed, while the stock is still being reconciled. Amazon names the PO and ASIN, shows an initial amount, and gives you 30 days to submit incremental proof. Not a dispute case. Evidence it can use right now, while the process is live.

This is preventive dispute filing — Amazon-invited, during active reconciliation. Not a practice we endorse, where recovery agencies file disputes on Day 0 and pre-empt Smart Match auto-corrections, inflating success. RVD is the opposite: Amazon asks, you respond, the proof feeds reconciliation directly.

Amazon ran webinars after launch because most suppliers still didn't know the tool existed. That gap is the opportunity.

#Why it matters: timing, not amount

Standard path: delivery → invoice due 60–90 days later → 35-day Smart Match wait → dispute filed → 8–16 weeks to resolution. Five to six months from delivery to cash.

RVD path: Day 10 notification → 30 days to respond → resolved before invoice due → paid on normal terms.

The honest counterargument: Smart Match corrects most of the initial shortage anyway, so why build a process around a number that halves itself regardless? Because the final amount is similar either way. What's different is when it arrives. For vendors managing high shortage volumes, the difference between paid on normal terms and paid 5 months late compounds every quarter.

One calibration before your first notification: the initial RVD figure is typically double the post-Smart-Match number. Amazon's opening position, not your real exposure. Let the 30-day window drive urgency — not the number.

#What the Amazon Receive Variance Dashboard asks you to prove

RVD maps to five categories: incorrect PO, ASN, BOL, EDI interchange, or received quantity. The first four cover information gaps — a process broke down, a transmission didn't go through, a record needs correcting. Submit them where they apply. They matter.

Disputing received quantity is where it gets different. You're not filling a gap in the information chain. You're saying Amazon's FC received this shipment wrong — and here is the physical proof. WMS records, pallet photographs, loading video, signed POD. Amazon's own threshold rule applies: clean POD plus a solid inbound defect score across the prior six weeks and they pay back the variance even when their own internal checks don't resolve it.

#The pipeline is the real challenge

Every RVD dispute runs at PO and ASIN level — every line with its own 30-day window, tracked independently. A vendor with 50 active POs can face hundreds of ASIN-level flags in a week, each needing its own proof type, its own evidence, its own submission. New flags arrive every week. Miss a window in Q4 because your team is buried and that line drops back to the standard queue — gone, unrecoverable.

Relentlessly granular, continuous, unforgiving of gaps. Not work that belongs on a human's plate in 2026.

#PACMAN is built for this

PACMAN already talks to all your systems — WMS, carrier, EDI, Vendor Central — and knows exactly what's happening at every PO and ASIN level. Every RVD flag monitored. Proof type selected per line. Evidence sourced and filed within the window. Continuously.

Because we file through RVD — early, before Smart Match has finished running — our commission reflects that. We're not waiting for Smart Match to settle and charging full rate on the result. We file early, we take the risk early, and our rate reflects it. That's what early filing should look like.

After years of a purely reactive model, Amazon is finally moving toward prevention. That matters to us deeply — it's what we've built for. RVD is the first real signal that the industry is heading in the right direction.

This is the path to zero-error delivery. The information gaps that cost vendors millions every year — wrong ASNs, missed transmissions, receive errors — are exactly what RVD is designed to surface and close, in real time, while the delivery is still live in Amazon's systems.

Amazon built the window. PACMAN makes sure you never miss it.