Reimbursements · X post · source Oct 21, 2026
FBA Inbound Shortage Claims with Grok Bot
Find units lost on the way to FBA and file reimbursement claims
“getting $2,654 back for inventory lost on the way to FBA”
Per source Self-reported by the source, not independently verified.
Copy-paste prompt
Using my WisePPC data, compare units shipped vs units received for every FBA inbound shipment closed in the last [60] days. List each shipment with a shortfall: shipment ID, SKU, units sent, units received, units missing, and estimated value. Skip anything Amazon already reimbursed. For each remaining gap, draft the Seller Central case text with the evidence I'll need (invoice, packing list, carrier proof of delivery). Ask me before filing anything, then track each case until it is resolved.
The source didn't publish its exact prompt. We wrote this starter so you can try the same workflow. Replace anything in [brackets].
What they did
The seller's Grok Bot used WisePPC to compare the units they sent to FBA with the units Amazon received and found the gaps. In a reply in the same thread, the author says the bot asked his permission to file the Seller Central cases, then filed them and followed through until they were resolved.
How it went
The author reports the bot filed 10 claims and Amazon paid 9 of them in full, getting $2,654 back for inventory lost on the way to FBA. 'All I did was say yes.'
We only report what the source says. Results are self-reported unless noted.
Worth knowing
Short X post plus the author's own reply. He doesn't say how the bot was connected to Seller Central or WisePPC, or what time period the claims covered. Amazon's Agent Policy (added to its Business Solutions Agreement on March 4, 2026) lets Amazon restrict AI agents in Seller Central, and some sellers posted in October 2026 that their Grok Bots were blocked. See the Agent Policy case.