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.
Services · Savunma
Shipment Discrepancies
Amazon does not chase the missing units. The seller who reconciles closed shipments gets paid.
Best fit: FBA catalogs with inbound every month and nobody comparing shipped to received
15–60d
Inbound shortages filed while Closed — not after the window
Packet
POD, packing list, invoice — not a one-line case
Desk
Same weekly log as IPI. Missing units are a bid input
Seller Central shipment discrepancies are not “refund clawbacks.” They are operational: Amazon received fewer units than you shipped, lost or damaged them in the FC, or a removal/return never came back. Auto-reimbursement covers some warehouse losses. Inbound shortages usually do not file themselves.
The inbound clock tightened. Published Seller Central guidance (from the Sept 2024 policy) puts missing-units-from-a-shipment-to-Amazon at 15–60 days from delivery, and only once the shipment is Closed — not while it still says Receiving. Confirm the live window in Seller Central before you wait. Older “nine month” articles are leftover policy.
Evidence is the job. Shipment ID, FNSKU, shipped vs received, carrier POD/BOL, supplier invoice. Reimbursement is generally sourcing cost, not retail. I will not invent a payout. I will not miss a Closed shipment because ads were more interesting that week.
Who this is for
3P FBA sellers who send inbound regularly and want shipped-vs-received, FC loss/damage, and removal gaps in the same weekly desk as IPI — not a once-a-year “reimbursement tool” login.
Who it is not for
A software farm that auto-files every adjustment. I reconcile, document, and file. I do not scrape Seller Central through a grey API.
How the work actually runs
01
Close first
Only Closed shipments. Receiving and Delivered are not claimable yet.
02
Diff SKUs
Contents tab: shipped vs received. Multi-destination splits get every child shipment ID, not just the parent plan.
03
Packet
Shipment ID, FNSKU, qty, tracking, box count, POD/BOL, supplier invoice. One SKU per case when Amazon requires it.
04
Watch payout
Reimbursements report inside 30 days. Wrong amount or silence gets a follow-up on the original case ID.
What is in the workstream
- Closed inbound: shipped vs received by SKU
- Research-missing-units cases inside the live window
- FC lost / damaged adjustment watch
- Removal-in-transit and customer-return-not-received flags
- Evidence packet: POD/BOL, packing list, invoice
- Reimbursements report vs what still needs a case
- Ads pause if heroes are short against inbound we already paid to send
- Windows confirmed in Seller Central — not a blog rate card
Week one
I pull closed inbound in the live window, the Reimbursements report, and Inventory Adjustments. Anything already auto-credited is marked. Anything still short and still eligible gets a claim list with the evidence gap named.
Every week after
Closed inbound: shipped vs received by SKU. Inventory adjustments for lost/damaged. Removal and customer-return gaps still inside the window. Cases that need a BOL/POD get a packet, not a hope.
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.
Sellerboard
SellerBoardTrue P&L after COGS, Amazon fees, ads, and reimbursements — the number that sets the bid ceiling, not the Ads Console ACOS tile.
Claude
Anthropic ClaudeLong-context read of search-term exports, change logs, and playbooks — drafts the founder note. Does not bid, does not log into Seller Central.
Kimi
Kimi K2, MoonshotA 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.
FAQ
Is this automatic now?
Some warehouse lost/damaged lines auto-credit. Inbound shipped-vs-received usually does not. If you do not open Closed shipments, you donate the units.
What is the filing window?
Inbound missing units: typically no earlier than 15 days and no later than 60 days from delivery, shipment Closed. FC lost/damaged is often 60 days from the adjustment date. Removal and customer-return windows differ. Confirm in Seller Central — Amazon has shortened these before.
Do you pay out at retail?
No. Current reimbursement math is generally documented sourcing cost. I will not sell a retail-price recovery story.
Is this Vendor Central too?
No. 3P FBA inbound lives here. 1P PO shortages, invoice -SC, and chargebacks are the Vendor Central shortages workstream. Different console, different clock.
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.
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.
Capacity is limited because I work the accounts myself. The review is how we decide if this workstream belongs on yours.
Request a free reviewRelated workstreams
Inventory & IPI
Restock, stranded, and IPI pacing so ads do not buy rank into a stockout — especially through Q4 fee windows.
Vendor Central Shortages
1P PO vs ASN vs received: shortage claims (PQV / SHORT), invoice disputes, and operational chargebacks — filed with a packet, not left on the remittance.
Catalog & Variations
Parentage, stranded listings, suppressions, and backend terms — the catalog bugs that make ads look broken.
Account Health
ODR, late shipment, listing policy, and product safety — watched weekly so a metric does not become a selling-privilege problem.