Missing Cost Data in an FBA Reimbursement Audit: Why the Estimate Is Blank or Zero
Diagnose missing unit-cost data in an FBA inventory audit by checking identifier mapping, currency, unit basis and evidence before estimating value.
Check whether a verified unit cost is mapped to the affected product, in the correct currency and unit basis. Keep an unpriced inventory candidate separate from a genuine zero-value result. Do not substitute selling price just to fill the estimate.
A quantity finding can exist without a reliable value
You can have enough evidence to investigate an inventory incident while lacking the cost data needed to estimate its financial impact. Treat those as separate completeness questions. The candidate can remain open for review, with its value labeled unknown.
A blank estimate, a displayed zero and a real documented zero are different conditions. Check what the value represents before drawing a conclusion. The diagnostic steps below are our recommended review process; they do not assert that every interface uses the same missing-value behavior.
1. Check the product mapping
Compare the identifiers in your cost file with the identifiers retained for the inventory incident. A cost may exist but fail to map because the working copy altered the SKU, removed a leading zero or associated the cost with a different product variant.
Keep a mapping table when your purchasing system uses supplier item codes that differ from your inventory identifiers. Retain the source document and the explanation for the relationship. Similar product names are a clue to investigate, not sufficient evidence for copying a cost across products.
If several cost rows match the same product, resolve which one is relevant to the review instead of accepting the first row by accident. Record any date or batch assumptions that affect the choice.
2. Check unit basis and currency
An invoice amount may cover a case pack, carton or multiple products. Convert it to a defensible unit cost with the calculation visible. In a fictional example, $80 for ten identical units yields an $8 unit cost; $80 for a mixed carton does not support that calculation without more detail.
Keep currency as its own field. If your internal review converts a cost, record the conversion rate, date and purpose. Avoid comparing a EUR cost with a USD reimbursement as if the figures were directly interchangeable.
| Symptom | Question to check | Recommended action |
|---|---|---|
| Cost exists but candidate is unpriced | Do identifiers map correctly? | Verify product mapping |
| Estimate looks much too high | Is cost per carton or per unit? | Document the unit calculation |
| Two costs conflict | Which document and period apply? | Resolve the evidence |
| Cost and payment currencies differ | Was conversion intentional? | Separate or document conversion |
| No supporting cost record | What evidence is available? | Keep value unknown |
3. Check what belongs in the cost basis
Amazon's pre-order inventory cost announcement describes sourcing or manufacturing cost rather than the item's selling price, and excludes shipping, handling and customs. Check the current policy for your marketplace and incident category before using a value in a reimbursement question.
For the audit, keep the documented product cost separate from other business costs. You may track landed cost internally for profitability, but clearly label it if it differs from the basis relevant to the reimbursement investigation. Do not silently reuse one figure for both purposes.
4. Estimate only the quantity still under review
After event matching and distinct resolution checks, calculate the remaining quantity. Use that quantity for an internal unresolved-value estimate when a verified cost is available. Do not multiply the original incident quantity if some units are already resolved.
Worked example with fictional values: five affected units, three distinct verified resolutions and a documented $8 unit cost leave two units for review and an internal estimate of $16. If the cost is missing, the same quantity investigation remains, but the estimate should stay unpriced.
Do not add retail price, expected profit or unsupported overhead to make a candidate look more valuable. An accurate data gap is actionable: request the invoice, confirm the unit basis or repair the mapping.
5. Refresh the review after correcting the data
Keep a record of the cost source, mapping decision and review date. When you supply corrected cost information in FluxPilot, revisit the affected findings and compare them with the underlying documents. Check the actual result rather than assuming the upload fixed every mapping.
Prioritize the queue using more than dollar estimates. Evidence readiness, outstanding policy checks and approaching category-specific deadlines can matter even when a candidate is unpriced. A high estimated value with weak evidence should not automatically outrank a smaller well-documented incident.
Keep internal estimates separate from confirmed recoveries in monthly reporting. A new cost file can change an estimate without creating a new inventory event or a new payment.
Frequently asked questions
Should I use selling price when unit cost is missing?
Keep the estimate unpriced until you establish a suitable documented basis. Check the policy for the event category instead of filling the gap with retail price.
Does a zero estimate mean no inventory problem exists?
Check data completeness and the meaning of the display. Quantity investigation and valuation are separate tasks.
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 FBA inventory reimbursement policy (check your marketplace)