Reimbursements · Workflow template · source Not dated on the page (checked Oct 29, 2026)
FBA Shipment Reimbursement Reconciler with an n8n Template
Find inbound units Amazon lost and never reimbursed, and draft the claims
Template only.
Per source A published workflow template, not a reported result.
Copy-paste prompt
Draft an Amazon Seller Support case for this FBA inbound shipment discrepancy. Shipment ID: [FBA...], SKU [x], units shipped [n], units received [n], already reimbursed [n]. State the facts only, attach-ready: shipment ID, SKU, quantities, the date the shipment closed, and a request to investigate and reimburse the [n] missing units. No more than 120 words.
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
A paid ($19) n8n template from n8n Template Store runs weekly on two Seller Central exports you put in Google Sheets: the shipment reconciliation report and the reimbursements report. It matches shipped against received quantities per SKU, subtracts anything already reimbursed, values the remaining units, has OpenAI draft a claim for each new discrepancy, saves the claim as a Gmail draft and logs it to a sheet.
How it went
Template only. It needs no SP-API access, and the weekly digest email keeps listing money still owed until Amazon reimburses it. The seller pitch is keeping the 25% a recovery service would take.
We only report what the source says. Results are self-reported unless noted.
Worth knowing
This is a published workflow template, not a reported result: nobody in the source says what it did for their sales. Read the template's setup steps and test it on one account before you rely on it. It's sold by the store, not a free n8n.io template. Check each draft against the shipment's case window and the received date before you file it, and don't file claims for units that are still being received.