Sales shares a forecast. Operations reviews capacity. Finance checks the numbers. The problem is that these conversations happen in separate rooms, on separate schedules, with separate data. When the numbers don't reconcile, the business makes commitments it can't keep, builds inventory it doesn't need, or misses the financial targets it set three months earlier.
Sales and Operations Planning, or S&OP, is the structured process that brings those conversations into one governed cycle. It is not a software product, a forecasting algorithm, or a production schedule. It is a cross-functional decision process with defined inputs, a fixed cadence, clear ownership, and a single reconciled output: a plan the whole business can execute against.
Why the Numbers Don't Reconcile
A similar dynamic can appear inside companies, where sales protects its forecast, operations protects its capacity assumptions, and finance protects its margin model. Each function holds a version of the truth that was accurate when it was built and has drifted since.
NIST's Advanced Manufacturing Data Infrastructure and Analytics program identifies a related structural problem: turning data into meaningful intelligence is difficult, and technologies are seldom one-size-fits-all solutions. The data exists across CRM pipelines, ERP order books, MRP outputs, shop-floor work orders, and warehouse records. The challenge is not collecting it. The challenge is that no one owns the reconciled version, and no regular process forces the functions to agree on one.
The consequence is decision latency. By the time a capacity constraint surfaces in a production meeting, the sales team has already quoted a lead time that can't be met. By the time finance closes the month, the inventory variance has already happened. S&OP is the mechanism that moves those conversations upstream, before the commitments are made.
What S&OP Actually Is, and What It Is Not
It is not demand forecasting, which is the statistical or judgment-based process of estimating future customer demand. It is not Material Requirements Planning (MRP), which explodes a production plan into component and raw material needs. It is not a Master Production Schedule (MPS), which translates the aggregate plan into specific item-level production timing. It is not Advanced Planning and Scheduling (APS), which optimizes detailed sequencing across constrained resources. And it is not Integrated Business Planning (IBP), which is an extended version of S&OP that more tightly connects operational plans to financial strategy and portfolio decisions.
S&OP sits above all of those. It takes the outputs of demand review, supply review, and financial review and produces a single agreed plan that authorizes the more detailed planning layers to proceed. If the detailed layers disagree with the S&OP output, that is an escalation signal, not a reason to run parallel plans.
Each cycle moves through a defined sequence of reviews before reaching an executive decision meeting.
The demand review assembles the commercial picture: the statistical forecast, sales pipeline, customer commitments, new product launches, and any known demand events. The output is a single demand plan, not a range of scenarios that operations must guess between.
The supply review tests that demand plan against what the business can actually produce. The owner is operations or supply chain, with input from procurement and production planning.
The pre-S&OP meeting, sometimes called the reconciliation meeting, is where the gaps between demand and supply are surfaced and options are developed. This is where the real work happens: identifying whether a capacity constraint can be resolved through overtime, outsourcing, or demand shaping, and what each option costs. Finance participates here to translate the options into margin and cash flow terms.
The executive S&OP meeting is a decision meeting, not a review meeting. Its purpose is to approve the reconciled plan, resolve any gaps that the pre-S&OP meeting could not close, and authorize the business to execute. The owner is the general manager or equivalent. If the executive meeting becomes a status report, the process has lost its authority.
Reconciling the Constraints
Demand wants the highest possible service level. Operations wants the most stable production schedule. Finance wants the lowest possible inventory and the highest margin. These objectives conflict, and S&OP does not eliminate the conflict. It forces the business to make an explicit tradeoff rather than letting each function optimize independently and discover the incompatibility later.
The practical test is whether the plan is financially closed. A demand plan and a supply plan that agree on volume but produce a margin the business cannot accept are not reconciled.
The tool question is secondary to the process question, but it matters. A manufacturer running S&OP for the first time can start with spreadsheets and structured meeting templates. The discipline of the cycle matters more than the sophistication of the software. Spreadsheets become a constraint when the data preparation burden consumes more time than the decision conversation, when version control breaks down across functions, or when the planning horizon and product complexity exceed what a manual process can manage reliably.
The question is whether those modules are configured, populated with clean data, and actually used by the functions that own the inputs. An ERP with accurate demand, inventory, and capacity data can support a functional S&OP cycle. An ERP with stale or incomplete records cannot, regardless of what the module is capable of.
Specialized planning software, including APS and dedicated S&OP platforms, may add value when the business has complex multi-site capacity constraints, long and variable lead times, or a product mix that makes aggregate planning genuinely difficult. The tradeoff is implementation effort, data quality requirements, and the ongoing discipline needed to keep the planning model current. A planning tool that runs on assumptions the business no longer trusts produces a plan no one will follow.
Analytics and reporting layers, whether built on a data platform or through BI tools connected to existing systems, may help when the core problem is that the functions cannot see the same numbers at the same time. The prerequisite is that the underlying records are accurate and owned.
Where to Start
Before selecting a tool or redesigning a process, answer these questions about your current state.
Do the demand, supply, and financial plans currently agree at the end of each month, or does each function carry its own version? If they disagree, identify where the first divergence occurs in the data, not in the meeting.
Who owns the demand plan? Who owns the supply plan? If the answer is a system rather than a person, the ownership is not defined.
Is there a single meeting where the general manager approves the reconciled plan? If that meeting does not exist, the S&OP cycle does not exist yet, regardless of what the individual reviews produce.
What is the data preparation burden for each review? If the team spends most of its time assembling the numbers rather than discussing the tradeoffs, the data infrastructure is the constraint, not the process design.
Start with the process and the ownership. Define the cycle, the owners, and the decision rights before evaluating whether the current tools can support it. In many cases, the first constraint is not the software. It is the absence of a single agreed number that all functions are willing to defend.
