S&OP and IBP Process

Sales & Operations Planning (S&OP) is a monthly cross-functional process that aligns demand signals, supply capability, and financial targets into one agreed operating plan. Integrated Business Planning (IBP) is the strategic evolution — extending the horizon to 24–36 months and connecting S&OP outputs directly to the annual operating plan (AOP) and strategic plan.

The 5-Step S&OP Cycle

Runs monthly, typically over 3–4 weeks:

Step	Timing	Participants	Output
1. Product review	Week 1	Product management, marketing	New product launch plan, portfolio changes, discontinuations
2. Demand review	Week 1–2	Sales, marketing, demand planning	Consensus unconstrained demand forecast
3. Supply review	Week 2–3	Operations, procurement, logistics	Constrained supply plan; capacity gaps identified
4. Financial reconciliation	Week 3	Finance, supply chain	Gap analysis: plan vs. budget vs. latest estimate
5. Executive S&OP	Week 4	C-suite + functional VPs	Decision on gaps; approved plan published

The executive S&OP meeting is a decision forum, not a status report. If it runs as a reporting meeting, the process has failed.

IBP: The Evolution

IBP (Oliver Wight definition) extends S&OP in three ways:

1. Longer horizon: 24–36 months vs. 12–18 for S&OP
2. Strategic linkage: IBP outputs feed the AOP and 3-year strategic plan (catchball with Hoshin — see CI Program Governance)
3. Financial integration: Finance is a full participant, not a recipient; the financial plan is reconciled in real time, not post-process

Major IBP software platforms: Kinaxis RapidResponse, o9 Solutions, SAP IBP, Blue Yonder (JDA) Luminate Planning.

Key Performance Metrics

Metric	Definition	Best-in-Class
Forecast accuracy (MAPE)	Mean absolute % error vs. actuals	<15% at SKU/week
Forecast bias	Systematic over/under-forecast	±2%
Schedule adherence	% of supply plan executed as planned	>95%
Inventory days on hand	Days of forward cover	Category-specific
Plan stability index	% of week-2 plan unchanged by week-4	>80%

Common Failure Modes

Failure	Root Cause	Fix
S&OP is a reporting meeting	Decisions made offline before the meeting	Pre-work is preparation, not pre-decision
Finance disconnected	Finance receives the plan but doesn’t co-own it	Finance joins Week 3 reconciliation as an equal
Spreadsheet process	No single version of truth; reconciliation consumes cycle time	Invest in planning platform
Sales sandbagging	Sales submits low forecasts to manage expectations	Separate demand forecast from sales quota
Supply plan always “constrained by everything”	No prioritization framework	Constraint ranking and trade-off logic

Maturity Model

Stage	Characteristics
Reactive	No formal S&OP; firefighting mode; demand and supply plans disconnected
Anticipatory	Monthly process exists; demand and supply reviewed separately
Collaborative	Cross-functional consensus; one number; financial reconciliation happens
Orchestrated	IBP: 24-month horizon; AOP-linked; scenario planning; board-level visibility

Most organizations sit at Stage 2 (anticipatory). Moving from Stage 2 to Stage 3 requires organizational change, not just a software upgrade.

S&OP in the DC Context

The S&OP plan directly drives warehouse operations:

• Staffing plan: Approved volume forecast feeds the labor model (see Labor Modeling) — headcount plans and temp agency contracts are set against the S&OP volume curve
• Inbound scheduling: Supply plan drives container/trailer arrival scheduling; dock capacity is a constraint input to the supply review
• Slot reservation: DC space allocation by SKU family is set against the S&OP inventory plan
• Throughput validation: Peak volume from the demand plan is tested against DC throughput capacity (see Throughput Analysis); gaps trigger investment or constraint decisions in executive S&OP

---

IBP vs. S&OP: The Practical Differences (Course 4.5 Depth)

The IBP label was introduced by George Palmatier around 2005 to differentiate a more strategically connected process from traditional S&OP. The substantive differences:

Dimension	S&OP	IBP
Planning horizon	12–18 months	24+ months rolling
Scope	Supply/demand balance	All business functions including strategy and capital
Financial integration	Month 3 reconciliation	Finance as a full participant from demand review
Scenario planning	Occasional	Routine; multiple scenarios evaluated every cycle
Executive ownership	VP-level review	Executive team; decisions affect AOP and strategic plan
External linkage	Internal focus	Extends to key customers and suppliers

Both S&OP and IBP use the same 5-step monthly cycle structure. The difference is depth of engagement, horizon, and what decisions get made in the executive meeting.

S&OE: The Weekly Execution Gate

Sales and Operations Execution (S&OE) is the weekly gate between the monthly S&OP plan and daily warehouse/production/logistics execution. It operates within the “frozen zone” — the 0–3 month horizon where S&OP decisions are already committed.

S&OE handles:

• In-period supply exceptions and short-term constraints
• Demand deviations that exceed the exception threshold
• Allocation decisions when short-term supply falls short of demand
• Coordination of urgent order changes

The value of S&OE: it absorbs the operational noise that would otherwise contaminate the monthly S&OP process. Companies without S&OE spend their S&OP meetings managing last week’s fire rather than the next 12 months. Companies with S&OE run cleaner monthly cycles because short-term exceptions have their own governance lane.

Planning Horizon and Aggregation

The planning horizon determines which decisions can be made in the S&OP context:

Horizon	Decision Types	Aggregation
0–3 months (frozen)	Execution adjustments only; managed in S&OE	SKU/week
3–12 months	Capacity adjustments, supplier renegotiation, workforce planning	Product family/month
12–24 months	Network changes, major capital, product portfolio decisions	Brand/category/quarter
24+ months (IBP)	Strategic investments, M&A, new market entry	Business unit/year

Most S&OP processes run at the product-family/month level in the 3–12 month window. Dropping to SKU/week for a 12-month horizon is a data management problem masquerading as a planning problem — the added granularity doesn’t improve decision quality, it just makes the meetings longer.

The One-Number Principle (Governance Rule, Not Math)

“One number” is the most misunderstood S&OP concept. It means one version of truth — one agreed demand number that all functions use for planning decisions. It does not mean the operational forecast, sales target, and financial plan are the same number.

Three distinct numbers always coexist:

• Operational forecast: best estimate of what customers will actually buy (probabilistic, uncommitted)
• Sales target/quota: what sales has committed to deliver (aspirational, incentive-linked)
• Financial plan: what the business has committed to external stakeholders (board, investors, budget)

The S&OP bridge process makes the gap between these three numbers explicit and manages it deliberately. The dysfunction is not having three numbers — it’s when each function hides its number and the gap is discovered at quarter end.

Palmatier’s IBP Maturity Stages

George Palmatier (Oliver Wight) defined 4 IBP maturity stages:

1. Reacting: No process; each function plans independently; performance is firefighting
2. Anticipating: Monthly S&OP cycle exists; demand and supply reviewed but financial integration is weak
3. Collaborating: Finance integrated; cross-functional decisions; external linkage beginning
4. Orchestrating (IBP): Full 24+ month rolling horizon; strategic decisions made in the IBP context; board-level outputs

Fewer than 5% of organizations achieve Stage 4. Moving from Stage 2 to Stage 3 is the most common transformation challenge — and it requires organizational change, not software.