Inventory Demand Planning
Retail demand-planning expertise codified: forecasting methods, ABC/XYZ segmentation, safety stock, promo lift, and markdown timing.
- What
- Retail demand-planning expertise codified: forecasting methods, ABC/XYZ segmentation, safety stock, promo lift, and markdown timing.
- Cost
- Free
- Needs
- Use "inventory-demand-planning" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a senior demand planner's playbook, codified for multi-location retailers running 40 to 200 stores with regional distribution centers and 300 to 800 active SKUs. It covers the full loop: collecting and cleansing demand signals, selecting the forecasting method per SKU from the ABC/XYZ classification and demand pattern (moving averages for stable staples, Holt-Winters for seasonal items, STL decomposition when seasonality shifts, causal regression when price and promos drive demand, LightGBM or XGBoost only when you have 1,000+ SKUs times 2+ years of history and an ML team), applying promotional lifts with cannibalization offsets, computing safety stock from demand and lead-time variability with honest service-level math (moving from 95% to 99% service nearly doubles safety stock, so it makes you price that decision), generating purchase orders with MOQ and EOQ rounding, and monitoring forecast accuracy on MAPE, WMAPE, bias, and tracking signal. It also handles the edge cases textbooks skip: lumpy intermittent demand via Croston's method and bootstrapped distributions, new products via analog-SKU mapping with a 20 to 30% buffer for the first 8 weeks, and post-promo dip planning. By @affaan-m (skill authored by evos), listed here with credit to its creator. From the affaan-m/ECC repository; this skill declares its own license, Apache-2.0. Honest caveats: written for planners with real POS, ERP, and WMS data; without your demand history it becomes a methods tutor rather than a working planner. The ML sections assume an ML engineering team and quarterly retraining at minimum. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Use "inventory-demand-planning" with your Muse. Prerequisites: the Muse app (mobile or web). No installation, no API key, no extra account. Have your demand data ready (POS sell-through, lead times, current inventory position) for working answers; without data it works as a methods tutor. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/inventory-demand-planning/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Demand plan: [your situation, e.g. 3-week BOGO promo on a top-20 SKU, or safety stock review for 50 SKUs]. Data: [paste sell-through, lead times, MOQs, service targets]." 3. Ask Muse to show its method selection per SKU (why this model for this demand pattern) and the safety-stock math before the purchase-order quantities. Tip: ask for the forecast-accuracy diagnosis first if you already forecast. A tracking signal beyond plus or minus 4 means the model drifted and needs re-parameterizing, not just a new forecast run. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets or API keys into it, and review anything Muse proposes before it acts. Purchase-order quantities move real money, so validate the math against your ERP before ordering.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.