Best AI prompts for FBA reimbursements
These are copy-paste AI prompts for Amazon FBA reimbursements, drawn from 24 of the 26 sourced cases on this site. First are all 3 prompts the original sources published, quoted word for word. Then come 21 starter prompts we wrote, clearly labeled, so you can try the same jobs: lost and damaged inventory, inbound shortages, returns, audits, support cases, and fee checks.
Replace anything in [brackets]. Don't let a prompt file a case or send a message until you've checked the output.
Prompts published by the original sources
These 3 prompts were published by the people or companies in the cases. They are labeled From the source. The wording is unchanged, including any uneven phrasing. Rights stay with the original authors; see the license.
Weekly lost and damaged inventory check
From the source. Copy this prompt as published; replace anything in [brackets].
I'm attaching my Amazon Inventory Ledger and Reimbursements report for the last 60 days. Which units did Amazon lose or damage that it never reimbursed? Give me a table: FNSKU, date, event type, quantity, reference ID, and whether a reimbursement matches. Only list units where the ledger clearly shows a loss or damage and no matching reimbursement.
Credit: Dondada01, Forum post, Sep 28, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): They say it finds the mismatches 'in about a minute' and that the tip 'saved me real money this year', though they don't say how much. They also say the stockout answer is 'better than my gut was'.
Self-reported by the source, not independently verified.
A forum post with no figures. The seller points out that most of these claims now have a 60-day window, which is why a weekly check matters. Check each flagged unit against the ledger yourself before you file.
Open and stalled support cases across accounts
From the source. Copy this prompt as published; replace anything in [brackets].
Across all my client accounts, which cases are open, and which have had no reply from us in the last 7 days?
Credit: Nhan Dinh (@NhanTDinh), X post, Oct 22, 2026. Original source · Case on this site.
Tools named in the case: Claude, Cajari MCP.
Result (per source, vendor-affiliated): The author reports that across three agencies (89 client accounts, 1,714 cases), the question surfaced 23 open cases. Six were waiting on the agency, twelve had gone more than a week without a reply, and the oldest had been open 109 days.
From a vendor-affiliated source, not independently verified.
The author discloses a personal stake in Cajari. Case Log is in beta, and the AI can read cases but not reply to them.
Size-tier overcharge audit from the fee preview report
From the source. Copy this prompt as published; replace anything in [brackets].
Compare the dimensions Amazon has on file in the fee preview report against the true dimensions in my spec sheet. Flag every SKU where Amazon's dimensions are larger than mine. For each flag, calculate what the fulfillment fee should be at the correct size tier under Amazon's 2026 fee schedule. Compare it against the actual fees charged in the date range report over the last 90 days, and give me the SKU, the per unit overcharge, the total 90-day exposure, and a ranking by exposure.
Credit: Seller Labs, YouTube video, Apr 27, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, vendor claim): "$20,000 came back over the next 2 months in fee reimbursements he was actually owed." The video's worked example: 10 SKUs selling about 17 units a day, measured half an inch long at intake and pushed from standard size to small bulky, with the fee going from $6.97 to about $8.27, comes to "over $19,000" in 90 days.
From the tool's vendor, not independently tested.
A vendor video from Seller Labs, narrated by an AI avatar of Nhan Dinh from a script by the Seller Labs team; the seller isn't named. Reimbursement claims must be filed within 90 days of the charge, Amazon limits how many remeasure cases you can file at once, and the first reply is often a no.
Starter prompts written by AI Agents for Sellers
The source in these cases did not publish its exact prompt. We wrote these starter prompts so you can try the same workflow. Each one is labeled Starter prompt written by AI Agents for Sellers, based on [the case]. Replace anything in [brackets]. These starter prompts are part of our own text and are covered by the CC BY 4.0 license on this page.
Lost, damaged, and inventory ledger
Line up the inventory ledger with reimbursements already paid, and flag lost or damaged units that still need a claim.
Review the inventory ledger and account charges
Starter prompt written by AI Agents for Sellers, based on Inventory Ledger and Fee Reviews with ChatGPT.
You are an Amazon account specialist familiar with all of Amazon's terms of service and FBA policies. I'm pasting my Inventory Ledger (detailed view) and my fee/transaction report for the last 18 months. 1. Find units that were lost, damaged, or missing at fulfillment centers or inbound and not later found or reimbursed. 2. Find customer returns refunded more than 45 days ago where the unit was never returned or reimbursed. 3. Flag any fee charges that look inconsistent with the product's size tier. Output a table per finding (FNSKU, date, quantity, reason, evidence row) and draft the Seller Support message for each.
The case: Arbitrage Ops (@ArbitrageOps), X post, Jun 11, 2025. Original source · Case on this site.
Tools named in the case: ChatGPT.
Result (per source, self-reported): This is a tip post with no outcome reported.
Self-reported by the source, not independently verified.
Check any policy claims against Seller Central help pages. LLMs can cite outdated policy.
Reconcile approved reimbursements with the ledger
Starter prompt written by AI Agents for Sellers, based on FBA Reimbursement Reconciliation with Agent Central.
Pull my FBA reimbursements approved in the last 60 days with reason, quantity and amount. Then pull inventory ledger movements and FBA customer returns for the same ASINs and dates. List every lost/damaged ledger movement and every refunded return that has no matching reimbursement (match on ASIN/FNSKU, quantity and date). For each, show the claim deadline and the days left. Label every match as a candidate to check in Seller Central, not a confirmed claim.
The case: Agent Central, Vendor docs, Oct 17, 2026. Original source · Case on this site.
Tools named in the case: Agent Central.
Result (per source, vendor claim): These are vendor docs with no customer result. The vendor is upfront about limits: the AI 'can line up the records; it can't file the claim.' Matches are 'candidates to confirm, not proof.'
From the tool's vendor, not independently tested.
The ledger read doesn't include Amazon's adjustment reason codes, and no shared key links a ledger movement to the reimbursement that paid it. A trial only covers the last 30 days, which is shorter than some claim windows. U.S. claim windows depend on the event type; check deadlines in Seller Central.
Build a per-SKU inventory ledger dashboard
Starter prompt written by AI Agents for Sellers, based on FBA Inventory Ledger and Transfer Dashboard with Claude Code.
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.
The case: DataDoe, YouTube video, Jun 8, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, DataDoe.
Result (per source, vendor claim): This is a vendor demo with no measured result. It shows the finished dashboard and says a Claude skill to recreate it is in the video description.
From the tool's vendor, not independently tested.
Made by DataDoe's own channel. It needs a DataDoe account, and the first data pull takes about 24 hours. The same ledger view is the starting point for finding lost or damaged units to claim.
Trace each reimbursement to its source
Starter prompt written by AI Agents for Sellers, based on Reimbursement Source Tracing with Grok Bot.
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.
The case: TonyGainzzz (@TonyGainzzz), X post, Oct 21, 2026. Original source · Case on this site.
Tools named in the case: Grok Bot, Sellerboard, Unturned.
Result (per source, self-reported): For Sept 20 to Oct 20 he reports $302K in sales, $35.7K net profit and $11.3K in reimbursements: $5,678.02 from his VA's chat cases (50%), $3,556.12 from Amazon's automatic reimbursements (31%), $1,044 from closed-shipment cases (9%) and $1,005.25 from Unturned (9%, $753.94 after its 25% fee). His takeaway: Amazon only reimbursed 31% automatically, and 59% came from his team filing cases.
Self-reported by the source, not independently verified.
The bot did the accounting; people filed the cases.
Inbound shortages and shipment discrepancies
Compare units shipped with units received, and draft cases for inbound shortages.
File inbound shortage claims from shipped vs received
Starter prompt written by AI Agents for Sellers, based on FBA Inbound Shortage Claims with Grok Bot.
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 case: Maksym Tsanko (@MaksymTsanko), X post, Oct 21, 2026. Original source · Case on this site.
Tools named in the case: Grok Bot, WisePPC.
Result (per source, self-reported): 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.'
Self-reported by the source, not independently verified.
He doesn't say how the bot was connected to Seller Central or WisePPC, or what time period the claims covered. The case also notes Amazon's Agent Policy (added to its Business Solutions Agreement on March 4, 2026) lets Amazon restrict AI agents in Seller Central.
Daily check for short FBA inbound shipments
Starter prompt written by AI Agents for Sellers, based on Daily Brand Watch: Short Shipments, Review Requests and Badge Changes with Claude.
Here is my list of FBA inbound shipments with units shipped and units received [paste]. List shipments that are closed with fewer units received than shipped, the missing count per SKU, and how many days since closing. Draft the reimbursement case text for each, quoting the shipment ID and SKU.
The case: Alex Willen (The Automated Operator) (@Willenation), Blog post, Apr 16, 2026. Original source · Case on this site.
Tools named in the case: Claude, Playwright.
Result (per source, self-reported): He gives no figures for these jobs. He still files the shortage cases himself because there's no API for support cases.
Self-reported by the source, not independently verified.
This is one section of a longer round-up post about running his brands with AI. The stored prompt is the inbound-shipment check. Shipments can sit open for a month or two after receipt, which is why a daily check helps.
Draft a case for an FBA inbound discrepancy
Starter prompt written by AI Agents for Sellers, based on FBA Shipment Reimbursement Reconciler with an n8n Template.
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 case: n8n Template Store, Workflow template, Undated page. Original source · Case on this site.
Tools named in the case: n8n, OpenAI API.
Result (per source, template): 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.
A published workflow template, not a reported result.
This is a published workflow template, not a reported result. 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.
Returns and denied claims
Match returns to orders, turn photos into case text, and follow up when a claim is denied.
Match return labels to orders and draft cases
Starter prompt written by AI Agents for Sellers, based on Return Reimbursement Claims with ChatGPT.
I'm an Amazon FBA seller. Attached: photos of return labels from a removal order, screenshots of the original customer orders, and my notes. Tasks: 1. Match each return label to the correct customer order (explain the match). 2. Write a concise Seller Support case for each requesting reimbursement for a customer return that came back incomplete/damaged, citing the relevant Amazon FBA customer returns policy. 3. Draft a polite follow-up appeal for if Amazon offers less than the item's value. Only use facts from my attachments.
The case: Britton Jewell (@BuyHoldCollect), X post, Mar 28, 2025. Original source · Case on this site.
Tools named in the case: ChatGPT.
Result (per source, self-reported): He says these returns went from something he dreaded to 'just another workflow.' The final reimbursement amount isn't stated.
Self-reported by the source, not independently verified.
Amazon doesn't show the original order ID on returns, which is why the label-to-order matching mattered.
Turn return photos into reimbursement case details
Starter prompt written by AI Agents for Sellers, based on Turning Return Photos into Reimbursement Case Details with a Claude Bot.
Here are photos of a returned unit, its LPN sticker and the return slip [attach]. Extract: Return Shipment ID (the part between the first and second dash after 'RA #'), LPN, Removal Order ID, FNSKU (in the column labelled ASIN). Then write one line for Condition from what the photo shows, e.g. 'Returned missing all of the hardware needed to install the product.' Flag any character you're not sure of (l vs I, 0 vs O).
The case: Alex Willen (The Automated Operator) (@Willenation), Blog post, Jun 4, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): It works, and filing the cases now takes a few minutes a month. He still opens the case himself because Amazon has no API for support cases, and he decided against automating it in the browser.
Self-reported by the source, not independently verified.
Only the photo reading and the condition text use Claude; the rest is ordinary code. Small-font IDs with lookalike characters (l and I) were misread a couple of times in testing, which is why the validation step exists.
Pursue a denied customer-damage reimbursement
Starter prompt written by AI Agents for Sellers, based on Denied Reimbursement Claims Pursued with Codex.
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.
The case: jhliuyu (@jhliuyu), X post, Oct 30, 2026. Original source · Case on this site.
Tools named in the case: Codex, dot.
Result (per source, self-reported): The seller says Amazon eventually approved compensation and the credit was verified in their seller account: 'Real money recovered.' They don't say how much.
Self-reported by the source, not independently verified.
A short first-hand post with no amount or timeline. The point the seller makes is persistence: a tiny team often gives up on these cases because it can't keep chasing them.
Find return root causes and one listing fix per ASIN
Starter prompt written by AI Agents for Sellers, based on Return Root Causes and One Listing Fix per ASIN with a Claude Skill.
For my 5 ASINs with the highest return cost, read the FBA customer returns report, the product's reviews and the current listing side by side. For each ASIN give: - the likely root cause, with return counts, reason-code shares, 2-3 buyer quotes, the gap in the listing, and a confidence level (never 'high' from reason codes alone); - ONE change to test (title under 75 characters, counted; image brief; size chart; or supplier brief); - today's return rate as the baseline to check at 30 and 60 days. Don't change anything and don't contact buyers.
The case: Ori Firouz, Blog post, Oct 20, 2026. Original source · Case on this site.
Tools named in the case: Claude, Adi (Claude skill).
Result (per source, self-reported): Demo only, on a fictional store. In the example, a bamboo cutting board set was returned 12.0 times per 100 sold, 56% coded 'not as described.' 43 return comments said it was smaller than expected, 8 of 10 critical reviews agreed, and the 109-character title never gave the size. The proposed test was a 73-character title with '15 x 10 in' plus measurements on image 2. 'No result is promised.'
Self-reported by the source, not independently verified.
It only reads data. It never changes a listing or contacts buyers. For returns coded as a different item, it drafts Seller Support case text instead of accusing the buyer.
Audits and claim tables
Check a reimbursement service's findings, or rank likely claims from your own report exports before you file.
Check a reimbursement service's findings first
Starter prompt written by AI Agents for Sellers, based on Automated FBA Reimbursement Audits with Refunzo.
Before I hire a reimbursement service, help me check its findings. From the Reimbursements report and the Inventory Ledger (detailed) I attach, list: 1. units marked lost or damaged with no reimbursement and no later 'found' event, 2. customer returns refunded more than 60 days ago that never came back to sellable stock and weren't reimbursed, 3. any reimbursement that was later reversed. Give counts and estimated value at my unit cost: [paste cost per SKU].
The case: Jimi Patel (Refunzo), Blog post, Apr 16, 2026. Original source · Case on this site.
Tools named in the case: Refunzo.
Result (per source, vendor claim): These are vendor claims, not a measured customer result. The blog says the audit runs in minutes, compared with days to weeks by hand. Refunzo says running the reconciliation is free and it charges 15% of what's actually recovered.
From the tool's vendor, not independently tested.
Written by Refunzo's co-founder. The blog says most claim types allow up to 18 months, but Amazon's current U.S. policy uses shorter, event-specific windows (for example, 60 days for units lost or damaged in a fulfillment center), so check deadlines in Seller Central and don't wait.
Rank likely FBA reimbursement claims from CSVs
Starter prompt written by AI Agents for Sellers, based on FBA Reimbursement Claims Table with a Claude Code Skill Pack.
Here are my FBA shipment, inventory and returns CSVs: [attach]. Produce a ranked reimbursement claim table with ASIN, issue type, estimated amount, one-line evidence and confidence. I will file in Seller Central myself — draft case text only, no login.
The case: Wang Xiaohan (@wang_xiaohan), X post, Nov 6, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, Codex.
Result (per source, vendor claim): Product launch post: a free 10-SKU teaser and a paid pack/DFY pilot are mentioned; no public recovery dollars from a named seller.
From the tool's vendor, not independently tested.
An indie vendor skill pack (November 6, 2026). Sellers approve before any Seller Central case; no Amazon password is stored.
Cross-check seven FBA reports for cases worth chasing
Starter prompt written by AI Agents for Sellers, based on FBA Problem Finder Across Seven Inventory and Reimbursement Reports with Codex.
I'm giving you these FBA reports: inventory ledger, reimbursements, customer returns, removal orders, removal shipments, inventory adjustments and current inventory. Join them by SKU/FNSKU and date and find units that were lost, damaged, returned or removed without a matching reimbursement or reconciliation. Write a script for the math rather than estimating. Output one row per case: SKU, what happened, units, dates, evidence rows, and a label (act now / investigate / monitor / no action). Then build a simple dashboard of the results. Don't file anything.
The case: Shikha Mishra, YouTube video, Sep 26, 2026. Original source · Case on this site.
Tools named in the case: Codex.
Result (per source, self-reported): "Codex did the heavy lifting. It went through 89,000 records and finally narrowed everything down to just four cases that actually needed attention." The decision step used three requests, around 2,700 tokens. Everything ends up on one dashboard instead of seven reports.
Self-reported by the source, not independently verified.
A 2-minute demo. The video doesn't say whose account the reports came from or whether the four cases were filed or paid. The decision API is only partly named in the video, so it isn't tagged here.
Support cases and appeals
Draft Seller Support cases, and keep a case desk from sending anything without your approval.
Draft Seller Support cases, appeals, and POAs
Starter prompt written by AI Agents for Sellers, based on Seller Support Cases, Appeals and Listing Translations with ChatGPT.
This thread is only for my Seller Central case about [issue]. Here's the history so far: [original case text], [Amazon's replies], [my Account Health call notes]. Amazon just rejected my appeal with: "[paste]". Draft a new response that addresses exactly what they asked for, lists the attached evidence, and stays professional and under 250 words.
The case: u/HappyKapow, Reddit thread, Nov 19, 2024. Original source · Case on this site.
Tools named in the case: ChatGPT.
Result (per source, agency-reported): The agency calls ChatGPT a 'lifesaver' for cases that keeps replies professional 'especially when frustrated with inexperienced agents' and 'saves so much time and mental energy', and says its translations are 'way better than Amazon's auto-translations, especially when tone or cultural nuances matter.'
Reported by an agency about its own client work, not independently verified.
From a longer agency comment listing nine ways they use ChatGPT. The one-thread-per-issue habit is the reusable trick.
Run a draft-only Seller Central case desk
Starter prompt written by AI Agents for Sellers, based on FBA Back-Office Fleet of Grok Bots (Vendor Setup).
Act as my Seller Central case desk. Read my last 10 buyer messages and account-health notices [paste or attach]. For each: what it is, the deadline under the 24-hour response rule, policy risk (low/medium/high) and the next step. Then draft replies for the ones that need one. Don't send anything; I'll review each draft.
The case: CrokPot (Workplace AI), Vendor docs, Not dated on the page (checked Oct 29, 2026). Original source · Case on this site.
Tools named in the case: Grok Bot.
Result (per source, vendor claim): Vendor page only, with no reported results. The vendor says every bot drafts and nothing is sent, edited or submitted without your approval, and that it makes no earnings or time-saved guarantees.
From the tool's vendor, not independently tested.
This is the vendor's own product page, not a seller's reported result. Example numbers on the page are illustrations, not results. It costs $200/month and runs on the vendor's own workspace; you don't own the seat.
Fees, payouts, and records
Catch fee drift, reconcile payouts, pull the reports you need, and keep the records behind a claim.
Catch FBA fee drift and draft disputes
Starter prompt written by AI Agents for Sellers, based on FBA Fee Drift Alerts with n8n.
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 case: Rateb Sadeqi, Blog post, Sep 21, 2026. Original source · Case on this site.
Tools named in the case: n8n.
Result (per source, self-reported): 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.
Self-reported by the source, not independently verified.
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.
Reconcile orders shipped against settlement payouts
Starter prompt written by AI Agents for Sellers, based on Payout Reconciliation with Claude Code.
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 case: Jakob Wolitzki (DataDoe), Blog post, May 11, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, DataDoe.
Result (per source, vendor claim): 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.'
From the tool's vendor, not independently tested.
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.
Pull purchase and shipping confirmations from email
Starter prompt written by AI Agents for Sellers, based on Order and Shipping Confirmation Retrieval with Claude Code.
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.
The case: Yuri Jew (@yuri_jew), X post, Mar 15, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, Trigger.dev.
Result (per source, self-reported): He calls it an automation of 'one of the most annoying things about being an amazon seller' and offers to set it up for others for free.
Self-reported by the source, not independently verified.
The post doesn't say which submission it's for (for example, reimbursement or invoice requests).
Pull a Seller Central report from one sentence
Starter prompt written by AI Agents for Sellers, based on Seller Central Report Pulls from One Sentence with a Claude Skill.
Pull last month's FBA customer returns report from Seller Central through my SP-API credentials and save it as a CSV in my reports folder. Use Seller Central's definition of "last month" for my marketplace's time zone, and log the timestamp, report type, date range and output file name.
The case: Yuri Jew, Blog post, May 6, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): 'Pull last month's returns' puts a CSV in the reports folder about 30 seconds later, and every pull is logged with timestamp, report type, date range and output file so it can be audited or rerun. His weekly returns brief, restock forecast, settlement reconciliation and Buy Box audit now start from one prompt instead of a Seller Central login.
Self-reported by the source, not independently verified.
A lead-magnet post (comment to get the skill), with no time-saved figure beyond the 30-second pull. The audit log is the part worth copying: it lets you rerun the exact pull behind any number you report. SP-API setup is a one-time job.
Design a bookkeeping and shipments app
Starter prompt written by AI Agents for Sellers, based on Bookkeeping and FBA Shipment App with Claude.
Help me design (don't code yet) a small bookkeeping app for my Amazon + Walmart + eBay business. It must track: sales by channel, refunds, Amazon reimbursements, expenses, shipping costs, inventory on hand by SKU with COGS, and cash flow. Propose the data model (tables and fields), what each channel's settlement/transaction report maps to, and the 5 screens I need. Ask me about anything you're unsure of.
The case: Parker (@pmcommerce), X post, Oct 12, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): He says the best part is that 'when something breaks, Claude fixes it that day.'
Self-reported by the source, not independently verified.
You become the maintainer. This case is tagged reimbursements because the app tracks shipments and related records, but the stored prompt is a bookkeeping-app design request.
How we picked these
As of Nov 17, 2026, this site has 364 public, sourced cases. 26 of them include reimbursements as a topic. 3 of those cases include a prompt published by the original source; 21 include a starter prompt written by us and appear on this page, and 2 are not yet on this page.
Section 1 includes all 3 source prompts, unchanged. Section 2 includes all 21 starter prompts we wrote for the cases on this page, grouped by reimbursement job. This page covers 24 of the 26 reimbursement cases. We did not pick prompts to promote a tool. Vendor, vendor-affiliated, agency, and template cases are labeled as such.
Every case links to its original public source. Every number on this page is quoted from the case. We do not independently verify results. Counts reflect what we found, not market share or how many sellers use each tool. See how we source cases. Related pages: Reimbursements cases, Which AI agent for Amazon FBA reimbursements?, and State of AI Agents for Amazon Sellers.
See the Q4 2026 Report for how often these tools and jobs show up across 330 sourced cases.
License and how to cite this page
The counts, groupings, and original text written by AI Agents for Sellers, including starter prompts, are CC BY 4.0: reuse them with credit and a link to this page. Quotes, prompts marked “source”, and linked material belong to their original authors.
How to cite this page: AI Agents for Sellers, “Best AI prompts for FBA reimbursements”, as of Nov 17, 2026, https://aiagentsforsellers.com/prompts/amazon-reimbursements/