Skip to content

Monthly FBA reimbursement check with claim drafts

Runs your Seller Central inventory ledger, returns and reimbursement reports through fixed scripts to find lost or damaged units with no matching reimbursement and refunds where the item never came back. Each one is dated against the claim window, with a draft case message for you to verify and send.

Ecommerce and resaleWorks with Claude Code · Claude Desktop with MCPCommunity example

What it does

  • Reads the inventory ledger, returns, settlement and reimbursement reports you upload
  • Finds lost or damaged units with no matching warehouse reimbursement
  • Finds refunds that were neither returned nor reimbursed
  • Dates each item against the 60 day and 60 to 120 day claim windows
  • Drafts a case message per SKU or order still inside the window

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending any case to Amazon

You decide what happens next.

More about this workflow

This setup is for online sellers and resale shops juggling listings, orders and buyers. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads the inventory ledger, returns, settlement and reimbursement reports you upload. Next, it finds lost or damaged units with no matching warehouse reimbursement. Then it finds refunds that were neither returned nor reimbursed. After that, it dates each item against the 60 day and 60 to 120 day claim windows. Finally, it drafts a case message per SKU or order still inside the window. It works with your marketplace data and spreadsheets, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sending any case to Amazon, and says plainly if a step cannot be undone.

“Results are framed as worth checking, never as money Amazon owes you.”
Vedant Agarwal Vedant-Agarwal on GitHub · Oct 6, 2026
Before you startMarketplace data · Spreadsheets accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • eBay

    Handles the marketplace data part of this job. Grant read scopes for orders and listings.

    API required: Yes. Needs an eBay developer account and an app keyset. Seller actions use OAuth tokens with the scopes you grant.

  • Google Sheets

    Handles the spreadsheets part of this job. Grant access to the single sheet it needs.

    API required: Yes. Needs a Google Cloud OAuth app or a service account with the Sheets API turned on.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Gemini 3.8 Flash

Built for agent workflows, with a free tier to test on.

$0.75 per million input tokens and $3.75 per million output tokens through December 31, 2026. $1.50 and $7.50 from January 1, 2027.

Google docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for many listings at once.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

ledger, returns, settlements, reimbursements

Amazon US

2Your prompt

4 of 4 still empty
Fill these in before you run it: [SELLER CENTRAL REPORTS: ledger, returns, settlements, reimbursements] [AVERAGE UNIT COST] [MARKETPLACE: Amazon US] [WHO VERIFIES AND FILES CASES] You are the Monthly FBA reimbursement check with claim drafts agent. Runs your Seller Central inventory ledger, returns and reimbursement reports through fixed scripts to find lost or damaged units with no matching reimbursement and refunds where the item never came back. Each one is dated against the claim window, with a draft case message for you to verify and send. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads the inventory ledger, returns, settlement and reimbursement reports you upload - Finds lost or damaged units with no matching warehouse reimbursement - Finds refunds that were neither returned nor reimbursed - Dates each item against the 60 day and 60 to 120 day claim windows - Drafts a case message per SKU or order still inside the window What you must never do without a yes from a person: - Sending any case to Amazon Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect eBay with its own login, not yours. Grant read scopes for orders and listings.
  2. 2Connect Google Sheets with its own login, not yours. Grant access to the single sheet it needs.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval27 / 30

Waits for a yes on: sending any case to amazon.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Human approval: Add a second named stop next to "sending any case to amazon", so every step that leaves your hands waits for a yes, and have the confirm say plainly what cannot be undone +3
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3

Do all of these to reach 89, up from 77.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Monthly FBA reimbursement check with claim drafts](https://trustcase.dev/badge/monthly-fba-reimbursement-check-with-claim-drafts.svg)](https://trustcase.dev/use-cases/monthly-fba-reimbursement-check-with-claim-drafts)
HTML
<a href="https://trustcase.dev/use-cases/monthly-fba-reimbursement-check-with-claim-drafts"><img src="https://trustcase.dev/badge/monthly-fba-reimbursement-check-with-claim-drafts.svg" alt="Trustcase trust score for Monthly FBA reimbursement check with claim drafts" height="20"></a>

Other workflows that use the same tools

  • Daily delivery app sales log

    Operations. Reads yesterday's sales from each delivery app and your point of sale every morning. Writes the totals into one sales sheet.

  • Weekly ops report

    Operations. Writes the Monday numbers summary so you do not build it by hand.

  • Vendor quote compare

    Operations. Lines up quotes from several vendors side by side.