Güncellemeler SOP Vendor
SOP: Vendor Central SHORT / PQV dispute packet
Amazon, Seller Central ve Ads duyurularını İngilizce yayımlar. Kaynak metin kaybolmasın diye aşağıdaki brief İngilizce kalır. İnceleme, formlar ve politikalar sizin dilinizde. Canlı rakamları Seller Central’da doğrulayın.
Who it hits
1P vendors with PQV / SHORT on the remittance.
What to do this week
Reconcile PO, ASN, packing list, POD. Do not mix operational chargebacks into the shortage packet.
Packet
- PO qty, ASN qty, invoice qty, FC received qty.
- BOL / POD, carton counts, delivery date, seal if you have it.
- Dispute missing quantity in Payments → Invoices / Review-Dispute Shortages.
- ASN / OTPO / prep chargebacks are separate codes. Separate packet.
Workstream: Vendor Central shortages.
What SHORT / PQV is
On Vendor Central, Amazon deducts when FC received quantity is below the invoice. Remittance code SHORT, invoice suffix -SC, sometimes self-reverses to -SCR when receipts catch up. Amazon often auto-matches for several weeks. Filing on day one can waste a dispute. Filing after the portal deadline on the claim is an auto-deny. Use the date on the claim, not a blog’s generic “30 days.” ASN, OTPO, and prep chargebacks are different codes. Different packet.
How to reconcile before you click Dispute
PO qty, ASN qty, invoice qty, FC received qty. BOL / POD, carton counts, delivery date, seal if you have it. Payments → Invoices / Review-Dispute Shortages. Wait for auto-match when the claim is still inside the auto window and receipts are still landing. When you dispute, attach the operational packet only — do not staple an unrelated chargeback “while you are in there.”
Ads and 1P
A SHORT on a hero PO is a supply problem. If you run ads on the same ASIN (or the 3P offer next to it), treat missing receipts like an inbound miss: do not buy rank into a hole. This SOP does not replace a 3P FBA discrepancy filing. Workstream: Vendor Central shortages.
How operator blogs get Vendor Central wrong
Most 3P “Amazon shortage” posts mix Seller Central shipped-vs-received with Vendor Central SHORT / PQV. They are different consoles, different remittance codes, and different clocks. 1P operator notes that are useful do three things: they name SHORT / -SC / -SCR, they tell you to wait for auto-match when receipts are still landing, and they tell you the deadline is on the claim — not a generic “30 days” from a 2022 PDF. Chargebacks (ASN, OTPO, prep, damage, co-op) get their own packet. Stapling everything into one Dispute is how you lose the shortage and still owe the chargeback.
A worked week (not a legal memo)
- Monday: export remittance. Tag SHORT / -SC. Note the portal date on each claim.
- If receipts are still posting and you are inside the auto-match window, wait. Log the PO so ads do not scale into a hole.
- When the window is closing or receipts have stopped, dispute with PO / ASN / invoice / FC received plus BOL or POD.
- Watch for -SCR. If Amazon already reversed, do not double-count recovered dollars in the founder log.
- Only then restore ranking on the 1P (or adjacent 3P) offer if the ASIN can actually fulfill.
What not to do
- Dispute every SHORT on day one “to be safe.”
- Mix co-op / damage / shortage into one narrative.
- Ignore -SCR reversals and double-count recovered dollars.
FAQ
Should 3P sellers use this SOP?
No. 3P inbound is Seller Central shipped-vs-received. This page is Vendor Central SHORT / PQV.
Where is the deadline?
On the claim in Vendor Central. Copy that date into the tracker. Do not memorize a generic window from an old PDF.
What is -SCR?
A self-reversal when receipts catch up. Log it so you do not dispute a shortage Amazon already reversed, and so you do not double-count recovered dollars.
Can I staple ASN and shortage into one dispute?
No. Different codes, different packets. Mixing them is how both get delayed.
Operator SOP / guide. Confirm live policy in Seller Central before you file or bid.
Stuck on this change?
I will walk the public listing, say whether this change is leaking spend, and what week one would be.