Low-inventory fee playbook for replenishment teams

Low-inventory fees punish chronic understocking. They are easy to miss because they look like a fee problem, but the root cause is usually replenishment discipline: inaccurate lead times, late purchase orders, missed transfers, or overly conservative cash planning.

Find exposed SKUs

Start with SKUs that combine three signals:

• recent sales velocity
• low available FBA stock
• delayed inbound replenishment

Then check whether the fee exposure is large enough to change the operating decision. A small fee on a slow SKU may not justify intervention. A repeated fee on a high-volume SKU usually does.

Decide whether to accelerate

Acceleration is not always the right answer. Compare the expected fee and stockout cost against the cost of faster prep, shipping, or supplier handling. The decision should be made on contribution margin, not urgency alone.

If acceleration is worth it, make the owner and due date explicit. If it is not worth it, update the baseline so the fee is understood instead of rediscovered next week.

Fix the planning loop

A fee playbook that only reacts will keep generating work. After each review, ask what changed in the planning assumptions: supplier lead time, prep time, sell-through, purchase order cadence, or cash allocation. Update the planning model so the same SKU does not become a repeat offender.

Separate unavoidable fees from process failures

Some low-inventory fees are rational. A seller may intentionally run down a SKU before discontinuing it, protecting cash instead of chasing perfect fee avoidance. A seasonal product may be near the end of its cycle, and sending more units would create storage exposure. Those cases should be documented as accepted exceptions.

The process failures are different. A purchase order was placed late. The warehouse missed a prep window. A supplier lead time changed but the planning model did not. A fast mover was excluded from replenishment because the buyer looked at units on hand instead of days of cover. These are the cases that need a corrective action.

Build a repeat-offender view

Reviewing fee exposure one week at a time hides chronic problems. Create a repeat-offender view that shows SKUs with low-inventory exposure across multiple review cycles. Sort by total fee exposure, lost sales risk, and the number of weeks the SKU has appeared.

This view changes the conversation. A one-week exception may need a tactical fix. A six-week exception needs an operating change. The buyer may need a different reorder point, the warehouse may need a faster receiving process, or finance may need to approve a different cash allocation for high-velocity products.

Feed the lesson back into replenishment

The playbook is only successful if future orders improve. After each review, update one of the underlying assumptions: reorder point, safety stock, supplier lead time, prep capacity, inbound transit time, or acceptable days of cover. Do not let the fee queue become a second replenishment system.

When the same data powers the fee review and the replenishment plan, the team can see the tradeoff clearly. Sometimes paying the fee is cheaper than moving inventory faster. Sometimes the fee is a signal that the operating model is too slow for the SKU's demand. The decision should be explicit either way.

Review the cash constraint openly

Low inventory is sometimes a cash allocation problem, not a forecasting problem. If the team is choosing which SKUs to fund, rank exposed products by contribution margin, stockout cost, fee exposure, and supplier reliability. That makes the tradeoff visible. The right answer may be to fund fewer SKUs well instead of partially funding many SKUs and paying fees across the catalog. Document that cash decision so the fee is understood later.