Choose language · Choisir la langue · اختر اللغة
All guides
Partial coverage

Amazon FBA Partial Reimbursement: Separate Missing Units from Value Differences

Investigate a partial FBA reimbursement by checking event matching, distinct resolved units, cost evidence and the remaining question for Seller Support.

A shipping carton and separated coin stacks illustrating a partial inventory reimbursement.
Diagnose the differenceIllustration · FluxPilot Field Guide
Quick answer

First verify which incident the reimbursement covers. Then separate outstanding units from any dispute about the amount paid for resolved units. Check inventory resolutions, currency and cost evidence before deciding what remains for review.

There are two different kinds of shortfall

A partial reimbursement review can concern quantity or valuation. In the first, some affected units appear unresolved. In the second, the units are compensated but you want to understand the amount. Keeping those questions separate makes the investigation and any follow-up much clearer.

An apparent shortfall can also be a matching error. A reimbursement for another incident may have been attached to this one, or an inventory resolution may be missing from the worksheet. Start with the relationship between the evidence records rather than with the expected dollar total.

1. Rebuild the quantity history

Record the original affected quantity, later inventory resolutions and compensation linked to the event. Only subtract distinct, verified resolutions. Do not count a later found movement and an inventory reimbursement separately when they describe the same units.

Fictional example: five units are affected. Evidence supports one distinct unit found later, two units compensated in cash and one different unit compensated in inventory. One unit remains for investigation. If the inventory compensation is the same unit as the found movement, the arithmetic must be revised.

Illustrative quantity review; every resolution must be distinct
ComponentUnitsEvidence question
Original affected quantity5Is the event identified?
Found later1Is it linked to this incident?
Compensated in cash2Is the reimbursement allocated here?
Compensated in inventory1Does it overlap with found units?
Remaining for review1Is the non-overlap assumption verified?

2. Investigate valuation as a separate question

Amazon's cost-policy announcement distinguishes pre-order inventory loss or damage from loss or damage after a customer order. For the pre-order category it describes product sourcing or manufacturing cost and excludes shipping, handling and customs. Verify the current marketplace policy before applying a valuation basis.

For your review, retain the cost document, currency, relevant product mapping and unit basis. A supplier invoice for a carton of ten units cannot be compared directly with a one-unit reimbursement unless you calculate and document the per-unit cost. A selling price is not automatically the right comparator.

3. Calculate an internal estimate without declaring a debt

Using fictional data, one unresolved unit with a documented internal unit cost of $8 produces an $8 review estimate. Keep that figure apart from the cash already recorded. It describes the unresolved quantity using your chosen cost basis; it does not establish Amazon's liability or the outcome of a claim.

If all five units were compensated but the money differs from your expectation, do not reopen them as five missing units. Preserve the resolved quantity and create a valuation question with the original reimbursement reference, your calculation and supporting evidence.

If currency, unit cost or event matching is unknown, leave the comparison incomplete. A blank, explained estimate is more useful than a precise-looking number built from an unsupported assumption.

4. Prepare a narrow follow-up

For a quantity question, state which event is involved, what evidence covers the resolved units and what remains unclear. For a valuation question, identify the reimbursement and ask how the amount was calculated, using relevant cost evidence. Avoid mixing several unrelated incidents into one unexplained total.

Review the current procedure and timing before making a re-evaluation request. Amazon's October 15, 2025 announcement includes a separate re-evaluation window of 90 days from the initial claim. Treat that announcement as a reference to check against your current marketplace policy, not a universal deadline calculator.

5. Record the decision and refresh the audit

After a response, update the quantity status and valuation status independently. Keep the case reference, review date and decision evidence. A request for more documents is different from an approval, and an internal estimate is different from received cash.

FluxPilot's ledger, costs and reimbursement workflow can help surface apparent partial coverage. Inspect repeated products and uncertain matches before interpreting the displayed remainder. Your next action should follow the missing evidence: verify a link, obtain costs, clarify an amount or check eligibility.

The final record should explain why each unit is resolved or still under review and why the valuation question is open or closed. That explanation prevents a later export from turning the same issue into a new recovery estimate.

Frequently asked questions

Should I ask for the difference from my selling price?

First determine the applicable event category and valuation basis. Support the specific question with evidence rather than assuming selling price applies.

Does partial payment mean some units are still missing?

Not necessarily. Separate quantity coverage from valuation and verify inventory resolutions and event matching.

Sources and further reading

Workflows and examples are from FluxPilot. Amazon policies change; verify the current policy for your marketplace before filing a claim.

Amazon announcement: cost evidence and pre-order inventory reimbursement Amazon announcement: claim submission windows effective October 15, 2025 Amazon FBA inventory reimbursement policy (check your marketplace)