Every weak claim costs you a strong one.
Amazon caps how many measurement requests an account may open each month, and it judges claim quality per account. So the question is never "is this SKU wrong?" — plenty are. It is which wrongs are worth a slot, and which should never be filed at all. Both halves of that decision are on this page.
The one number that decides everything
Every candidate SKU gets scored the same way:
Units sold in the look-back window × the per-unit error = what the claim is actually worth.
The trap is using units on hand. Reimbursement on a fee overcharge is computed on units that shipped, not units sitting in a warehouse. A pallet of a dead SKU with a $4 error is worth close to nothing. A fast seller with a $0.31 error, moving 480 units a month, is worth about $150 every month — and it keeps earning until the measurement is corrected.
How your catalog gets sorted
Every ASIN lands in exactly one, and the bucket decides what happens next.
| Bucket | What it looks like | What we do |
|---|---|---|
| Fight | Meaningful per-unit error and real sales velocity. Evidence is clean — Amazon's own recorded dimensions disagree with the physical product. | Filed first, one case per SKU, evidence attached. Chased past Amazon's ten-business-day standard until it resolves. |
| Stretch | The error per unit looks trivial — cents. But the SKU moves hundreds of units a month, so the monthly bleed is large and permanent. | Filed once the obvious wins are in. Usually the highest-value items on the board over a year, and almost nobody files them because the per-unit number looks too small to bother with. |
| Skip | Small error, slow seller. Or a discrepancy inside normal measurement tolerance. | Logged, not filed. Re-scored every cycle — if it starts selling, it moves up. |
| Blocked | Dimensions already agreed and matching. Two cases already open on the SKU. No sellable units for anyone to measure. Outside its window. | Not filed, and we say why. The "no measurable inventory" ones go on a re-file queue and return automatically when a shipment is received. |
Why we chase the ones that look too small
Two SKUs, both measured wrong, both eligible. Most services file the first and ignore the second.
| SKU A — looks worth it | SKU B — looks trivial | |
|---|---|---|
| Error on the fee, per unit | $4.10 | $0.31 |
| Units sold, last 30 days | 14 | 481 |
| Bleeding, per month | $57 | $149 |
| Over a year, uncorrected | $689 | $1,789 |
| Which gets filed first | second | first |
Illustrative figures in the shape of real cases from our account. The per-unit error on SKU B is small enough that a human scanning a spreadsheet skips it — which is exactly why ranking has to be arithmetic rather than instinct.
Three rules that move a SKU up or down
- Recurring beats one-time. A corrected measurement stops the overcharge on every future unit; a lost-inventory reimbursement pays once. Equal value today, the permanent one wins.
- Storage claims are free to file. They do not consume the monthly measurement allowance, so the storage record is checked and claimed independently — and it disagrees with the fulfillment record more often than anyone expects, in both directions.
- Deadline outranks value. Anything about to expire jumps ahead of anything larger with time left. An expired claim is worth exactly nothing, whatever the spreadsheet says.
The claims we will not file
Amazon evaluates cases per account. An account that submits a steady stream of weak, undocumented or duplicate claims gets slower handling and more reflexive denials — including on the claims that are genuinely good. The cost of a bad claim is not zero. It is charged to the credibility of your next one.
Which is an awkward incentive for a service paid on volume of recoveries. So here is our list, in public.
Anything outside its window
Reimbursement claims past their deadline, fee disputes past theirs. These are not long shots, they are automatic denials. Any service filing them is generating activity, not recoveries.
Claims Amazon has already paid automatically
A meaningful share of lost and damaged inventory is reimbursed by Amazon's own systems without anyone asking. Re-filing those produces duplicates, and billing you commission on money that would have arrived anyway is somewhere between sloppy and dishonest. We reconcile against reimbursements already issued before anything gets filed.
Duplicates of a claim already open
Including one you or another service filed. Duplicate cases on the same event get closed, and they are the fastest way to look disorganised to the people deciding your claims.
Losses that are genuinely yours
Damage caused by insufficient packaging on your side. Units that arrived non-compliant and were disposed of under policy you accepted. Customer damage on a return where the customer, not the warehouse, broke it. We will tell you these are not recoverable rather than spend your credibility discovering it.
Inventory claims with no cost documentation behind them
Since March 2025 these are valued at Amazon's own internal estimate, which runs below actual cost. Filing without documentation locks in the lower number. We would rather delay a week to get your supplier invoice on file than file fast and get paid less. Why this changed.
Speculative dimension disputes
We request remeasurements where the evidence supports it, not across the catalog on the chance something sticks. That capped monthly allowance is the reason: spending it on guesses means the SKU actually costing you thousands has to wait.
Appeals with nothing new in them
Resubmitting an identical case after a denial is not an appeal. If we cannot add evidence or cite the specific policy the denial got wrong, we close it and say so.
What this costs you: a lower number of cases filed than some competitors would report. What it buys you: a higher proportion approved, faster handling on everything else, and an account Amazon's support system has no reason to treat as noisy.
You see the ranking, not just the result
Your findings report shows every candidate we scored, which bucket it landed in, and the arithmetic behind it — including the ones we chose not to file and why. The buckets are re-scored every cycle, so a SKU that was a Skip in March because it barely sold becomes a Fight in October when it takes off.
If you disagree, file it yourself
It is your account. Where we decline something, we tell you what we found, why we think it will be denied, and what evidence would change our mind. If you want it filed anyway, you have every case tool we do — and we will document the finding for you at no charge.
See your catalog ranked.
The free audit sorts your ASINs into these buckets with real dollar figures — including the stretch items nobody else is filing.