Reimbursements · Blog post · source Sep 21, 2026
FBA Fee Drift Alerts with n8n
Catch FBA fee overcharges and wrong size tiers without exporting reports
“over 8 hours of manual data entry saved weekly”
Per source Self-reported by the source, not independently verified.
Copy-paste prompt
Design an n8n workflow that runs every Monday: pull the last 7 days of FBA fee transactions per SKU through SP-API reports, compare each SKU's billed size tier and dimensions with my master spec sheet in Google Sheets, and flag any SKU whose fee per unit rose more than 5% or whose tier changed. For each flagged SKU, draft a Seller Support case with the SKU, my true dimensions and the fee difference. Don't submit anything; send me the drafts.
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
Rateb Sadeqi describes an audit pipeline he built: an n8n workflow runs every Monday to pull fulfillment fee transaction logs, return reports and inventory velocity sheets through Seller Central reporting APIs into a central data warehouse; a parser with AI anomaly detection compares billed dimensions with the product's true manufactured specs and sends an alert when an FBA fee spikes or a SKU moves into a wrong size tier; and when an overcharge or unreimbursed lost inventory is found, the workflow generates a dispute template with the SKU dimensions and shipment IDs, ready to submit to Seller Support.
How it went
He reports over 8 hours of manual data entry saved weekly, 'zero missed fee hikes,' and reimbursements reclaimed before they expire. He gives no dollar amounts.
We only report what the source says. Results are self-reported unless noted.
Worth knowing
A LinkedIn post that doesn't name the seller or the AI model used. His figure that one re-measurement error can cost $0.40 to $1.20 in margin per unit is a general estimate, not a reported loss.