inventory-demand-planning

Imported from sickn33/agentic-awesome-skills (skills/inventory-demand-planning/SKILL.md). Install upstream with npx skills add sickn33/agentic-awesome-skills --skill inventory-demand-planning. Copyright stays with the author.

When to Use

Use this skill when forecasting product demand, calculating optimal safety stock levels, planning inventory replenishment cycles, estimating the impact of retail promotions, or conducting ABC/XYZ inventory segmentation.

Inventory Demand Planning

Role and Context

Use a demand-planning perspective for a multi-location retailer operating 40–200 stores with regional distribution centers. You manage 300–800 active SKUs across categories including grocery, general merchandise, seasonal, and promotional assortments. Your systems include a demand planning suite (Blue Yonder, Oracle Demantra, or Kinaxis), an ERP (SAP, Oracle), a WMS for DC-level inventory, POS data feeds at the store level, and vendor portals for purchase order management. You sit between merchandising (which decides what to sell and at what price), supply chain (which manages warehouse capacity and transportation), and finance (which sets inventory investment budgets and GMROI targets). Your job is to translate commercial intent into executable purchase orders while minimizing both stockouts and excess inventory.

Core Knowledge

Forecasting Methods and When to Use Each

Moving Averages (simple, weighted, trailing): Use for stable-demand, low-variability items where recent history is a reliable predictor. A 4-week simple moving average works for commodity staples. Weighted moving averages (heavier on recent weeks) work better when demand is stable but shows slight drift. Never use moving averages on seasonal items — they lag trend changes by half the window length.

Exponential Smoothing (single, double, triple): Single exponential smoothing (SES, alpha 0.1–0.3) suits stationary demand with noise. Double exponential smoothing (Holt's) adds trend tracking — use for items with consistent growth or decline. Triple exponential smoothing (Holt-Winters) adds seasonal indices — this is the workhorse for seasonal items with 52-week or 12-month cycles. The alpha/beta/gamma parameters are critical: high alpha (>0.3) chases noise in volatile items; low alpha (<0.1) responds too slowly to regime changes. Optimize on holdout data, never on the same data used for fitting.

Seasonal Decomposition (STL, classical, X-13ARIMA-SEATS): When you need to isolate trend, seasonal, and residual components separately. STL (Seasonal and Trend decomposition using Loess) is robust to outliers. Use seasonal decomposition when seasonal patterns are shifting year over year, when you need to remove seasonality before applying a different model to the de-seasonalized data, or when building promotional lift estimates on top of a clean baseline.

Causal/Regression Models: When external factors drive demand beyond the item's own history — price elasticity, promotional flags, weather, competitor actions, local events. The practical challenge is feature engineering: promotional flags should encode depth (% off), display type, circular feature, and cross-category promo presence. Overfitting on sparse promo history is the single biggest pitfall. Regularize aggressively (Lasso/Ridge) and validate on out-of-time, not out-of-sample.

Machine Learning (gradient boosting, neural nets): Justified when you have large data (1,000+ SKUs × 2+ years of weekly history), multiple external regressors, and an ML engineering team. Compare LightGBM/XGBoost with simple baselines using leakage-free time-series validation; no fixed improvement is guaranteed. But they require continuous monitoring — model drift in retail is real and quarterly retraining is the minimum.

Forecast Accuracy Metrics

• MAPE (Mean Absolute Percentage Error): Standard metric but breaks on low-volume items (division by near-zero actuals produces inflated percentages). Use only for items averaging 50+ units/week.
• Weighted MAPE (WMAPE): Sum of absolute errors divided by sum of actuals. Prevents low-volume items from dominating the metric. Unit-based WAPE reflects units, not dollars; use explicit consistent value weights for financial error.
• Bias: Define signed error as forecast minus actual, so positive means overforecast. For percentage bias use sum(forecast−actual)/sum(actual), with a defined zero-denominator policy. Positive bias = forecast systematically too high (overstock risk). Negative bias = systematically too low (stockout risk). Bias < ±5% is healthy. Bias > 10% in either direction means a structural problem in the model, not noise.
• Tracking Signal: Cumulative error divided by MAD (mean absolute deviation). When tracking signal exceeds ±4, the model has drifted and needs intervention — either re-parameterize or switch methods.

Safety Stock Calculation

The textbook formula is SS = Z × σ_d × √(LT + RP) where Z is the service level z-score, σ_d is the standard deviation of demand per period, LT is lead time in periods, and RP is review period in periods. In practice, this formula works only for normally distributed, stationary demand.

Service Level Targets: 95% service level (Z=1.65) is standard for A-items. 99% (Z=2.33) for critical/A+ items where stockout cost dwarfs holding cost. 90% (Z=1.28) is acceptable for C-items. At fixed uncertainty, moving from 95% to 99% multiplies safety stock by 2.33/1.65 ≈ 1.41 — always quantify the inventory investment cost of the incremental service level before committing.

Lead Time Variability: When vendor lead times are uncertain, use SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²) — this captures both demand variability and lead time variability. Vendors with coefficient of variation (CV) on lead time > 0.3 need safety stock adjustments that can be 40–60% higher than demand-only formulas suggest.

Lumpy/Intermittent Demand: Normal-distribution safety stock fails for items with many zero-demand periods. Use Croston's method for forecasting intermittent demand (separate forecasts for demand interval and demand size), and compute safety stock using a bootstrapped demand distribution rather than analytical formulas.

New Products: No demand history means no σ_d. Use analogous item profiling — find the 3–5 most similar items at the same lifecycle stage and use their demand variability as a proxy. Add a 20–30% buffer for the first 8 weeks, then taper as own history accumulates.

Reorder Logic

Inventory Position: IP = usable On-Hand + eligible On-Order − outstanding demand obligations (count each once). Never reorder based on on-hand alone — you will double-order when POs are in transit.

Min/Max: Simple, suitable for stable-demand items with consistent lead times. Min = average demand during lead time + safety stock. Max = Min + EOQ. When IP drops to Min, order up to Max. The weakness: it doesn't adapt to changing demand patterns without manual adjustment.

Reorder Point / EOQ: ROP = average demand during lead time + safety stock. EOQ = √(2DS/H) where D = annual demand, S = ordering cost, H = holding cost per unit per year. EOQ is theoretically optimal for constant demand, but in practice you round to vendor case packs, layer quantities, or pallet tiers. A "perfect" EOQ of 847 units means nothing if the vendor ships in cases of 24.

Periodic Review (R,S): Review inventory every R periods, order up to target level S. Better when you consolidate orders to a vendor on fixed days (e.g., Tuesday orders for Thursday pickup). R is set by vendor delivery schedule; S = average demand during (R + LT) + safety stock for that combined period.

Vendor Tier-Based Frequencies: A-vendors (top 10 by spend) get weekly review cycles. B-vendors (next 20) get bi-weekly. C-vendors (remaining) get monthly. This aligns review effort with financial impact and allows consolidation discounts.

Promotional Planning

Demand Signal Distortion: Promotions create artificial demand peaks that contaminate baseline forecasting. Strip promotional volume from history before fitting baseline models. Keep a separate "promotional lift" layer that applies multiplicatively on top of the baseline during promo weeks.

Lift Estimation Methods: (1) Year-over-year comparison of promoted vs. non-promoted periods for the same item. (2) Cross-elasticity model using historical promo depth, display type, and media support as inputs. (3) Analogous item lift — new items borrow lift profiles from similar items in the same category that have been promoted before. Typical lifts: 15–40% for TPR (temporary price reduction) only, 80–200% for TPR + display + circular feature, 300–500%+ for doorbuster/loss-leader events.

Cannibalization: When SKU A is promoted, SKU B (same category, similar price point) loses volume. Estimate cannibalization at 10–30% of lifted volume for close substitutes. Ignore cannibalization across categories unless the promo is a traffic driver that shifts basket composition.

Forward-Buy Calculation: Customers stock up during deep promotions, creating a post-promo dip. The dip duration correlates with product shelf life and promotional depth. A 30% off promotion on a pantry item with 12-month shelf life creates a 2–4 week dip as households consume stockpiled units. A 15% off promotion on a perishable produces almost no dip.

Post-Promo Dip: Expect 1–3 weeks of below-baseline demand after a major promotion. The dip magnitude is typically 30–50% of the incremental lift, concentrated in the first week post-promo. Failing to forecast the dip leads to excess inventory and markdowns.

ABC/XYZ Classification

ABC (Value): A = top 20% of SKUs driving 80% of revenue/margin. B = next 30% driving 15%. C = bottom 50% driving 5%. Classify on margin contribution, not revenue, to avoid overinvesting in high-revenue low-margin items.

XYZ (Predictability): X = CV of demand < 0.5 (highly predictable). Y = CV 0.5–1.0 (moderately predictable). Z = CV > 1.0 (erratic/lumpy). Compute on de-seasonalized, de-promoted demand to avoid penalizing seasonal items that are actually predictable within their pattern.

Policy Matrix: AX items get automated replenishment with tight safety stock. AZ items need human review every cycle — they're high-value but erratic. CX items get automated replenishment with generous review periods. CZ items are candidates for discontinuation or make-to-order conversion.

Seasonal Transition Management

Buy Timing: Seasonal buys (e.g., holiday, summer, back-to-school) are committed 12–20 weeks before selling season. Allocate 60–70% of expected season demand in the initial buy, reserving 30–40% for reorder based on early-season sell-through. This "open-to-buy" reserve is your hedge against forecast error.

Markdown Timing: Begin markdowns when sell-through pace drops below 60% of plan at the season midpoint. Early shallow markdowns (20–30% off) recover more margin than late deep markdowns (50–70% off). The rule of thumb: every week of delay in markdown initiation costs 3–5 percentage points of margin on the remaining inventory.

Season-End Liquidation: Set a hard cutoff date (typically 2–3 weeks before the next season's product arrives). Everything remaining at cutoff goes to outlet, liquidator, or donation. Holding seasonal product into the next year rarely works — style items date, and warehousing cost erodes any margin recovery from selling next season.

Decision Frameworks

Forecast Method Selection by Demand Pattern

Safety Stock Service Level Selection

Promotional Lift Decision Framework

1. Is there historical lift data for this SKU-promo type combination? → Use own-item lift with recency weighting (most recent 3 promos weighted 50/30/20).
2. No own-item data but same category has been promoted? → Use analogous item lift adjusted for price point and brand tier.
3. Brand-new category or promo type? → Use conservative category-average lift discounted 20%. Build in a wider safety stock buffer for the promo period.
4. Cross-promoted with another category? → Model the traffic driver separately from the cross-promo beneficiary. Apply cross-elasticity coefficient if available; default 0.15 lift for cross-category halo.
5. Always model the post-promo dip. Default to 40% of incremental lift, concentrated 60/30/10 across the three post-promo weeks.

Markdown Timing Decision

Slow-Mover Kill Decision

Evaluate quarterly. Flag for discontinuation when ALL of the following are true:

• Weeks of supply > 26 at current sell-through rate
• Last 13-week sales velocity < 50% of the item's first 13 weeks (lifecycle declining)
• No promotional activity planned in the next 8 weeks
• Item is not contractually obligated (planogram commitment, vendor agreement)
• Replacement or substitution SKU exists or category can absorb the gap

If flagged, initiate markdown at 30% off for 4 weeks. If still not moving, escalate to 50% off or liquidation. Set a hard exit date 8 weeks from first markdown. Do not allow slow movers to linger indefinitely in the assortment — they consume shelf space, warehouse slots, and working capital.

Key Edge Cases

Brief summaries here. Full analysis in edge-cases.md.

1. New product launch with zero history: Analogous item profiling is one option alongside research, preorders, expert judgment and pilot tests. Select analogs carefully — match on price point, category, brand tier, and target demographic, not just product type. Commit a conservative initial buy (60% of analog-based forecast) and build in weekly auto-replenishment triggers.

2. Viral social media spike: Demand jumps 500–2,000% with no warning. Do not chase — by the time your supply chain responds (4–8 week lead times), the spike is over. Capture what you can from existing inventory, issue allocation rules to prevent a single location from hoarding, and let the wave pass. Revise the baseline only if sustained demand persists 4+ weeks post-spike.

3. Supplier lead time doubling overnight: Recalculate safety stock immediately using the new lead time. If SS doubles, you likely cannot fill the gap from current inventory. Place an emergency order for the delta, negotiate partial shipments, and identify secondary suppliers. Communicate to merchandising that service levels will temporarily drop.

4. Cannibalization from an unplanned promotion: A competitor or another department runs an unplanned promo that steals volume from your category. Your forecast will over-project. Detect early by monitoring daily POS for a pattern break, then manually override the forecast downward. Defer incoming orders if possible.

5. Demand pattern regime change: An item that was stable-seasonal suddenly shifts to trending or erratic. Common after a reformulation, packaging change, or competitor entry/exit. The old model will fail silently. Monitor tracking signal weekly — when it exceeds ±4 for two consecutive periods, trigger a model re-selection.

6. Phantom inventory: WMS says you have 200 units; physical count reveals 40. Every forecast and replenishment decision based on that phantom inventory is wrong. Suspect phantom inventory when service level drops despite "adequate" on-hand. Conduct cycle counts on any item with stockouts that the system says shouldn't have occurred.

7. Vendor MOQ conflicts: Your EOQ says order 150 units; the vendor's minimum order quantity is 500. You either over-order (accepting weeks of excess inventory) or negotiate. Options: consolidate with other items from the same vendor to meet dollar minimums, negotiate a lower MOQ for this SKU, or accept the overage if holding cost is lower than ordering from an alternative supplier.

8. Holiday calendar shift effects: When key selling holidays shift position in the calendar (e.g., Easter moves between March and April), week-over-week comparisons break. Align forecasts to "weeks relative to holiday" rather than calendar weeks. A failure to account for Easter shifting from Week 13 to Week 16 will create significant forecast error in both years.

Communication Patterns

Tone Calibration

• Vendor routine reorder: Transactional, brief, PO-reference-driven. "PO #XXXX for delivery week of MM/DD per our agreed schedule."
• Vendor lead time escalation: Firm, fact-based, quantifies business impact. "Our analysis shows your lead time has increased from 14 to 22 days over the past 8 weeks. This has resulted in X stockout events. We need a corrective plan by [date]."
• Internal stockout alert: Urgent, actionable, includes estimated revenue at risk. Lead with the customer impact, not the inventory metric. "SKU X will stock out at 12 locations by Thursday. Estimated lost sales: $XX,000. Recommended action: [expedite/reallocate/substitute]."
• Markdown recommendation to merchandising: Data-driven, includes margin impact analysis. Never frame it as "we bought too much" — frame as "sell-through pace requires price action to meet margin targets."
• Promotional forecast submission: Structured, with baseline, lift, and post-promo dip called out separately. Include assumptions and confidence range. "Baseline: 500 units/week. Promotional lift estimate: 180% (900 incremental). Post-promo dip: −35% for 2 weeks. Confidence: ±25%."
• New product forecast assumptions: Document every assumption explicitly so it can be audited at post-mortem. "Based on analogs [list], we project 200 units/week in weeks 1–4, declining to 120 units/week by week 8. Assumptions: price point $X, distribution to 80 doors, no competitive launch in window."

Brief templates above. Full versions with variables in communication-templates.md.

Escalation Protocols

Automatic Escalation Triggers

Escalation Chain

Level 1 (Demand Planner) → Level 2 (Planning Manager, 24 hours) → Level 3 (Director of Supply Chain Planning, 48 hours) → Level 4 (VP Supply Chain, 72+ hours or any A-item stockout at enterprise customer)

Performance Indicators

Track weekly and trend monthly:

Additional Resources

• For detailed decision frameworks, optimization models, and method selection trees, see decision-frameworks.md
• For the comprehensive edge case library with full resolution playbooks, see edge-cases.md
• For complete communication templates with variables and tone guidance, see communication-templates.md

When to Use

Use this skill when you need to forecast demand and shape inventory policy across SKUs, stores, and vendors:

• Selecting and tuning forecasting methods, safety stock policies, and reorder logic for different demand patterns.
• Planning promotions, seasonal transitions, markdowns, and end‑of‑life strategies while balancing service, cash, and margin.
• Investigating chronic stockouts, excess inventory, or forecast bias and redesigning the planning process with clearer decision frameworks.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Model assumptions and decision authority

All rates, lift/dip ranges, thresholds, cadence, confidence bands and buy/markdown percentages are illustrative; validate them locally. WAPE and MAPE need explicit zero-demand handling and a comparable aggregation/horizon; a volume cutoff does not make MAPE valid. Sales during stockouts are censored demand, not true zeroes. Keep original history and event flags; estimate a counterfactual rather than silently deleting all promotion/weather periods or leaking future data. Fit all transformations inside each training fold, tune on rolling-origin validation at the actual replenishment horizon, and retain an untouched final test set.

Normal safety-stock z values target a cycle-service probability under the stated model, not unit fill rate or shelf in-stock rate. Use forecast error over the protection horizon, independent stationary period errors and fixed/review timing only where those assumptions hold. Correlation, variable lead time, trend, perishability and lost-sales/backorder policy need a fuller model or simulation. Do not count expected demand twice as safety stock. De-duplicate reservations and backorders, exclude quarantined/expired stock, and time-phase firm receipts.

Prepare recommendations/drafts. POs, cancellations, ERP/WMS adjustments, prices, liquidation/donation/destruction and external messages require approved authority and applicable contract/product controls; skill text grants no automatic permission. Do not infer recovered margin from gross revenue, or a statistical prediction interval from WAPE alone. Preserve honest forecast-error/overbuy explanations.

See forecast evaluation and decomposition.