Sales and Operations Planning, and IBP
Sales and operations planning is a monthly cadence of reviews that produces one committed plan and the decisions behind it. It is not a meeting, and it is not something a system delivers. Software can hold the numbers and run the scenarios.
It is a cadence, not a meeting. Each review consumes the previous one's output, which is what makes a weak handoff visible rather than absorbed.
The executive review decides; it does not discover. Where surprises surface at the final meeting, the reconciliation step has failed and the cadence is decorative.
A sales target is not a demand plan. Substituting one for the other is the most common single failure, and it makes every downstream number unreliable.
The plan-to-budget gap is the governance question. Mature processes quantify it and close it with decisions. Immature ones maintain two numbers and reconcile them retrospectively.
Software supports the process and cannot create it. It can hold one set of numbers and run scenarios. It cannot confer decision rights or prevent renegotiation outside the cycle.
Market overview
The short answer
Sales and operations planning is a management process: a monthly cadence in which a business reviews its product portfolio, agrees a demand plan, tests whether supply can meet it, reconciles the result against the financial plan, and then commits to a single approved course of action at an executive review. Integrated business planning is a later and broader formulation of the same discipline, extending it to portfolio and financial integration over a longer horizon. Both are processes rather than software categories, and the label matters less than three things: whether the cadence actually holds, whether decision rights are explicit, and whether the gap between the operational plan and the financial plan is made visible and closed by decision rather than left to be discovered at quarter end.
KEY FACTS
Verified August 2026. Each statement below is complete on its own and cites its source in section 08.
Where did S&OP come from, and what is IBP?
The process emerged from the manufacturing planning tradition of the 1970s and 1980s, as an answer to a specific problem: aggregate production planning and material requirements planning could compute a plan, and nothing in them reconciled that plan with what the commercial side of the business intended to sell or what finance had committed to deliver. The consultancy Oliver Wight developed the response, and the concept is generally attributed to Richard Ling, who co-authored the first book on it in 1988. The professional body definition frames it as setting the overall level of output and related activity to best satisfy planned sales while meeting business objectives for profitability, productivity, and lead time.
Integrated business planning came later from the same source and is best understood as advanced sales and operations planning rather than a different thing. It adds explicit product and portfolio integration at the front of the cycle, deeper financial reconciliation, and a longer, more strategic horizon. Whether an organization calls its process one or the other matters far less than whether the additional elements are actually present, and the term itself is commercially owned rather than defined by any open standard.
This matters for a buyer because vendors and consultancies use the labels as positioning. A software product described as integrated business planning software is describing a market segment rather than conformance to a specification. The useful diagnostic is to ask which reviews exist, what each decides, and whether the financial plan is reconciled inside the cycle. Those questions distinguish processes; the acronym does not.
Table 1. The three terms compared. The final row is included because the labels in this area carry commercial ownership, and a buyer should know who is promoting the vocabulary a proposal uses.
What are the five reviews, and what does each decide?
The canonical cycle has five steps and each exists to produce a decision rather than a discussion. The product or portfolio review decides launches, transitions, and end of life, and confirms whether a launch is actually ready across supply, quality, and regulatory. Getting this first matters, because a demand plan built on a launch date that supply cannot support is wrong before it is written.
Figure 1. The cadence and the horizon. Each review consumes the previous review's output, so a weak handoff is visible at once rather than absorbed. The lower band distinguishes the planning horizon, where capacity and commitments are still decisions, from the frozen period, where they are facts to be executed against.
The demand review decides the unconstrained consensus demand plan, reconciling the statistical baseline with commercial intelligence about promotions, customers, and competitive activity. Unconstrained is the operative word: this step establishes what the market will take, not what the factory can make, because conflating the two hides the constraint that the next step exists to expose. SCR covers the forecasting methods and the software that produces the baseline in its demand planning guide, and this page deliberately leaves them there.
The supply review decides feasibility, testing the demand plan against capacity, inventory, materials, and lead times, and producing an explicit statement of where it cannot be met. The reconciliation step, sometimes called pre-review, decides the trade-offs: it quantifies the gaps between demand, supply, and the financial plan, frames the options with their consequences, and settles what can be resolved at working level and what must be escalated. The executive review then decides, commits resources, and resolves the escalations. If it is discovering the gaps rather than deciding on them, reconciliation did not do its job.
Table 2. The five reviews. Names vary between organizations and some add a data gathering step at the front; the sequence and the handoffs are what matter rather than the labels.
Who owns the number, and how do we set decision rights?
Owning the number does not mean writing the forecast. It means being accountable for an unbiased plan and for the consequences of it being wrong in either direction. That distinction resolves most of the arguments this question generates, because the objection to demand planning owning the number is usually that sales knows the customers, which is an argument about inputs rather than about accountability.
A workable arrangement assigns each review an accountable owner and makes the rest consulted or informed. Demand planning is accountable for the demand plan, drawing on commercial input. Supply planning is accountable for the feasibility statement. Finance is accountable for reconciliation and for quantifying the gap to the financial plan. The executive sponsor is accountable for the committed plan and for enforcing that it stands until the next cycle. Writing this down as a responsibility matrix takes an afternoon and prevents a year of ambiguity.
Two rules keep the cadence alive once rights are set. Dates are fixed for the year in advance, and attendance is delegated rather than the meeting postponed, because a slipped demand review compresses everything downstream and the cycle degrades within two months. And each review's output is the next review's input in a defined form, which makes a low-quality handoff visible immediately instead of being absorbed by whoever receives it.
The commercial function's role deserves care. Sales holds information nothing else can supply: what a specific customer intends, what a competitor is doing, what a promotion will actually deliver. The process needs that input and should not accept the sales target in its place. Separating the two, and being explicit that the demand plan is an unbiased estimate while the target is a commitment used to manage performance, is the single change that most often repairs a broken cycle.
Why is the demand plan against the financial plan the real question?
Most organizations carry two numbers. There is an operational plan describing what the business expects to sell and can supply, and there is a financial plan, usually the budget, describing what it has committed to deliver. When these agree, planning is straightforward. They rarely agree, and the difference between them is where the governance question actually lives.
Immature processes handle this by maintaining both and letting them diverge, reconciling only at period end when the outcome is already determined. That produces the characteristic pathology in which everyone knows the budget will not be met months before anyone says so, and the planning cycle continues producing plans against a number nobody believes. It also destroys the credibility of the process, because participants learn that the committed plan is not the plan the company is actually being run against.
A mature process treats the gap as the primary output of reconciliation. The step quantifies it, decomposes it into causes, and frames options with their consequences: additional promotional investment, accepting a shortfall, pulling capacity forward, changing mix. The executive review then decides which to take. The gap does not have to be closed to zero, and it does have to be acknowledged and owned. A cycle that produces a single plan with an unstated gap has produced a document rather than a decision.
Two supporting practices make this work. Assumptions should be recorded explicitly and reviewed each cycle, because a plan is only as good as the assumptions beneath it and unrecorded assumptions cannot be challenged when conditions change. And scenarios belong inside the cycle rather than as a separate exercise: presenting the executive review with a base case and two bounded alternatives converts a discussion about whether the number is right into a decision about which course to take.
What goes wrong, and what can software actually do?
Four failure modes account for most broken cycles. The first is the review becoming a status report: participants present what happened rather than deciding what to do, and no decision leaves the room. The second is renegotiation outside the cycle, where the committed plan is quietly revised in a corridor or a side meeting, which destroys the single plan and teaches everyone that the cadence is optional. The third is the sales target substituting for the demand plan, described in section 04. The fourth is calendar drift, where one slipped review compresses the rest and the cycle degrades until it is running on the day of the executive meeting.
Each has a structural remedy rather than an exhortation. A status report becomes a decision forum when the reconciliation step is required to bring framed options rather than analysis. Renegotiation stops when the executive sponsor visibly declines to reopen a committed number outside the cycle, which is a behavior rather than a policy. Target substitution stops when the two numbers are named separately and both are reported. Calendar drift stops when dates are fixed annually and delegation replaces postponement.
On software, be precise about the division. A planning system can consolidate data into one layer so that participants argue about the decision rather than about whose spreadsheet is right, generate a statistical baseline, hold assumptions, run scenarios and probabilistic simulations quickly enough to be useful inside a meeting, and maintain the audit trail of what was decided. Those are real contributions and they remove a large amount of preparation effort.
What it cannot do is supply governance. No system creates decision rights, enforces a calendar, prevents a senior leader from reopening a number, or makes an executive accountable for an unbiased plan. Maturity models published in this market are frequently used to imply that advanced tooling produces advanced maturity, and those models are published by an analyst firm that takes vendor payment and republished by vendors positioning their products at the upper stages. Treat them as a commercial framework. An organization with a disciplined cadence and spreadsheets outperforms one with an excellent platform and no decision rights, which is the uncomfortable conclusion this page exists to state.
The fair counterargument deserves a hearing. A serious critic would say the monthly aggregate cadence is too slow for volatile, short-life-cycle businesses, and that continuous replanning plus disciplined execution makes the fixed executive rhythm partly obsolete. There is force in that: horizon, granularity, and frequency should be fitted to the business rather than copied from a template. What the criticism does not displace is the need for cross-functional commitment to one plan, which continuous data does not by itself produce, because the problem the cadence solves is organizational rather than computational.
Frequently asked questions
Is S&OP a meeting or a process?
A process, specifically a monthly cadence of reviews that each produce decisions and feed the next. The executive meeting is one step within it. Organizations that treat the meeting as the whole process typically find it becomes a status report within a few cycles.
What is the difference between S&OP and integrated business planning?
Integrated business planning is a later and broader formulation of the same discipline, adding portfolio integration, deeper financial reconciliation, and a longer horizon. The term is promoted by a consultancy rather than defined by an open standard, so what matters is which elements are actually present.
How is this different from the demand planning we already do?
Demand planning produces the forecast. This process decides what the business will do about it across functions, testing it against supply and against the financial plan and committing to one course of action. SCR covers the forecasting side separately.
Who should own the number?
Demand planning should be accountable for an unbiased demand plan with commercial input, supply for feasibility, finance for reconciliation, and an executive sponsor for the committed plan. Owning the number means accountability for its lack of bias, not authorship of the forecast.
What horizon should the process cover?
Typically a rolling 18 to 24 months, extending to 36 in some businesses. The horizon should reach far enough that capacity, inventory, and commercial commitments are still decisions rather than facts, which is what distinguishes it from execution.
What is sales and operations execution?
The activity inside the frozen period: executing against the committed plan and rebalancing in the short term. It has a different owner, a different cadence, and a different purpose, and confusing it with the tactical planning cycle produces meetings that solve neither problem.
Should the demand plan match the sales target?
No. The demand plan is an unbiased estimate of what will happen; the target is a commitment used to manage performance. Both are legitimate and they answer different questions. Substituting one for the other is the most common single cause of an unreliable planning cycle.
How often should the cycle run?
Monthly is the norm and suits most businesses. What matters more than the frequency is that dates are fixed in advance and held, since a slipped review compresses everything downstream and the cadence degrades quickly once it starts moving.
Do we need dedicated software?
Not to start. Software consolidates data, generates baselines, and runs scenarios, which removes preparation effort and improves the quality of the conversation. It cannot create decision rights or enforce the calendar, so a disciplined cadence on spreadsheets beats an excellent platform without governance.
Are maturity models reliable?
Treat them as commercial frameworks. The most cited model is published by an analyst firm that sells research and takes vendor payment, and software vendors republish it while positioning their products at the upper stages. The stages are a useful vocabulary and not a neutral measurement.
Method, sources, and where to go deeper
Method
The origin and definitional material follows the professional body definition and the primary published works, with the commercial ownership of the integrated business planning label stated explicitly.
The cycle description follows the canonical formulation used across the practitioner literature, noting where organizations vary the step count without changing the sequence.
Maturity model material is attributed to the analyst firm that publishes it, with its funding model stated, rather than presented as a neutral framework.
Supply Chain Research is independent and vendor-neutral. We accept no payment from the vendors or categories covered, and this page names no products.
Caveats
SCR publishes no benchmark for the benefits of implementing this process. Percentage improvements in inventory, service, revenue, or capacity circulating in this market originate with analyst firms and planning software vendors and carry no disclosed method.
Maturity stage distributions, including claims about the share of companies stuck at lower stages, are analyst estimates rather than measured populations and should be attributed accordingly.
Integrated business planning is a term owned and promoted by a consultancy. It is not an open standard, and conformance to it cannot be assessed independently.
Step counts and review names vary between organizations and between the sources that describe them. The sequence and the handoffs are the durable content; the labels are local.
Figure 1, Table 1, and Table 2 are structural summaries rather than measured research findings.
Where to go deeper
Readers whose question concerns forecasting methods or the software that produces a statistical baseline should read the SCR guide to demand planning and forecasting software, which owns that boundary. The inventory optimization and MEIO guide covers the buffer policy decisions that the supply review depends on. The MRP versus ERP versus APS guide covers the planning engines that execute inside the frozen period. The supply chain metrics and SCOR guide covers how the resulting performance should be measured, and readers scoping across categories should start with the SCR supply chain software category map.
Sources
Sources
- Association for Supply Chain Management. Sales and operations planning and the digital supply chain. Professional body, membership funded. Cited for the definitional framing.
- Association for Supply Chain Management. SCOR Digital Standard, introduction and front matter. Professional body. Cited for the process and function distinction.
- Oliver Wight. Transitioning from sales and operations planning to integrated business planning. Interested source: the consultancy that originated the process and promotes the integrated business planning label, and which sells implementation services.
- Oliver Wight Americas. Assessment framework for sales and operations planning and integrated business planning. Interested source: the same consultancy publishing its own assessment framework.
- Demand Driven Institute. Adaptive sales and operations planning. Interested source: a body that owns and certifies a related methodology and sells training. Cited for the continuing development of the discipline.
- Gartner. Sales and operations planning maturity model. Interested source: an analyst firm that sells research and takes vendor payment. Cited to identify the origin of the maturity stages used across this market.
- Reference overview. Sales and operations planning, history and definition. Tertiary source, used for historical scaffolding only and not for any status claim.
