How do I set up demand planning software for scenario planning and monthly forecast reviews?

Here’s a practical way to set up demand planning software so it supports both scenario planning and monthly forecast reviews.

1) Define the planning structure first

Before configuring the tool, decide:

• Planning horizon: e.g. 12–18 months rolling
• Planning grain: monthly by SKU / family / location
• Forecast levels: e.g. total company, category, product family, SKU
• Review cadence: monthly S&OP/IBP cycle, with weekly exception checks if needed
• Owner roles: demand planner, sales, marketing, finance, supply chain

This gives the software a clear hierarchy and workflow.

---

2) Load clean master data

Your software needs reliable inputs. Set up:

• Product hierarchy: item → family → category
• Customer / channel hierarchy if relevant
• Location hierarchy: plant, DC, region
• Calendar: fiscal months, holidays, promotional periods
• Units of measure: ensure conversions are defined
• Lifecycle flags: new item, active, phase-out, discontinued
• Constraints: MOQ, lead time, shelf life, capacity if applicable

Bad master data will make scenario planning unreliable.

---

3) Configure forecast baseline generation

Set the software to create a statistical baseline forecast using:

• Historical shipments or demand
• Seasonality
• Trend
• Outlier handling
• Intermittent demand logic if you have slow movers
• New product model if no history exists

Best practice:

• Let the system generate the baseline automatically
• Then allow planners to overlay business judgment

---

4) Set up scenario planning capabilities

Create separate scenario layers so you can compare assumptions without overwriting the baseline.

Common scenario types

• Base case: current consensus forecast
• Upside case: promotional lift, stronger market demand
• Downside case: lost customer, weaker market, supply disruption
• Price change scenario
• Launch scenario for new products
• Promotion scenario
• Capacity-constrained scenario

How to configure

In the tool, define:

• Scenario versioning
• Assumption drivers
• Copy/clone baseline to a scenario
• Editable driver inputs by period and product
• Comparison reports: baseline vs scenario, by volume/revenue/margin

Recommended drivers

Use driver-based inputs such as:

• Growth %
• Promo uplift %
• Distribution changes
• Win/loss probability
• Price elasticity
• Market index assumptions

This is better than manually editing every SKU.

---

5) Build the monthly forecast review workflow

A monthly review should be structured and repeatable.

Typical monthly cycle

1. System forecast refresh

   • Update with latest actuals
   • Recalculate statistical baseline

2. Exception detection

   • Flag large forecast error
   • Detect bias
   • Highlight SKUs with demand spikes/drops
   • Identify items affected by promotions or launches

3. Planner review

   • Review top variance items
   • Adjust based on market intelligence
   • Add reason codes for changes

4. Sales / marketing input

   • Incorporate account updates, promotions, campaigns

5. Consensus review

   • Align demand, supply, and finance
   • Lock approved forecast version

6. Publish forecast

   • Send approved forecast to ERP / supply planning

What to set up in the software

• Workflow approvals
• Task assignments
• Commenting and audit trail
• Version control
• Threshold-based alerts
• Forecast lock dates

---

6) Create forecast versions and controls

You’ll want multiple versions for monthly reviews, such as:

• Statistical forecast
• Planner-adjusted forecast
• Consensus forecast
• Scenario A / B / C
• Final approved forecast

Set rules for:

• Who can edit what
• When changes are allowed
• How scenarios become the final forecast
• How to preserve historical versions for analysis

---

7) Add KPI tracking

To improve forecast reviews, configure KPIs such as:

• Forecast accuracy (MAPE, WAPE)
• Bias
• Forecast value add (FVA)
• Scenario variance
• Service level impact
• Inventory impact
• Revenue and margin impact

Dashboards should show:

• Forecast vs actual
• Top errors by SKU/customer/category
• Scenario comparison
• Planner performance trends

---

8) Integrate with source systems

For best results, connect the planning tool to:

• ERP for orders, shipments, inventory
• CRM for pipeline and deals
• POS / market data if available
• Finance for budget/targets
• Promotion calendar / marketing systems
• Supply planning / APS tools

Automated data integration reduces manual cleanup each cycle.

---

9) Use workflow templates for monthly reviews

A simple template works well:

Monthly review agenda

• Demand assumptions update
• Last month actuals vs forecast
• Key customer or channel changes
• Promo/event impact
• New product / end-of-life updates
• Scenario review
• Consensus decision
• Forecast freeze / publish

Configure this as a standard workflow in the software so each cycle is consistent.

---

10) Pilot, then expand

Start with:

• One business unit
• One product family
• One region

Validate:

• Forecast accuracy
• User adoption
• Scenario usability
• Integration reliability

Then scale to the full organization.

---

Suggested setup checklist

• Define planning hierarchy and calendar
• Clean master data
• Load historical demand
• Configure statistical forecast
• Set up scenario templates
• Build monthly workflow
• Configure approvals and versioning
• Define KPIs and dashboards
• Connect ERP/CRM/finance data
• Pilot and refine

---

If you want, I can also give you:

1. a sample monthly forecast review process,
2. a recommended software configuration checklist, or
3. a template for scenario planning by SKU/category.