How should you audit an FBA low-inventory-level fee?
Start with the current Low-Inventory-Level Fee report, reconcile the charged FNSKU and shipped units to historical days of supply, and confirm that the product was eligible on the charge date. Then decide whether the right response is replenishment, demand control, a catalog correction, or monitoring for an applicable credit.
Amazon changed the US calculation to the product FNSKU level effective January 15, 2026. Do not reuse an older parent-product workbook or assume that every low stock position creates a fee. Eligibility, exclusions, metrics, and credit treatment can change, so use the live report and current help page for each audit.
Build the charge-to-FNSKU audit table
- Record marketplace, FNSKU, ASIN, SKU, size tier, charge date, shipped units, fee amount, and the transaction or settlement reference.
- Capture the historical days-of-supply values shown for the FNSKU and the exact measurement date instead of substituting a current dashboard screenshot.
- Reconcile sellable, reserved, inbound, receiving, stranded, and unsellable units so the inventory state is not overstated.
- Add trailing sales, promotions, stockouts, price changes, suppressed days, and seasonality that could distort a simple demand average.
- Mark the eligibility rule, exemption, exception, or credit path shown in the current help content and retain the supporting report.
Choose the smallest corrective action
If demand is stable and inbound stock is genuinely insufficient, recalculate the reorder quantity with realistic production, freight, check-in, and availability lead times. If a promotion or price change caused a temporary spike, protect the cash plan before accelerating a large purchase order.
When units are already inbound or delayed in receiving, model the timing gap and preserve shipment evidence. Do not create duplicate inbound shipments merely to improve a dashboard metric; excess units can replace a short-term fee with storage, aged-inventory, and working-capital costs.
Review exceptions and verify credits
- Separate new, seasonal, low-volume, replenishable, and non-replenishable products according to the live eligibility rules.
- Check whether Amazon-managed inbound or processing delays qualify for a credit under the current policy.
- Reconcile credits to the original FNSKU, charge period, and settlement rather than netting them against unrelated fees.
- Escalate only with the report row, inventory timeline, inbound evidence, and the specific rule you believe was applied incorrectly.
- Recheck the next fee report after the correction; a replenishment receipt does not prove the historical metric changed immediately.
Know when this control applies
This workflow is for US FBA products assessed under the low-inventory-level fee. It does not replace storage utilization, capacity, aged inventory, stranded inventory, or stockout planning, and it may not apply in another marketplace.
Confirm the current [Amazon low-inventory-level fee guidance](https://sellercentral.amazon.com/help/hub/reference/external/GV43F6S76Y9DHYRH?locale=en-US) before acting. Avoid hard-coding thresholds or rates in an operating sheet unless you also record the policy effective date.
Related Amazon seller guides
- [Use days of cover to prioritize inventory decisions](https://amazonmargincalculator.cloud/blog/amazon-days-of-cover-dashboard)
- [Request more FBA capacity only after a profit test](https://amazonmargincalculator.cloud/blog/amazon-fba-capacity-manager-profit-request)
- [Reconcile monthly Amazon fees by SKU](https://amazonmargincalculator.cloud/blog/amazon-fee-reconciliation-routine)