Home Blog Amazon's Low-Inventory-Level Fee: The Complete 2026 Guide to Staying Above the 28-Day Threshold

Amazon's Low-Inventory-Level Fee: The Complete 2026 Guide to Staying Above the 28-Day Threshold

September 04, 2026
Here is the complete article HTML: ```html

Most guides to Amazon's low-inventory-level fee treat it as an inventory management problem: hold more stock, keep your days of supply above the threshold, done. That framing is wrong, or at least incomplete. The real problem is a pipeline problem. Every day your incoming inventory spends at a supplier, at a prep center, riding a carrier truck, or sitting in an Amazon receiving queue is a day it does not count toward your on-hand supply. A reorder placed at what looks like a comfortable buffer can arrive at an Amazon fulfillment center too late to prevent a fee trigger - not because you misjudged your stock level, but because you did not account for every stage between a purchase order and a scan-in confirmation. Prep center speed, carrier transit, and FC receiving time are not logistics details. They are fee-avoidance variables.

What the Fee Is and Who Pays It

Amazon introduced the low-inventory-level fee in April 2024. The underlying logic: thin FBA inventory forces Amazon to store and ship from a wider spread of fulfillment centers to meet delivery promises, raising Amazon's own transportation costs. The fee prices that cost back to sellers who chronically understock.

The charge applies to FBA sellers only. It accrues per unit sold while a given FNSKU sits below the threshold - it is not a flat monthly charge. A high-velocity SKU running lean generates fees with every order; a slow mover at the same inventory level accumulates far less because the per-unit rate multiplies against actual sales. That distinction matters when modeling exposure: the same thin stock position has a very different dollar impact depending on how fast the ASIN sells.

At launch, the fee covered standard-size products only. Many sellers managing bulky items ignored it. That changed on January 15, 2026, when Amazon extended the scope to Small Bulky and Large Bulky products. The expansion caught sellers off guard for two reasons: bulky products tend to have longer supplier lead times and slower FC receiving windows, which amplifies the pipeline problem described in this guide. And bulky FNSKUs sitting in the lowest inventory bands carry the highest per-unit charges across any size tier. Sellers who had never built a replenishment discipline around this fee suddenly faced their most expensive version of it. For current rates by size tier and inventory band, check the FBA fee schedule in Seller Central - Amazon has revised these figures since the fee launched.

How the Rate Structure Works

The fee is not binary. It scales across two axes: the product's size tier and how far below 28 days of supply the FNSKU sits. As inventory drops, the per-unit charge rises. The further below threshold, the higher the rate. Size tier also matters - bulky products carry higher charges than standard-size equivalents at comparable inventory levels.

The three inventory bands that determine the rate are 21-28 days, 14-21 days, and 0-14 days. A product in the 21-28 band pays the lowest rate within its size tier. The same product in the 0-14 band pays the highest. For a seller moving significant daily volume on a large-standard ASIN sitting in the middle band, the accumulated monthly fee on a single SKU can rival a full month of FBA storage costs for that unit. To see the exact rates currently applied to your FNSKUs, open the SKU Economics report in Seller Central and download it as a CSV - it shows low-inventory-level fees charged per FNSKU alongside other fulfillment fees, line by line.

The Dual-Window Trigger - and the Seasonal Trap

The fee only fires when both the trailing 30-day and trailing 90-day historical days of supply fall below 28 days simultaneously. If either window stays at or above 28 days, no fee applies for that period. That dual-window design sounds like a safety net. For steady-state inventory, it often is. For seasonal sellers, it is a delayed trap.

Here is how the trap works. A seller runs a product at moderate sales velocity most of the year. In November, a strong seasonal spike arrives. Daily units sold in the trailing 30-day window jumps sharply. The on-hand inventory in the numerator stays the same - only velocity changes. The 30-day days-of-supply collapses. But the 90-day window still carries months of pre-spike slower sales, which pulls the 90-day average velocity down and keeps 90-day days-of-supply above 28. So the fee does not trigger during the spike itself, even though inventory is genuinely thin. No alarm sounds. The seller does not replenish aggressively.

The trap closes in January. The November spike now sits fully inside the 90-day trailing window, pulling the 90-day average velocity up. On-hand inventory was not rebuilt because the spike period felt fine. Now both windows fall below 28 days at the same moment - often during a soft post-holiday period where fees accumulate across weeks before the seller notices in a report. The dual-window rule does not protect against structural understock. It changes when the fee registers, not whether it registers.

The 2026 FNSKU-Level Change and the Variation Trap

Before January 15, 2026, Amazon calculated days of supply at the parent ASIN level across all variants combined. A ten-variant listing with one out-of-stock size but healthy stock across the other nine was treated as a blended pool. That protection ended with the January 2026 update. Amazon now calculates the fee at the seller-FNSKU level. Each size, each color, each variation is its own independent calculation with its own fee exposure. An under-stocked FNSKU generates its own charge without affecting the other variants on the same parent.

A multi-variation listing that previously felt manageable at the parent level can now produce multiple simultaneous fee charges - one per under-stocked FNSKU - while neighboring variants on the same listing pay nothing. Sellers who set replenishment triggers at the parent ASIN level and never examined individual FNSKU inventory depth now have the wrong unit of analysis entirely.

To audit your exposure under the current rules:

  1. Open the FBA Inventory page in Seller Central.
  2. Open the column customization menu and add the Historical Days of Supply column to your view.
  3. Filter the view to show all FNSKUs under a single parent ASIN.
  4. Identify any FNSKU where Historical Days of Supply shows below 28 in either the 30-day or 90-day reading.
  5. Cross-reference those specific FNSKUs against the SKU Economics report to confirm whether fees are being charged and at what band.

Any FNSKU that consistently shows below 28 days in that view needs its own replenishment trigger, independent of the parent ASIN's overall stock position.

The Hidden Pipeline Days

The most common version of this fee problem is not a seller who is genuinely out of stock. It is a seller who has inventory somewhere in the restock pipeline that does not count yet. Amazon's days-of-supply formula uses only units physically checked into a fulfillment center. Inventory at a prep center, on a carrier truck, delivered to an FC dock but not yet scanned - none of it counts. Every stage of the pipeline between a purchase order and an FC check-in is invisible to the formula.

The full restock timeline broken down by stage:

  • Supplier lead time: Typically 7-21 days for domestic suppliers; international sourcing can run considerably longer. This is the stage most sellers account for.
  • Prep center turnaround: Industry standard is 24-48 hours at a well-staffed center with current capacity. Slower or backlogged centers run 3-5 business days. Q4 volumes can extend that further at facilities that have not scaled staffing. Every extra day of prep turnaround is one less day of days-of-supply coverage.
  • Carrier transit to Amazon FC: Ground shipping within the continental US typically runs 2-5 days depending on origin and destination FC.
  • FC receiving and check-in: After carrier delivery, Amazon's receiving and check-in process can take 2-10 days depending on the fulfillment center, carrier used, and how congested the network is at that moment. Amazon does not publish a receiving guarantee or timeline.

Add those ranges at the slower end: 21 days lead time plus 5 days prep plus 5 days transit plus 10 days FC receiving equals 41 days from PO creation to on-hand inventory. A seller who reorders at 35 days of visible supply does not have a comfortable cushion. They have a fee trigger already in motion. The prep center's turnaround time is often the most controllable link in that chain. A center with 24-hour processing and a daily ship cutoff removes nearly a week compared to a center with 4-day turnaround and a twice-weekly shipping schedule - and that difference flows directly into days-of-supply readings.

Inventory in transit does not count. Inventory at a prep center does not count. The only inventory that counts toward days of supply is inventory Amazon has physically checked into a fulfillment center. Plan your reorder points around that fact, not around when you expect units to leave your supplier.

The Six Exemption Categories

Not every FBA product is subject to the fee. Six situations currently remove a product or unit from exposure.

  • New parent ASINs within 180 days of first FC receipt: The clock starts at the first time any unit of that parent ASIN is received at an Amazon FC - not when you create the listing, not when you send the shipment. The exemption runs for 180 days from that date. Adding new size or color variations to an existing parent does not reset the clock. Plan your replenishment cadence so you have a healthy days-of-supply baseline before the window closes; there is no second 180-day grace period.
  • Low-velocity SKUs: Products that sold fewer than 20 units in the trailing 7 days are exempt. This exemption was added May 15, 2024, and remains in force. Note that a promotion or external traffic spike can push a previously exempt SKU above that velocity threshold within a single week, removing the exemption with minimal warning.
  • Grocery: Categorically exempt regardless of days-of-supply levels.
  • Apparel: Categorically exempt. Exemption status follows Amazon's assigned category, not your intended category. Verify the category shown on the back end of your product listing - if Amazon has classified it differently than you expected, the exemption may not apply.
  • Shoes: Categorically exempt under the same logic as Apparel.
  • AWD-replenished units: Inventory replenished through Amazon Warehousing and Distribution is exempt from the low-inventory-level fee for those specific units. The exemption applies to the AWD-managed portion of your inventory. AWD has its own storage cost structure, which runs lower per cubic foot than standard FBA off-peak storage - check the AWD fee schedule in Seller Central for current rates.

Strategies to Stay Above 28 Days Without Holding Excess Capital

The reflexive response to a fee based on low inventory is to hold more stock. That trades one cost for another - additional storage fees, capital locked in inventory, and higher exposure if a product slows down. Smarter approaches compress the pipeline or increase replenishment frequency rather than just inflating the reorder point.

Smaller, more frequent shipments outperform a single large monthly replenishment for a specific mechanical reason. Each new FC receipt refreshes the trailing 30-day on-hand average upward. One large shipment arriving after a long gap lets the average sag for weeks while you wait. Biweekly or weekly smaller shipments keep the average elevated throughout the cycle. A prep center with low minimums and a daily ship cutoff is the operational enabler of this strategy - without it, the shipping schedule itself becomes a pipeline bottleneck.

There is a real tradeoff to model before committing to higher-frequency shipping: Amazon's inbound placement fees generally favor consolidated shipments. More frequent, smaller boxes may increase inbound placement fee exposure if they result in less efficient network placement per shipment. The correct approach is to model both fees simultaneously - projected low-inventory-level fee savings versus projected inbound placement fee increase - at your actual SKU velocity and margin. The optimal frequency varies by SKU; there is no universal answer.

Additional strategies that reduce exposure without requiring excess capital:

  • Set reorder triggers at the FNSKU level, not the parent ASIN level - the January 2026 change makes parent-level triggers structurally incorrect for multi-variation listings.
  • Build a pipeline buffer into your reorder point that accounts for prep center turnaround, carrier transit, and FC receiving as separate time estimates, not a single lumped lead time.
  • After any promotion or external traffic push, model what happens to your 90-day average velocity over the following 6-8 weeks and whether both windows will collapse together.
  • Review the SKU Economics report monthly, filtered to FNSKUs that triggered fees in prior periods, to identify which SKUs are repeat offenders versus one-time incidents.

The Amazon-Caused Delay Credit

When Amazon's own receiving operations or an Amazon-managed service caused the inbounding or processing delay that resulted in low-inventory-level fees, Amazon credits those fees back. The credit posts by the 15th day of the month following the delay. The credit does not appear automatically on your dashboard in an obvious way - you have to look for it in the right report.

The SKU Economics report in Seller Central is the correct tool. Download it as a CSV for the month the fees were charged and for the following month. The report shows low-inventory-level fees per FNSKU alongside other fulfillment fees. When a credit posts, it appears as an offset against the fee line for the affected FNSKU. If the offset is not present by the 15th of the following month, open a Seller Support case with the specific FNSKU, the shipment ID, and the gap between the carrier-confirmed delivery date and the FC check-in date. That gap is the documented evidence of the Amazon-side delay. Pull the shipment details from the shipping queue in Seller Central and the carrier's proof-of-delivery confirmation before opening the case - having both timestamps ready makes the case straightforward to process.

AWD vs. a Fast Prep Center

Amazon Warehousing and Distribution exempts AWD-replenished units from the low-inventory-level fee entirely. AWD also carries a lower per-cubic-foot storage rate than standard FBA off-peak storage. For sellers with large inventory volume, slower velocity, or products expensive to store at FBA rates, AWD can address both the fee and the storage cost problem in one move. But AWD is not the right tool for every scenario.

AWD adds a transfer step. Units must move from an AWD warehouse to an FBA fulfillment center before they count as FBA-available inventory, and that transfer takes time. Sellers whose primary problem is pipeline speed - getting units into Amazon's on-hand count faster - may find that AWD extends their effective pipeline rather than compressing it. The exemption is real, but so is the transfer lag.

Criterion Fast prep center - direct FBA AWD replenishment Both combined
LLIF exemption No - must maintain 28+ days actively Yes - exempt for AWD-replenished units Yes for AWD-managed portion
Storage cost Standard FBA rates apply Lower than FBA off-peak Lower for buffer stock held at AWD
Pipeline speed to FBA-available Fastest - single stage Slower - transfer lag from AWD to FC Fast replenishment plus deep buffer
Best fit High velocity, tight margins, time-sensitive replenishment High volume, slower velocity, storage cost pressure Variable-velocity or seasonal SKUs
Operational complexity Single inbound flow Two-stage inbound flow Highest - managing both flows

The scenario where both together make sense: a SKU with strong seasonal velocity swings. During the slow season, large quantities sit in AWD at lower storage cost with no low-inventory-level fee exposure. As peak season approaches, a fast prep center ships direct-to-FBA in smaller, frequent batches to build FBA-level days of supply ahead of the velocity spike. The AWD stock provides depth; the prep center provides speed. The combination handles what neither alone handles as cleanly.

Frequently Asked Questions

Does inventory sitting at a prep center count toward my Amazon days of supply?

No. Only units physically checked into an Amazon fulfillment center count as on-hand inventory for the days-of-supply calculation. Units at a prep center, on a carrier truck, or delivered to an FC dock but not yet scanned in are all invisible to the formula. This is the core reason prep center turnaround time and FC receiving speed are direct fee-avoidance variables, not just operational preferences.

If my 90-day days-of-supply window is above 28 days, am I safe from the fee right now?

Yes, for the current period - but that reading is a snapshot, not a guarantee. The fee requires both the 30-day and 90-day windows to fall below 28 simultaneously. If either stays above 28, no fee triggers that period. The risk is that a recent sales spike or promotion will shift your 90-day average velocity upward over the following weeks, pulling both windows below 28 together at a future date when you may not be watching closely.

How do I find out which specific FNSKUs on a multi-variation listing are triggering the fee?

Download the SKU Economics report from Seller Central as a CSV - it breaks out low-inventory-level fees per FNSKU, so you can see exactly which variants are being charged and at what rate. For proactive monitoring before fees trigger, the FBA Inventory page has a Historical Days of Supply column - add it via the column customization menu and filter by individual FNSKU to see which specific variants are running below 28 days in either window.

When does the 180-day new-ASIN exemption start, and does adding a new variation reset it?

The clock starts at the first receipt of that parent ASIN at any Amazon fulfillment center - not when you create the listing or when the shipment is sent. Adding new size or color variations to an existing parent ASIN does not reset the clock for the parent; only a genuinely new parent ASIN triggers a fresh 180-day window. Build your replenishment cadence to reach healthy days-of-supply levels before the window closes, because there is no second grace period.

Can I get a credit if Amazon's slow receiving caused my low-inventory-level fee?

Yes. Amazon credits back fees caused by Amazon-side inbounding or processing delays, and the credit should post by the 15th of the following month. Verify it appeared by pulling the SKU Economics report for the affected FNSKU in the month after the delay. If the credit is absent, open a Seller Support case with the shipment ID, the carrier-confirmed delivery date, and the FC check-in date - the gap between those two timestamps documents the delay and supports the credit request.

Does sending more frequent, smaller shipments always reduce my overall fees?

It reduces low-inventory-level fee exposure by keeping the trailing 30-day on-hand average higher between large replenishment events. But more frequent, smaller shipments can increase inbound placement fees if they result in less efficient network distribution per box. Model both fees together at your actual SKU velocity, size tier, and margin before shifting your shipping cadence - the optimal frequency is specific to each FNSKU, not universal across a catalog.

```

Need Help with FBA Prep?

Get professional prep services from SNS Prep Center

Contact Us 📞