Automated Replenishment: Configuring Amazon’s Auto-Replenishment Logic

A technical guide to setting up automated triggers and min/max inventory levels that move stock from external warehouses to Amazon FBA using sales velocity and predictive analytics to avoid stockouts and overstock.

Purpose and scope

Automated replenishment for Amazon FBA is the set of configuration rules, thresholds, and analytic inputs that determine when inventory should be moved from an external warehouse (third‑party, private, or AWD) into Amazon’s fulfillment network. The goal is to maintain the proper days of inventory on FBA to meet customer demand while minimizing excess storage fees and transfers. This guide explains the inputs, formulas, Amazon‑specific constraints, and practical steps to configure robust auto‑replenishment driven by sales velocity and predictive analytics.

Key concepts explained (beginner friendly)

• Sales velocity: The rate at which units sell over time, usually expressed as units per day or units per week. It is the primary driver of replenishment decisions.
• Lead time: Time from initiating a transfer (pick, pack, ship) at AWD to when inventory becomes available at FBA. Includes internal processing, carrier transit, and Amazon inbound processing.
• Reorder point (ROP): The inventory level at which a replenishment should be triggered. Common formula: ROP = (average daily sales × lead time) + safety stock.
• Min/Max levels: Min is the baseline reorder point; max is the target inventory level after replenishment. Together they control order frequency and batch size.
• Safety stock: Extra inventory held to cover demand variability and lead‑time uncertainty.
• Days of cover (DoC): How many days current FBA inventory will last at forecasted sales velocity.

Predictive analytics and Amazon’s role

Amazon provides restock recommendations and inbound management tools that use historical sales, seasonality, and trends. Third‑party systems and WMS solutions can supplement Amazon’s models with more granular inputs (promotions, lead‑time variability, channel mix). Amazon’s algorithms will also consider account limits (storage space, case entry limits), Inventory Performance Index (IPI), and category‑level constraints when accepting inbound shipments to balance the network and reduce long‑term storage exposure.

Configuring min/max and triggers — step by step

1. Gather baseline data: Collect at least 90 days of daily sales, lead time statistics from AWD to FBA (median, 95th percentile), and inbound processing days at Amazon.
2. Calculate average daily sales (ADS): ADS = total units sold in period / number of days in period. Use rolling windows (7, 30, 90 days) to capture trends and seasonality.
3. Estimate lead time (LT): Use conservative lead time for ROP calculations (e.g., 95th percentile) to avoid stockouts caused by occasional delays.
4. Determine safety stock: Simple approach: safety stock = z × standard deviation of demand during lead time. A practical, beginner‑friendly rule: safety stock = ADS × safety factor (0.5–2.0 depending on volatility). For low volatility use lower factor; for promotional SKUs use higher.
5. Set min (ROP) and max: ROP = (ADS × LT) + safety stock. Max = ROP + (ADS × target days of cover). Target days might be 14–60 days depending on SKU velocity and storage constraints.
6. Define triggers: Common triggers: (a) inventory falls below ROP at FBA, (b) projected days of cover falls below threshold, or (c) time‑based batch rule (e.g., weekly replenishment). Use a combination to avoid frequent small shipments.
7. Implement constraints: Factor in FBA capacity limits, palletization, minimum shipment sizes, and cost thresholds. Apply throttles to prevent oversizing when Amazon signals restricted receiving.

Example calculation (simple)

Assume ADS = 10 units/day, conservative LT = 7 days, safety factor = 1.0 (safety stock = 10 units × 1 = 10 units). Then ROP = (10 × 7) + 10 = 80 units. If target cover after replenishment is 30 days, Max = ROP + (10 × 30) = 80 + 300 = 380 units. Trigger a replenishment when FBA inventory ≤ 80 units, or when projected DoC ≤ 14 days, and batch shipments weekly to optimize transport cost.

How Amazon’s algorithms balance inventory

Amazon manages incoming inventory distribution, inbound processing prioritization, and, in some cases, internal redistribution to maintain service levels. Key behaviors to expect:

• Restock recommendations that combine historical sales, Browse‑node demand, and account constraints.
• Receiving throttles or temporary limits during peak periods, which require your system to delay or split shipments.
• Prioritization for higher velocity SKUs; slow movers may be given lower inbound priority to prevent capacity strain.
• Automatic placement of units across fulfillment centers, which affects lead time for transfers back to central warehouses if a redistribution is needed.

Best practices

• Use multi‑window forecasting (short, medium, long) and weight recent velocity more heavily when volatility increases.
• Monitor and update lead times regularly; include seasonal carrier delays and Amazon inbound variability.
• Batch replenishments to balance transport cost against inventory carrying cost — small frequent shipments lower inventory but raise shipping costs.
• Keep an actionable safety stock policy for promotional periods and launches; temporarily increase safety stock ahead of known spikes.
• Integrate WMS or 3PL data with Amazon REST or SP‑API to automate triggers and shipment creation.

Common mistakes and troubleshooting

Typical mistakes include using zero or static safety stock, relying only on average sales without accounting for variance, ignoring Amazon’s inbound constraints, and setting min/max too frequently (leading to many small, expensive shipments). Troubleshoot by validating forecasts against actual sales, running scenario tests (e.g., 20% surge), and monitoring KPIs: days of supply, stockout incidents, fill rate, and excess inventory (>180 days).

KPIs to monitor: stockout rate, fill rate, days of inventory on hand (FBA), units in transit, excess inventory days, IPI. Regularly review these and tune min/max and safety stock accordingly.

Summary

Effective automated replenishment for AWD → FBA combines sound forecasting of sales velocity, conservative lead‑time assumptions, and well‑tuned min/max settings. Use predictive analytics to set reorder points and safety stock, batch shipments intelligently, and integrate systems for end‑to‑end automation. Monitor Amazon‑specific behaviors and KPIs and iterate your settings to balance service level and cost.