Amazon FBA Inventory Found After Being Lost: How to Recheck Your Audit
Recheck an FBA lost-inventory candidate after a later found movement, without pairing unrelated events or counting the same resolution twice.
Investigate the relationship between the original loss and the later found movement. If evidence links distinct resolved units to the event, update the remaining quantity. Keep unrelated movements separate and check whether a reimbursement also refers to the same units.
A review result is a snapshot
A candidate created from an earlier export can change when new evidence arrives. The question is not only whether a product was reported missing; it is whether the specific incident remains unresolved at the latest review date. Preserve both the original observation and the newest evidence.
Our recommended process is to recheck open candidates after new exports rather than repeatedly adding them as new cases. The later movement should become a linked piece of evidence in the existing record, with its date and the reason it changes your interpretation.
Do not pair every negative row with the next positive row
Chronological proximity is a clue, not an event link. The same product can move through multiple locations or have several incidents. A positive quantity could have a different cause or refer to another part of the inventory history.
Compare the source references, inventory identifiers, location, movement category and case history available to you. Keep an ambiguous pairing provisional. If a report does not provide enough information, inspect the underlying activity in Seller Central instead of forcing a match because the unit counts happen to fit.
Worked example: four missing units and two distinct units found
In this fictional example, Event REVIEW-004 initially affects four units. A later movement shows two units, and supporting evidence establishes that those two resolve part of the original incident. Update the review quantity to two, while retaining both source records.
Now imagine the positive movement belongs to a different incident. In that case, the original four-unit candidate should not be reduced by that movement. The quantity alone cannot tell you which of these two scenarios is correct.
Use a notes column to make the relationship explicit: which reference was checked, which units appear resolved and what remains uncertain. That short explanation protects the next reviewer from interpreting a provisional arithmetic result as a confirmed resolution.
| Observation | Evidence status | Recommended action |
|---|---|---|
| 4 affected units; 2 later found | Link verified; distinct units | Review the remaining 2 |
| 4 affected units; 2 positive elsewhere | No incident link | Keep events separate |
| Found movement plus compensation | Possible overlap | Check before subtracting both |
| New export changes old status | Update not yet explained | Compare source versions |
Check for overlap with reimbursement evidence
If you also find a reimbursement record, determine whether it covers different units or relates to the same resolution. Subtracting two found units and two compensated units from a four-unit incident is only valid if the evidence establishes that they resolve four distinct units.
Where related records change the interpretation of a payment, retain their references and verify the effect. Do not assume a later record is a new cash recovery or an automatic reversal. Record what Seller Central evidence actually supports.
Update the queue, the estimate and the history together
When the remaining quantity changes, revise any internal cost-based estimate as well. For example, reducing a fictional candidate from four to two units at $8 per unit changes that estimate from $32 to $16. It does not determine the amount Amazon will approve.
Store the review date, previous quantity, new quantity, supporting file and explanation. If the event becomes fully resolved, keep it in a closed-record history. Deleting it entirely makes it harder to prevent duplicate review when an overlapping export is imported later.
Make rechecking part of the routine
Assign a next action to candidates waiting for more evidence. A refreshed export, a case response or a newly matched reimbursement should trigger a review of the existing record. Avoid treating every new source file as a fresh opportunity total.
In FluxPilot, use the supplied ledger and optional reimbursement history to investigate the candidate in context. Confirm the outcome in Seller Central and apply the current category-specific policy before submitting any unresolved portion.
The success measure is an explained inventory event: resolved by inventory, resolved by compensation, still under investigation or ready for an eligibility review. A smaller unresolved total after a careful recheck can mean the audit is becoming more accurate.
Frequently asked questions
Can I automatically subtract all found units for a product?
Verify the incident relationship first. A product-level total can include movements unrelated to the candidate.
Should I delete a resolved candidate?
Keep the closed record and its supporting evidence so overlapping exports do not restart the same investigation.
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 FBA inventory reimbursement policy (check your marketplace)