SOP: file an FBA inbound shipment discrepancy (Seller Central)
Amazon publikuje komunikaty Seller Central i Ads po angielsku. Brief poniżej zostaje po angielsku, by nie zgubić źródła. Przegląd, formularze i polityki są w Twoim języku. Potwierdź liczby w Seller Central.
Who it hits
3P FBA who send inbound regularly.
What to do this week
Filter Closed. Diff shipped vs received. File Research missing units inside the live window with POD/BOL and invoice.
Packet
- Shipment ID (every child ID in a split). FNSKU. Shipped qty vs received qty.
- POD / BOL, packing list, supplier invoice.
- Case: Research missing units. Do not open it while status is Receiving.
- If the SKU is a hero, treat a short receive as a bid input until units exist.
Vendor Central SHORT is a different console. Do not file a 3P inbound case in 1P. Workstream: FBA shipment discrepancies.
What you are actually filing
A 3P FBA inbound discrepancy is shipped vs received on a shipment that is Closed. Amazon does not auto-file these the way many founders assume. Payout is generally sourcing cost, not retail, which is why waiting “until it is worth it” is how you donate units. Policy Amazon posted in September 2024 commonly puts Research missing units between day 15 and day 60 from delivery. Older “nine month reimbursement” guides are leftover. Confirm the live window in Seller Central the week you file. Do not open the case while status is Receiving.
How to find the gap
Payments / FBA reports: filter inbound Closed. Diff shipped vs received by FNSKU and by child shipment ID in a split. Sellerboard can flag; filing is still Seller Central. Screenshot the discrepancy. If the SKU is a hero, treat a short receive as a bid input until units exist — ranking into OOS is a second leak on top of the missing inventory.
Packet that survives review
Shipment ID (every child ID). FNSKU. Shipped qty vs received qty. POD or BOL, packing list, supplier invoice. Case type: Research missing units. Do not mix Vendor Central SHORT into this packet — different console, different codes. Do not mix damaged/lost warehouse claims into the inbound case unless the help page says they belong together this month.
After Amazon pays or denies
If paid, log sourcing cost recovered. If denied, read the reason; many denials are window or documentation. Restock the hero. Restore ads only when the offer can fulfill. Workstream: FBA shipment discrepancies.
How this desk differs from leftover reimbursement guides
Amazon does not auto-file 3P inbound shipped-vs-received the way founders assume. Payout is generally sourcing cost, not retail. Policy Amazon posted in September 2024 commonly puts Research missing units between day 15 and day 60 from delivery — older “nine month” guides are leftover. Confirm the live window the week you file. Do not open the case while status is Receiving. Split shipments need every child shipment ID. Do not mix Vendor Central SHORT into this packet. Do not mix damaged/lost warehouse claims into the inbound case unless the help page says they belong together this month. A short receive on a hero is also a bid input: ranking into OOS is a second leak on top of the missing inventory. File once with a complete packet. Then restock. Then restore ads.
FAQ
Can Sellerboard file this?
It can flag. Filing is still Seller Central inside the live window.
Can I file on day five?
Usually no. Receiving has to close and the live window (commonly day 15+) has to open. Confirm the help page. Filing early is a wasted case.
Is this the same as lost in warehouse?
No. Inbound shipped-vs-received is one SOP. Inventory that disappeared after check-in is another. Separate cases.
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.