Services · Verdedigen

Vendor Central Shortages

Amazon deducts first. The vendor who reconciles PO, ASN, and POD gets the money back.

Best fit: Vendor Central brands seeing SHORT / -SC on remittances and no one owning the dispute clock

SHORT Deductions named, not buried in AP

Packet ASN + POD + packing list, or we do not file

Clock Wait for auto-match, then dispute before the portal dies

Vendor Central shipment discrepancies are Purchase Quantity Variance — Amazon’s name for “we received less than you invoiced.” It shows as deduction code SHORT and often as an invoice suffix -SC. If Amazon later finds the receipt, it can flip to -SCR. Until then, they keep the money.

Do not rush a dispute on day one if Amazon’s internal match is still running (vendors often see ~35 days of auto-reconciliation). Do not wait past the dispute deadline showing in Vendor Central either. Published windows vary by workflow and FC — 30 days from claim date is common for SHORT; US PQV/PPV has also been described with a two-year outer limit. The date on the invoice in Vendor Central is the one that matters.

The packet is ASN vs BOL/POD vs packing list vs carton counts vs invoice qty. Operational chargebacks (ASN, on-time PO, prep) are a related but separate code. I will not mix a shortage dispute with a co-op deduction and call it one case.

Who this is for

1P vendors who invoice Amazon and want PO shortages, ASN mismatches, and chargebacks in a weekly desk — not a year-end AP cleanup.

Who it is not for

A chargeback-software login with no operator. Also not co-op / advertising accrual disputes as a finance department. I reconcile shipments and file the packet.

How the work actually runs

Read remittance

SHORT, -SC, chargeback codes. Separate shortage from prep/on-time/co-op.

Wait or file

If Amazon is still matching receipts, wait. If the portal deadline is close, file with what we have.

Packet

PO, ASN, invoice qty, BOL/POD, carton counts, delivery date. Quantity Amazon says is missing, documented.

Re-dispute

Partial deny or deny: use Vendor Central’s re-dispute when it is open. Email-only cases are not the first move anymore.

What is in the workstream

Shortage / PQV / SHORT watch on remittances
Invoice -SC vs -SCR (self-reversed) notes
PO vs ASN vs received qty reconciliation
Dispute packet: ASN, BOL/POD, packing list, carton counts
Wait-vs-file against Amazon’s auto-match window
ASN, on-time, and prep chargebacks still in window
Re-dispute path when Vendor Central allows a second pass
Windows confirmed in Vendor Central — not a blog deadline

Week one

I read Payments → Invoices / Review-Dispute Shortages and the open chargebacks. Auto-reconciliation in flight gets a wait note. Anything past Amazon’s match period with a POD still in hand gets a dispute list.

Every week after

New SHORT / PQV lines, invoices still in Amazon’s auto-match window, chargebacks (ASN, OTPO, prep) still disputable, and a packet list for anything that will not self-reverse.

On this workstream’s desk

Named seats, not a logo wall. Each page says the job, the rail, and what still has to happen in Seller Central or the Ads Console.

Kimi

Kimi K2, Moonshot

A second long-context pass on large Amazon exports and competing drafts — used when one model should not be the only reader of a 40,000-row file.

Claude

Anthropic Claude

Long-context read of search-term exports, change logs, and playbooks — drafts the founder note. Does not bid, does not log into Seller Central.

Full operator stack →

FAQ

Is this the same as FBA reimbursements?

No. Seller Central FBA is shipped-vs-received on your inbound. Vendor Central is Amazon as the retailer shorting your PO invoice. Different console, different evidence, different clock.

How long do I have to dispute?

Use the deadline on the claim in Vendor Central. SHORT is often ~30 days from claim date; Amazon has also run a multi-year outer cap on older PQV. I will not quote a blog as law.

Should I dispute on day one?

Usually no. Amazon’s match process can self-reverse a SHORT to -SCR. Filing too early wastes the one-shot (or re-dispute) on an invoice that would have cleared.

Do you run all of Vendor Central?

This workstream is shortages, PO receive discrepancies, and related operational chargebacks. 1P retail POs, pricing, and co-op are not a hidden full-service 1P agency.

This workstream on the free review

You do not need to hire it to find out if it belongs on the account. Send the public store link. I tell you whether this lever is leaking, whether I am the person to run it, and what week one would be.

The leaks I can see from the public listing

Title, bullets, A+, reviews, brand defense, and obvious ad-real-estate problems. Storefront URL only — no Seller Central login until we agree to work.

Whether this desk is a fit

If I cannot show the leaks, I decline. You are not added to a roster. A “no” is a complete answer, not a follow-up sequence.

What week one would be

Harvest, defense, listing pass, or “not yet.” Named in writing — not a 40-slide deck and a 12-month PDF.

Request a free review

Capacity is limited because I work the accounts myself. The review is how we decide if this workstream belongs on yours.