FBA Gap Auditorby Avyth

From your own Seller Central reports

Find FBA
reimbursement
gaps.

Compares what Amazon paid per unit with the price you supply.

Lists which lost‑or‑damaged events are still inside their 60‑day claim window. You file in Seller Central yourself.

Audit my reports →How it works
Example review · sample reportsas of 2026-09-14

Reimbursement gap · KT-MUG-16OZ-BLK

$9.10

Your supplied price
$12.95/ unit
Amazon paid
$8.40/ unit
Units reimbursed in cash
2

SuggestionWorth reviewing — Amazon decidesA comparison against the price you supplied, not Amazon's valuation.

BasisExact seller-SKU match · change the supplied price

Arithmetic and source rows

($12.95 − $8.40) × 2 = $9.10reimbursements-2026-09.csv row 2 · REIMB-7Q2K9-4381price from sku-prices.csv

Closing1
Open1
Expired1
Loss events · inventory-ledger-2026-09.csv
SKUEventWindow
PT-CANDLE-SOY-LAV2026-07-22Closing · 6 days left
KT-MUG-16OZ-BLK2026-08-30Open · 45 days left
GL-TUMBLER-20-SLV2026-07-02Expired · 14 days ago
PT-CANDLE-SOY-LAV2026-09-05Manual review

Start with your own reports

Files never leave your browser and results stay in this tab; refreshing clears them. No account connection.

  1. or drop reports here · 0 of 3

    Required: the Reimbursements report or the detailed Inventory Ledger. Optional: a price reference by SKU.

    CSV or TSV · up to three files, 5 MB, 20,000 rows and 100 columns each.

    Enter your supplied prices by seller SKU (optional)

    Prices entered here override matching CSV references and the audit recomputes on the next run. Use exact, case-sensitive SKUs. Conflicting references produce N/A. A selling price is your comparison reference, not Amazon's reimbursement valuation.

  2. Audit settings

    New York calendar date; countdowns are measured from this day.

    Currency

    Prices as plain decimals, no symbols or thousands separators.

    Accepted date formats

    YYYY-MM-DD, ISO timestamps, or unambiguous MM/DD/YYYY (07/08/2026 is rejected; convert it to ISO).

  3. Next: add at least one reimbursements or adjustments report.

Matching and deadline rules

A possible match requires identical FNSKUs when both exist, otherwise identical seller SKUs, and reimbursement approval 0–120 calendar days after the event. Matching is case-sensitive. It does not prove full quantity or reason coverage — so a possible match KEEPS its countdown bucket and is flagged for you to verify coverage before filing. Duplicate IDs are excluded from money totals, even when they may be legitimate separate line items. Auto-reimbursement or inventory restoration may already cover an event.

Negative M / Lost:M and E / Damaged:E adjustments (or warehouse / fulfillment-center lost / damaged text) use 60 days. Other reason codes need manual review. Day 60 is closing with zero days left; day 61 is expired. Customer-return reasons show a 60–120-day band after the refund/replacement date, which a ledger date cannot establish. Totals include only positive reimbursement gaps backed by valid price references; adjustment values are not estimated.

Check each gap against its source row

One SKU from the example reports, read left to right: two source rows, the difference they produce, and the claim window the ledger row sets. Export the worklist and file in Seller Central yourself.

reimbursements-2026-09.csv · row 2

REIMB-7Q2K9-4381 · KT-MUG-16OZ-BLK · 2026-08-28 · Lost_Warehouse

Amazon paid per unit
$8.40
Units reimbursed in cash
2

sku-prices.csv · KT-MUG-16OZ-BLK

Exact seller-SKU match

Your supplied price
$12.95

difference × units($12.95 − $8.40) × 2

$9.10

SuggestionWorth reviewing — Amazon decides

A comparison against the price you supplied, not Amazon's valuation.

inventory-ledger-2026-09.csv · row 3

KT-MUG-16OZ-BLK · 2026-08-30 · -2 · Damaged: Warehouse

claim window60 days from the event, as of 2026-09-14

Open · 45 days left

SuggestionWorth reviewing — confirm eligibility in Seller Central

How the columns were matched

Each suggestion states its basis. You confirm it, or pick another column, before anything is computed.

Reimbursement ID
reimbursement-idsuggested · header matches exactly
Seller SKU
skusuggested · header matches exactly
Paid per unit
amount-per-unitsuggested · header matches exactly
Quantity (cash reimbursed)
quantity-reimbursed-cashsuggested · header matches exactly
Reason code
reasonsuggested · header matches exactly

Audit 200 reimbursement rows free.

Available now

Free

  • Gap analysis for up to 200 reimbursement rows
  • Countdown review and supplied prices by SKU
  • CSV worklist export
Start an audit

FBA Gap Auditor

$5a month

  • Every reimbursement row, no 200-row limit
  • A dispute draft for each gap with a supplied price
  • A calendar (.ics) of closing windows

Sign in to Avyth and it unlocks on this device. Cancel from your account.

Before you file

Short answers on where the reports come from, what a gap is, and what happens to your files.

Where do I download the reports?
In Seller Central, open Reports → Fulfillment → Reimbursements. For loss events, open Reports → Fulfillment → Inventory Ledger and export the detailed view (or Inventory Adjustments where available). Download a period covering your events and reimbursements through your audit date. Menus and names vary by marketplace. A sales/pricing CSV is optional; it needs an exact SKU/FNSKU and a unit price you want to use as your reference.
Why is my gap N/A?
A gap needs a real expected price for that SKU, a valid paid-per-unit amount and a positive cash quantity. We never invent prices or treat the reimbursement itself as the expected value. Missing, conflicting or invalid references and duplicate reimbursement IDs get a visible explanation. Enter a reference and rerun the audit.
Does a gap mean Amazon owes me that amount?
No. A seller-entered or sales price is a comparison reference, not proof of Amazon’s reimbursement valuation. Eligibility, manufacturing-cost rules, inventory restoration and automatic reimbursements can change the outcome. Verify the current policy and evidence in Seller Central. This tool provides neither legal nor financial advice and is not affiliated with Amazon.
Are my files uploaded to a server?
No. Reports, SKU prices, calculations and CSV exports stay in your browser tab. There is no account connection and no file storage. Only an email signup you explicitly submit goes to our server for the launch list.
What does the 60-day window mean?

Amazon’s announced 2026 policy change (linked below) gives fulfillment-center loss or damage claims a deadline of 60 days after the reported event. Customer-return claims use a 60–120-day band after a refund or replacement. This tool uses those rules for review reminders; confirm the applicable marketplace policy and trigger date before filing.

Read Amazon’s reimbursement automation and eligibility-window announcement. Automatic reimbursement may already cover some events. The countdown does not establish entitlement or extend a deadline.