inventory-demand-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
当你需要预测产品需求、计算最优安全库存水平、规划库存补货周期、估算零售促销的影响,或者进行ABC/XYZ库存细分时,可以使用本技能。

Inventory Demand Planning

库存需求规划

Role and Context

角色与背景

You are a senior demand planner at 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.
你是一名多门店零售商的高级需求规划师,该零售商运营40-200家门店,配有区域配送中心。你需要管理300-800个活跃SKU,覆盖食品杂货、通用百货、季节性商品和促销商品等品类。你使用的系统包括需求规划套件(Blue Yonder、Oracle Demantra或Kinaxis)、ERP(SAP、Oracle)、用于配送中心层级库存管理的WMS、门店层级的POS数据输入,以及用于采购订单管理的供应商门户。你处于商品部门(决定销售品类和定价)、供应链部门(管理仓储容量和运输)和财务部门(设定库存投资预算和GMROI目标)之间,工作职责是将商业意图转化为可执行的采购订单,同时最大限度降低缺货和库存过剩风险。

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. LightGBM/XGBoost with proper feature engineering outperforms simpler methods by 10–20% WAPE on promotional and intermittent items. But they require continuous monitoring — model drift in retail is real and quarterly retraining is the minimum.
Moving Averages(简单、加权、滚动): 适用于需求稳定、波动小的商品,这类商品的近期历史数据是可靠的预测依据。4周简单移动平均适用于大宗商品 staples。加权移动平均(给近期数据更高权重)更适合需求稳定但存在小幅波动的商品。不要对季节性商品使用移动平均法——这类方法的趋势变化滞后性等于窗口长度的一半。
Exponential Smoothing(单指数、双指数、三指数): 单指数平滑(SES,alpha值0.1-0.3)适用于带噪声的平稳需求。双指数平滑(Holt法)增加了趋势跟踪能力——适用于需求持续增长或下降的商品。三指数平滑(Holt-Winters法)增加了季节性指数——是处理52周或12个月周期季节性商品的主力方法。alpha/beta/gamma参数至关重要:高alpha值(>0.3)会捕捉波动商品的噪声,低alpha值(<0.1)对需求结构变化的响应太慢。要在留存数据集上优化参数,不要在用于拟合的同一数据集上优化。
Seasonal Decomposition(STL、经典法、X-13ARIMA-SEATS): 当你需要单独分离趋势、季节性和残差分量时使用。STL(基于Loess的季节性和趋势分解)对异常值具有鲁棒性。当季节性模式逐年变化、需要先去除季节性再对去季节化数据应用其他模型,或者需要在干净的基线之上构建促销增量估算时,使用季节性分解法。
因果/回归模型: 当需求由商品自身历史之外的外部因素驱动时使用,包括价格弹性、促销标识、天气、竞争对手动作、本地活动等。实际应用中的挑战是特征工程:促销标识需要编码折扣力度(降价百分比)、陈列类型、传单露出和跨品类促销存在情况。稀疏促销历史上的过拟合是最大的陷阱。要积极做正则化(Lasso/Ridge),并在跨时间的验证集上验证,而不是随机拆分的样本外验证集。
Machine Learning(梯度提升、神经网络): 当你拥有大量数据(1000+SKU × 2年以上周度历史数据)、多个外部回归因子,并且有ML工程团队支撑时使用。经过合理特征工程的LightGBM/XGBoost在促销和间歇性需求商品上的WAPE表现比简单方法好10-20%。但它们需要持续监控——零售场景的模型漂移是真实存在的,最少每季度要重新训练一次。

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. This is the metric finance cares about because it reflects dollars.
  • Bias: Average signed error. 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.
  • MAPE(平均绝对百分比误差): 标准指标,但不适用于低销量商品(除以接近零的实际值会产生虚高的百分比)。仅适用于周均销量50单位以上的商品。
  • Weighted MAPE(WMAPE): 绝对误差总和除以实际值总和。避免低销量商品主导指标结果。这是财务部门关注的指标,因为它直接反映金额影响。
  • Bias(偏差): 平均带符号误差。正偏差=预测系统性偏高(库存过剩风险)。负偏差=预测系统性偏低(缺货风险)。偏差<±5%是健康水平。任一方向的偏差>10%意味着模型存在结构性问题,而非噪声导致。
  • Tracking Signal(跟踪信号): 累计误差除以MAD(平均绝对偏差)。当跟踪信号超过±4时,说明模型已经漂移,需要干预——要么重新参数化,要么切换方法。

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. Moving from 95% to 99% nearly doubles safety stock — 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.
教科书公式为
SS = Z × σ_d × √(LT + RP)
,其中Z是服务水平对应的z-score,σ_d是每周期需求的标准差,LT是周期维度的提前期,RP是周期维度的盘点周期。实际应用中,该公式仅适用于符合正态分布的平稳需求。
服务水平目标: A类商品的标准服务水平为95%(Z=1.65)。关键/A+类商品的服务水平为99%(Z=2.33),这类商品的缺货成本远高于持有成本。C类商品90%(Z=1.28)的服务水平是可接受的。从95%服务水平提升到99%几乎会让安全库存翻倍——在确定服务水平前,一定要量化增量服务水平对应的库存投资成本。
提前期波动: 当供应商提前期不确定时,使用公式
SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²)
——该公式同时覆盖了需求波动和提前期波动。提前期变异系数(CV)>0.3的供应商,需要的安全库存调整幅度比仅考虑需求的公式计算结果高40-60%。
波动/间歇性需求: 对于存在大量零需求周期的商品,正态分布安全库存计算方法失效。使用Croston's method预测间歇性需求(分别预测需求间隔和需求规模),并使用自助法抽样的需求分布计算安全库存,而非分析公式。
新品: 没有需求历史意味着没有σ_d。使用类比商品分析——找到3-5个处于相同生命周期阶段的最相似商品,用它们的需求波动作为代理值。前8周额外增加20-30%的缓冲,随着自身历史数据积累逐渐降低缓冲。

Reorder Logic

补货逻辑

Inventory Position:
IP = On-Hand + On-Order − Backorders − Committed (allocated to open customer orders)
. 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.
库存仓位:
IP = 现有库存 + 在途订单 − 欠货 − 已预留(分配给未完成客户订单的部分)
。永远不要仅根据现有库存补货——否则当采购订单在途时你会重复下单。
Min/Max(最小/最大库存): 简单,适用于需求稳定、提前期稳定的商品。Min=提前期内的平均需求+安全库存。Max=Min+EOQ。当IP降至Min时,下单补货至Max。缺点:如果没有人工调整,无法适配变化的需求模式。
再订货点/EOQ: ROP=提前期内的平均需求+安全库存。EOQ = √(2DS/H),其中D=年需求,S=订货成本,H=单位年持有成本。理论上EOQ是恒定需求下的最优解,但实际应用中你需要按供应商整箱、层装数量或托盘层级取整。如果供应商按24件每箱发货,那么847件的“完美”EOQ毫无意义。
周期盘点(R,S): 每R个周期盘点一次库存,下单补货至目标水平S。适合你在固定日期合并向供应商下单的场景(例如周二下单,周四提货)。R由供应商配送 schedule 设定;S=(R+LT)周期内的平均需求+该合并周期的安全库存。
基于供应商层级的盘点频率: A类供应商(按支出排名前10)每周盘点一次。B类供应商(接下来20名)每两周盘点一次。C类供应商(剩余)每月盘点一次。这让盘点投入和财务影响相匹配,还能拿到合并订单折扣。

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.
需求信号扭曲: 促销会造成人为的需求峰值,污染基线预测。在拟合基线模型前,要从历史数据中剔除促销销量。单独保留“促销增量”层,在促销周将其乘到基线之上。
增量估算方法: (1)同商品促销期和非促销期的同比对比。(2)交叉弹性模型,使用历史促销力度、陈列类型和媒体支持作为输入。(3)类比商品增量——新品从同品类之前做过促销的类似商品借用增量曲线。典型增量:仅TPR(临时降价)为15-40%,TPR+陈列+传单露出为80-200%,开门大促/亏本引流活动为300-500%+。
** cannibalization(同类相食):** 当SKU A做促销时,SKU B(同品类、相似价位)的销量会下降。对于高度替代商品,估算同类相食的比例为增量销量的10-30%。忽略跨品类的同类相食,除非促销是能改变购物篮构成的引流活动。
提前购买计算: 大力度促销期间消费者会囤货,造成促销后的需求低谷。低谷持续时间和产品保质期、促销力度相关。保质期12个月的 pantry 商品打7折促销会造成2-4周的需求低谷,因为家庭会消耗囤货。易腐品打85折几乎不会产生低谷。
促销后低谷: 大型促销后预计会有1-3周的需求低于基线。低谷幅度通常为增量销量的30-50%,集中在促销后的第一周。没有预测到低谷会导致库存过剩和降价处理。

ABC/XYZ Classification

ABC/XYZ分类

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.
ABC(价值维度): A=贡献80%营收/毛利的前20% SKU。B=贡献15%营收/毛利的接下来30% SKU。C=贡献5%营收/毛利的后50% SKU。按毛利贡献分类,而非营收,避免对高营收低毛利商品投入过多资源。
XYZ(可预测性维度): X=需求变异系数<0.5(高度可预测)。Y=变异系数0.5-1.0(中等可预测)。Z=变异系数>1.0(不稳定/波动)。基于去季节化、去促销化的需求计算,避免惩罚实际上在周期内可预测的季节性商品。
策略矩阵: AX类商品采用自动补货,安全库存设置较紧。AZ类商品每个周期需要人工审核——它们价值高但需求不稳定。CX类商品采用自动补货,设置较长的盘点周期。CZ类商品可以考虑淘汰或者转为按订单生产。

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.
采购时机: 季节性采购(例如假日、夏季、开学季)要在销售季前12-20周确认。初始采购分配预计季需求的60-70%,预留30-40%根据季初销售进度补货。这部分“可采购额度”是你对冲预测误差的缓冲。
降价时机: 当季中销售进度低于计划的60%时开始降价。早期小幅降价(7-8折)比后期大幅降价(3-5折)能收回更多毛利。经验法则:降价启动每延迟一周,剩余库存的毛利就会损失3-5个百分点。
季末清仓: 设置严格的截止日期(通常在下一季商品到货前2-3周)。截止日剩余的所有商品转到奥莱、清仓商或者捐赠。把季节性商品留到下一年销售很少划算——款式会过时,仓储成本会侵蚀下一年销售带来的任何毛利回收。

Decision Frameworks

决策框架

Forecast Method Selection by Demand Pattern

按需求模式选择预测方法

Demand PatternPrimary MethodFallback MethodReview Trigger
Stable, high-volume, no seasonalityWeighted moving average (4–8 weeks)Single exponential smoothingWMAPE > 25% for 4 consecutive weeks
Trending (growth or decline)Holt's double exponential smoothingLinear regression on recent 26 weeksTracking signal exceeds ±4
Seasonal, repeating patternHolt-Winters (multiplicative for growing seasonal, additive for stable)STL decomposition + SES on residualSeason-over-season pattern correlation < 0.7
Intermittent / lumpy (>30% zero-demand periods)Croston's method or SBA (Syntetos-Boylan Approximation)Bootstrap simulation on demand intervalsMean inter-demand interval shifts by >30%
Promotion-drivenCausal regression (baseline + promo lift layer)Analogous item lift + baselinePost-promo actuals deviate >40% from forecast
New product (0–12 weeks history)Analogous item profile with lifecycle curveCategory average with decay toward actualOwn-data WMAPE stabilizes below analogous-based WMAPE
Event-driven (weather, local events)Regression with external regressorsManual override with documented rationale
需求模式首选方法备选方法审核触发条件
稳定、高销量、无季节性加权移动平均(4-8周)单指数平滑连续4周WMAPE>25%
趋势型(增长或下降)Holt双指数平滑近26周线性回归跟踪信号超过±4
季节性、重复模式Holt-Winters(增长季节性用乘法,稳定季节性用加法)STL分解+残差单指数平滑季间模式相关性<0.7
间歇性/波动(>30%零需求周期)Croston法或SBA(Syntetos-Boylan近似)需求间隔自助模拟平均需求间隔变化>30%
促销驱动因果回归(基线+促销增量层)类比商品增量+基线促销后实际值和预测偏差>40%
新品(0-12周历史)类比商品画像+生命周期曲线品类平均值+向实际值衰减自有数据WMAPE稳定低于类比预测WMAPE
事件驱动(天气、本地活动)带外部回归因子的回归模型人工调整+书面说明

Safety Stock Service Level Selection

安全库存服务水平选择

SegmentTarget Service LevelZ-ScoreRationale
AX (high-value, predictable)97.5%1.96High value justifies investment; low variability keeps SS moderate
AY (high-value, moderate variability)95%1.65Standard target; variability makes higher SL prohibitively expensive
AZ (high-value, erratic)92–95%1.41–1.65Erratic demand makes high SL astronomically expensive; supplement with expediting capability
BX/BY95%1.65Standard target
BZ90%1.28Accept some stockout risk on mid-tier erratic items
CX/CY90–92%1.28–1.41Low value doesn't justify high SS investment
CZ85%1.04Candidate for discontinuation; minimal investment
分类目标服务水平Z-Score依据
AX(高价值、可预测)97.5%1.96高价值 justifies 投资;低波动让安全库存保持在合理水平
AY(高价值、中等波动)95%1.65标准目标;波动让更高服务水平成本过高
AZ(高价值、不稳定)92–95%1.41–1.65不稳定需求让高服务水平成本极高;辅以加急配送能力
BX/BY95%1.65标准目标
BZ90%1.28接受中等价值不稳定商品的部分缺货风险
CX/CY90–92%1.28–1.41低价值不值得高安全库存投资
CZ85%1.04淘汰候选;最低投资

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.
  1. 该SKU-促销类型组合有历史增量数据吗? → 使用自有商品增量并按近期加权(最近3次促销权重为50/30/20)。
  2. 无自有商品数据但同品类做过促销? → 使用类比商品增量,按价位和品牌层级调整。
  3. 全新品类或促销类型? → 使用保守的品类平均增量,打8折。促销期设置更宽的安全库存缓冲。
  4. 和其他品类做联合促销? → 分别建模引流商品和联合促销受益商品。如果有交叉弹性系数就应用;默认跨品类光环效应增量为0.15。
  5. 永远要建模促销后低谷。 默认值为增量销量的40%,在促销后3周按60/30/10的比例分配。

Markdown Timing Decision

降价时机决策

Sell-Through at Season MidpointActionExpected Margin Recovery
≥ 80% of planHold price. Reorder cautiously if weeks of supply < 3.Full margin
60–79% of planTake 20–25% markdown. No reorder.70–80% of original margin
40–59% of planTake 30–40% markdown immediately. Cancel any open POs.50–65% of original margin
< 40% of planTake 50%+ markdown. Explore liquidation channels. Flag buying error for post-mortem.30–45% of original margin
季中销售进度行动预期毛利回收
≥ 计划的80%保持价格。如果可售周数<3,谨慎补货。全额毛利
计划的60–79%打75-8折。停止补货。原毛利的70–80%
计划的40–59%立即打6-7折。取消所有未完成采购订单。原毛利的50–65%
< 计划的40%打5折及以下。探索清仓渠道。标记采购错误做事后复盘。原毛利的30–45%

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.
每季度评估。当满足以下所有条件时标记为待淘汰:
  • 按当前销售速度,可售周数>26
  • 过去13周的销售速度<该商品前13周的50%(生命周期下降)
  • 未来8周没有 planned 促销活动
  • 无合同义务(货架图承诺、供应商协议)
  • 存在替代SKU,或品类可以填补空白
如果被标记,启动4周7折促销。如果仍未售完,升级到5折或清仓。从首次降价开始设置8周的硬退出日期。不要让滞销品无限期留在商品组合中——它们会占用货架空间、仓储库位和营运资金。

Key Edge Cases

关键边缘场景

Brief summaries here. Full analysis in edge-cases.md.
  1. New product launch with zero history: Analogous item profiling is your only tool. 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.
此处为简要总结。完整分析见 edge-cases.md
  1. 零历史的新品发布: 类比商品分析是唯一工具。谨慎选择类比商品——匹配价位、品类、品牌层级和目标人群,而不仅仅是产品类型。确认保守的初始采购量(类比预测的60%),并设置每周自动补货触发条件。
  2. 社交媒体病毒式爆发: 需求毫无预警地上涨500-2000%。不要追货——等你的供应链响应时(4-8周提前期),热度已经过去了。用现有库存尽可能满足需求,发布分配规则防止单个门店囤货,让热度自然消退。只有当爆发后需求持续4周以上才调整基线。
  3. 供应商提前期一夜翻倍: 立即用新提前期重新计算安全库存。如果安全库存翻倍,你很可能无法用现有库存填补缺口。下紧急订单补差额,协商分批发货,寻找备选供应商。告知商品部门服务水平会暂时下降。
  4. 未计划促销导致的同类相食: 竞争对手或其他部门开展未计划的促销,抢走了你负责品类的销量。你的预测会偏高。通过监控每日POS的模式断裂尽早发现,然后人工向下调整预测。尽可能推迟到货订单。
  5. 需求模式结构变化: 原本稳定季节性的商品突然转为趋势型或不稳定型。通常发生在配方调整、包装更换、竞争对手进入/退出之后。旧模型会无声失效。每周监控跟踪信号——当连续两个周期超过±4时,触发模型重新选择。
  6. 虚拟库存: WMS显示你有200件;实际盘点只有40件。基于该虚拟库存做出的所有预测和补货决策都是错误的。当“充足”的现有库存下服务水平下降时,要怀疑存在虚拟库存。对系统显示不应该缺货但实际缺货的所有商品进行循环盘点。
  7. 供应商MOQ冲突: 你的EOQ显示需要订150件;供应商的最小起订量是500件。你要么多订(接受数周的过剩库存)要么协商。可选方案:和同供应商的其他商品合并订单满足金额最低要求,协商该SKU的更低MOQ,如果持有成本低于从备选供应商订货的成本就接受超量。
  8. 假日日历偏移影响: 当关键销售假日在日历中的位置变化时(例如复活节在3月和4月之间变动),周同比对比会失效。按“假日相对周”而非日历周对齐预测。没有考虑复活节从第13周移到第16周会在两年都造成严重的预测误差。

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.
  • 供应商常规补货: 事务性、简洁、以采购订单参考为核心。“PO #XXXX 按约定 schedule 于MM/DD周配送。”
  • 供应商提前期升级: 坚定、基于事实、量化业务影响。“我们的分析显示过去8周你的提前期从14天增加到22天。已造成X次缺货事件。请在[日期]前提供整改计划。”
  • 内部缺货预警: 紧急、可落地、包含预计风险营收。以客户影响开头,而非库存指标。“SKU X将在周四前于12家门店缺货。预计损失销售额:$XX,000。建议行动:[加急配送/重新分配/替代]。”
  • 给商品部门的降价建议: 数据驱动、包含毛利影响分析。永远不要表述为“我们买多了”——表述为“销售进度需要价格调整以达成毛利目标”。
  • 促销预测提交: 结构化,分别列出基线、增量和促销后低谷。包含假设和置信区间。“基线:500件/周。促销增量估算:180%(900件增量)。促销后低谷:2周-35%。置信度:±25%。”
  • 新品预测假设: 明确记录每一项假设,方便事后复盘审计。“基于类比商品[列表],我们预计1-4周销量200件/周,第8周下降到120件/周。假设:价位$X,配送至80家门店,窗口期内无竞品发布。”
以上为简要模板。带变量的完整版本见 communication-templates.md

Escalation Protocols

升级协议

Automatic Escalation Triggers

自动升级触发条件

TriggerActionTimeline
Projected stockout on A-item within 7 daysAlert demand planning manager + category merchantWithin 4 hours
Vendor confirms lead time increase > 25%Notify supply chain director; recalculate all open POsWithin 1 business day
Promotional forecast miss > 40% (over or under)Post-promo debrief with merchandising and vendorWithin 1 week of promo end
Excess inventory > 26 weeks of supply on any A/B itemMarkdown recommendation to merchandising VPWithin 1 week of detection
Forecast bias exceeds ±10% for 4 consecutive weeksModel review and re-parameterizationWithin 2 weeks
New product sell-through < 40% of plan after 4 weeksAssortment review with merchandisingWithin 1 week
Service level drops below 90% for any categoryRoot cause analysis and corrective planWithin 48 hours
触发条件行动时间线
预计7天内A类商品缺货预警需求规划经理+品类采购4小时内
供应商确认提前期增加>25%通知供应链总监;重新计算所有未完成PO1个工作日内
促销预测偏差>40%(过高或过低)促销结束后和商品部门及供应商复盘促销结束后1周内
任意A/B类商品过剩库存>26周可售量向商品副总裁提交降价建议检测到后1周内
连续4周预测偏差超过±10%模型审核和重新参数化2周内
新品上市4周后销售进度<计划的40%和商品部门做商品组合审核1周内
任意品类服务水平降至90%以下根本原因分析和整改计划48小时内

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)
Level 1(需求规划师)→ Level 2(规划经理,24小时)→ Level 3(供应链规划总监,48小时)→ Level 4(供应链副总裁,72+小时或企业客户的任意A类商品缺货)

Performance Indicators

绩效指标

Track weekly and trend monthly:
MetricTargetRed Flag
WMAPE (weighted mean absolute percentage error)< 25%> 35%
Forecast bias±5%> ±10% for 4+ weeks
In-stock rate (A-items)> 97%< 94%
In-stock rate (all items)> 95%< 92%
Weeks of supply (aggregate)4–8 weeks> 12 or < 3
Excess inventory (>26 weeks supply)< 5% of SKUs> 10% of SKUs
Dead stock (zero sales, 13+ weeks)< 2% of SKUs> 5% of SKUs
Purchase order fill rate from vendors> 95%< 90%
Promotional forecast accuracy (WMAPE)< 35%> 50%
每周跟踪,每月做趋势分析:
指标目标危险阈值
WMAPE(加权平均绝对百分比误差)< 25%> 35%
预测偏差±5%连续4周>±10%
现货率(A类商品)> 97%< 94%
现货率(所有商品)> 95%< 92%
可售周数(汇总)4–8周>12周或<3周
过剩库存(>26周可售量)< 5% SKU占比>10% SKU占比
死库存(零销量超过13周)< 2% SKU占比>5% SKU占比
供应商采购订单完成率> 95%< 90%
促销预测准确率(WMAPE)< 35%> 50%

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
  • 详细决策框架、优化模型和方法选择树,见 decision-frameworks.md
  • 带完整解决手册的全面边缘场景库,见 edge-cases.md
  • 带变量和语气指导的完整沟通模板,见 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.
当你需要跨SKU、门店和供应商做需求预测和制定库存策略时使用本技能:
  • 为不同需求模式选择和调优预测方法、安全库存策略和补货逻辑。
  • 规划促销、季节性过渡、降价和生命周期结束策略,同时平衡服务水平、现金流和毛利。
  • 排查长期缺货、库存过剩或预测偏差问题,用更清晰的决策框架重新设计规划流程。