Formula used
Safety stock = z-score x square root of lead time demand variance plus lead time variance. The z-score comes from the selected service level.
Search intent: Users want to estimate buffer inventory.
This safety stock calculator estimates the buffer stock needed to cover demand changes and supplier delays. It uses service level, demand variability, lead time, and lead time variability. If sales history is thin, it uses a visible fallback instead of hiding the assumption.
Safety stock = z-score x square root of lead time demand variance plus lead time variance. The z-score comes from the selected service level.
When there are not enough 30-day sales periods, demand variability is estimated as 20% of average daily demand and shown in the explanation.
Use lower service levels for slow or low-margin items and higher levels for products where stockouts are costly.
| Field | Why it matters |
|---|---|
| average_daily_sales | Base demand level for the SKU. |
| last_30_days_sales / last_60_days_sales / last_90_days_sales | Used to estimate demand variability when available. |
| lead_time_days | The replenishment window safety stock must cover. |
| lead_time_variability_days | Extra uncertainty from supplier delays. |
| desired_service_level | Controls how conservative the buffer should be. |
If average demand is 4.5 units/day, demand variability fallback is 0.9 units/day, lead time is 21 days, lead time variability is 4 days, and service level is 95%, the calculator uses z-score 1.65 and returns safety stock of 31 units.
Do not rely on the result when recent sales history is not representative, such as a launch week, clearance sale, seasonal spike, or stockout period.
95% is the default. Use 90% for less critical items and 98-99% for high-demand products where stockouts hurt.
You can provide average_daily_sales or recent 30/60/90 day sales totals.
No. It is a formula-based estimate from your uploaded or typed inputs.
Found a confusing result, CSV issue, formula edge case, or wording problem? Send a short note. Please do not include sensitive SKU names, stock levels, costs, prices, sales numbers, or full CSV files.