Reimbursements · Blog post · source May 11, 2026

Payout Reconciliation with Claude Code

Find orders Amazon shipped but never fully paid out

$4,200

“found $4,200 Amazon never settled”

Per source From the tool's vendor, not independently tested.

Copy-paste prompt

Copy-paste promptStarter prompt (written by us)
Using my connected Amazon data, compare every order shipped in the last 6 months against settlement payouts. Give me: the total gap in dollars by month, a list of orders with no settlement after 14 days (order ID, ship date, expected amount), and orders that settled for less than expected with the difference. Mark each as paid, pending or refunded. Don't open any cases; just give me the list to review.

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

Per a LinkedIn post by Jakob Wolitzki of DataDoe, Raffy Kumruyan connected Claude Code to a seller's Amazon account through the DataDoe MCP and asked one question: 'Show me what Amazon shipped vs what Amazon actually paid.' Claude built a dashboard of every shipped order against every settled payout, the gap in dollars by month, daily breakdowns, an order search showing whether each order is paid, pending or refunded, and an auto-sync every morning at 8 AM.

How it went

The post says the dashboard took 90 seconds to build and found $4,200 Amazon never settled, which it describes as 'Not stolen. Just delayed, fragmented, invisible.'

We only report what the source says. Results are self-reported unless noted.

Worth knowing

A vendor's post about its own product, retelling someone else's result; the seller isn't named. It doesn't say whether the $4,200 was later paid out or had to be claimed.

Original source

Blog postJakob Wolitzki (DataDoe) (Jakob Wolitzki (LinkedIn))Published May 11, 2026 · linkedin.com https://www.linkedin.com/posts/jakob-wolitzki_raffy-kumruyan-just-helped-an-amazon-seller-activity-7459566423846260737-doqOOpen the source

Keep going

Related use cases

ReimbursementsOlder source · Mar 2026

Order and Shipping Confirmation Retrieval with Claude Code

Pull purchase and shipping confirmations from email for a given ASIN ToolsClaude Code, Trigger.devSourceX post · Yuri JewSource dateMar 15, 2026PromptStarter prompt
View promptHide prompt for Order and Shipping Confirmation Retrieval with Claude Code,Starter prompt
Search my email for purchase/order confirmations and shipping confirmations related to [product name / ASIN] around [date] (± 14 days) for quantity [qty]. For each match, extract: retailer/supplier, order number, order date, item description, quantity, unit price, ship date, tracking number. Combine them into one summary table plus a list of the source emails, so I can attach them to a Seller Central case.

Inventory & Ops

FBA Inventory Ledger and Transfer Dashboard with Claude Code

Consolidate FBA ledger, transfer and inbound reports across marketplaces into one per-SKU view ToolsClaude Code, DataDoeSourceYouTube video · DataDoeSource dateJun 8, 2026PromptStarter prompt
View promptHide prompt for FBA Inventory Ledger and Transfer Dashboard with Claude Code,Starter prompt
From the FBA Inventory Ledger (summary and detailed), FC transfers and inventory reports I attach, build one table per SKU across all my marketplaces: starting balance, receipts, customer shipments, returns, transfers in/out, lost/damaged/found adjustments, ending balance and reserved/inbound quantities.
Then flag any SKU where units marked lost or damaged exceed units later found, or where the ending balance doesn't add up from the movements. Show the rows behind each flag.

Reimbursements

Denied Reimbursement Claims Pursued with Codex

Keep challenging a denied reimbursement for a return marked customer-damaged ToolsCodex, dotSourceX post · jhliuyuSource dateOct 30, 2026PromptStarter prompt
View promptHide prompt for Denied Reimbursement Claims Pursued with Codex,Starter prompt
My reimbursement claim for a returned unit marked "customer damaged" was denied. Here are the order ID, return details, the case ID and Amazon's replies: [paste].
Check the return and inventory records for evidence the damage happened in Amazon's care (carrier damage, warehouse damage, wrong disposition). Draft a short, factual reply asking Amazon to reinvestigate, citing the specific records. Then track the case and tell me when to follow up or ask for escalation. Don't send anything without my OK.

ReimbursementsReported numbers

Support Case Triage Across Client Accounts with Claude and an MCP

Find open and stalled Seller Central support cases across many accounts
23 open cases“the question surfaced 23 open cases” vendor-affiliated
ToolsClaude, Cajari MCPSourceX post · Nhan DinhSource dateOct 22, 2026PromptFrom the source
View promptHide prompt for Support Case Triage Across Client Accounts with Claude and an MCP,From the source
Across all my client accounts, which cases are open, and which have had no reply from us in the last 7 days?

ReimbursementsReported numbers

FBA Inbound Shortage Claims with Grok Bot

Find units lost on the way to FBA and file reimbursement claims
$2,654“getting $2,654 back for inventory lost on the way to FBA” self-reported
ToolsGrok Bot, WisePPCSourceX post · Maksym TsankoSource dateOct 21, 2026PromptStarter prompt
View promptHide prompt for FBA Inbound Shortage Claims with Grok Bot,Starter 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.

ReimbursementsReported numbers

Reimbursement Source Tracing with Grok Bot

Trace where every reimbursement dollar came from to see which claims pay
$11.3K“$11.3K in reimbursements” self-reported
ToolsGrok Bot, Sellerboard, UnturnedSourceX post · TonyGainzzzSource dateOct 21, 2026PromptStarter prompt
View promptHide prompt for Reimbursement Source Tracing with Grok Bot,Starter prompt
Pull every Amazon reimbursement for the last 30 days and trace each one to its source: automatic reimbursement, a case my team filed (closed shipment, lost or damaged in warehouse, customer return), or my third-party reimbursement service.
Give me a table with totals and % share by source, and the service's payout before and after its fee.
Then list closed shipments from the last 30 days with missing units that have no open or resolved case yet, so my VA can file them.
Show how each reimbursement appears in my Sellerboard profit report.