How the S&OP Process Maps to Salesforce Manufacturing Cloud

Sales and Operations Planning —S&OP — is one of the oldest formal management processes in manufacturing. Developed in the 1980s as a way to align sales forecasts with supply chain capacity and financial targets, it has become the monthly rhythm that governs how manufacturers make decisions about production, procurement, and resource allocation.

Salesforce Manufacturing Cloud is, in large part, a system designed to support this process. But the connection between the S&OP framework and the specific objects, workflows, and configurations inside Manufacturing Cloud is rarely explained clearly. Implementation teams often configure the technology correctly while missing the process alignment entirely — which is why so many Manufacturing Cloud instances go unused in the actual S&OP cycle.

This article maps the S&OP process to Manufacturing Cloud specifically: what each phase of S&OP is, what data it requires, and how Manufacturing Cloud objects and workflows support it.

What S&OP process actually is

Sales and operations planning is a monthly management process developed in the 1980s as a way to align sales forecasts with supply chain capacity and financial targets. It has become the planning rhythm that governs how manufacturers make decisions about production, procurement, and resource allocation.

In a working S&OP cycle, demand planning, supply planning, finance, and sales meet at fixed points each month. Each function brings their view of the next 12–18 months. By the end of the cycle, those views have been reconciled into one number that everyone commits to. The output is a locked, consensus forecast that drives MRP, hiring plans, and the financial outlook the CFO presents to the board.

When the S&OP process breaks down, every downstream system inherits the failure: factories build the wrong mix, procurement carries the wrong inventory, finance misses guidance, and sales chases revenue that was never going to land in the planned period.

The 4 phases of the S&OP process

The classic S&OP process has four phases that run in sequence across the month:

Manufacturing Cloud natively supports Phases 1 and 2. It has limited direct support for Phase 3 — supply review lives in ERP and planning systems, not in Salesforce. Its contribution to Phase 4 depends heavily on how well the analytics layer has been configured.

The rest of this article walks each phase in detail and shows where Manufacturing Cloud earns its place, where it hands off, and where most implementations breakdown.

How Salesforce manufacturing cloud supports each S&OP phase

Phase 1: Data gathering — The manufacturing cloud role

Before the demand review can happen, data needs to exist in the system. This is the most infrastructure-intensive phase and where many Manufacturing Cloud implementations break down.

Actuals from ERP

The prior month's shipped revenue and volume need to be loaded into Account Forecast Period actuals fields and Sales Agreement Product Schedule actuals fields. Without this, there is no basis for accuracy measurement, trend analysis, or the actuals-versus-forecast comparison that opens every demand review.

This integration is almost always built via middleware — MuleSoft, Boomi, Informatica, or a custom API layer. The nightly batch job pulls shipped invoices from SAP or Oracle and writes to Salesforce. The critical architectural decision: should actuals load at the account level, the product family level, or the SKU level? The answer determines which Manufacturing Cloud records need to be created and how the data model is structured. (For the full setup walkthrough, see our Salesforce Manufacturing Cloud setup guide.)

Distributor POS data

Distributors need to submit their point-of-sale data before the demand review. This data — what they sold to their customers in the prior period — is the leading indicator of actual end-market demand, as distinct from the manufacturer's sell-in.

In Manufacturing Cloud, distributor POS data lands as inputs to Account Forecast Period records or through a custom staging object depending on implementation design. Experience Cloud portals allow distributors to submit this data directly. File-based upload (via Data Loader or custom import) is the alternative for distributors not setup on the portal.

Timing matters. If POS data is not in the system by the time the sales team begins their Week 2 adjustments, those adjustments happen without the full picture. Best practice is to set a submission deadline for distributors and monitor compliance through a coverage dashboard. 

Pipeline and design win updates

Design wins from Sales Cloud opportunities need to be reflected in Account Forecasts before the demand review. If a rep closed a design win last month that will generate revenue starting in Q3, that information needs to be in the system — either as an adjustment to the Account Forecast Period or as a structured upside entry.

The cleanest architecture links closed-won design win opportunities in Sales Cloud to Account Forecast Period records through a custom relationship or a Flow automation that prompts the rep to update their forecast after a design win is confirmed. Without this link, design win intelligence stays in opportunity records and never reaches the demand plan. 

Phase 2: Demand review — The core manufacturing cloud workflow

The demand review is where Manufacturing Cloud earns its place. It is the structured process of building the consensus demand plan account by account, product family by product family, informed by distributor data, sales intelligence, and historical actuals. This is also where S&OP demand planning as a discipline either succeeds or quietly collapses back to spreadsheets. 

The bottom-up build

The demand review starts from the bottom: individual accounts, individual product families, individual planning periods. Each sales rep or demand planner reviews the Account Forecast Periods for their accounts — the baseline derived from agreements, distributor inputs, and prior period actuals — and applies their adjustments.

This is where the UX of Manufacturing Cloud matters enormously. A rep responsible for 30 accounts with 6 product families each, reviewing a 12-month horizon, is looking at 2,160 individual forecast period records. The standard Salesforce interface presents these one record at a time. The adjustment step — which is supposed to take a morning — becomes an all-week exercise, or it does not happen at all.

Best-practice implementations address this by ensuring reps have access to grid-style views that allow them to see multiple accounts and periods simultaneously. Some teams use CRM Analytics to build a demand review dashboard where reps can see their full portfolio at a glance before drilling into specific adjustments. Others use third-party tools that provide a spreadsheet-style interface over Manufacturing Cloud data.

The  demand review workflow — review, adjust, document rationale — is  well-supported by the Manufacturing Cloud data model. The challenge is  accessing that data efficiently enough for the process to run on schedule. 

Tracking adjustments and rationale

One of the most valuable things a demand review process produces is a record of adjustments and why they were made. Why did the rep adjust the Q4 forecast up by $300K? Was it a design win ramping? A stocking order they expect from a key distributor? Customer commentary from a recent QBR?

Account Forecast Periods include an Adjustment Notes field that captures this context. Disciplined use of this field turns the forecast into an auditable record — not just numbers, but the reasoning behind them. When the forecast misses, you can trace back to which adjustments were wrong and why, which is the foundation of forecast accuracy improvement.

Process discipline here requires more than a configured field. It requires a check in the demand review process: no adjustment gets locked without a note. This is a business process requirement, not a Salesforce configuration.  

Rollup and gap analysis

Once individual account adjustments are complete, demand planning teams need to see the aggregated picture. How does the bottom-up demand plan compare to the account manager targets set by leadership? Where are the gaps — accounts or product families where the forecast falls significantly short of or significantly above plan?

Manufacturing Cloud supports this through rollup views of Account Forecasts and comparison against Account Manager Target records. In practice, the most useful gap analysis views are built in CRM Analytics or custom reports, not in the standard Account Forecast list view.

The output of the demand review is a consolidated demand plan — a single set of Account Forecast Period records that represent the consensus view of expected demand for the planning horizon. This is the document the supply chain will plan against. 

This is where the process often slows down: Salesforce has the right records, but teams still need a faster way to review and adjust high-volume forecast data.

Phase 3: Supply review — Where manufacturing cloud hands off

The supply review is where demand meets capacity. The demand plan output from Phase 2 is compared against what the factory can actually produce, what materials can be procured, and what lead times allow.

This phase lives primarily in ERP and supply chain planning systems, not in Salesforce. MRP (Material Requirements Planning) runs against the demand signal. Capacity planning tools model production constraints. Procurement teams assess lead times and component availability.

Manufacturing Cloud's role in Phase 3 is as a data source, not a workflow tool. The demand plan data —Account Forecast Periods, Sales Agreement Schedules — needs to be accessible to the supply planning tools. This typically means either direct integration(Manufacturing Cloud API to planning system) or export to a format the planning system can consume.

The supply review produces two outputs relevant to Manufacturing Cloud: an allocation plan (which accounts can be fully served versus which need to be cut back) and a production commitment (what will actually be built in the planning horizon). Both feed back into Manufacturing Cloud as adjustments — some Account Forecast Period values get revised down to reflect allocation, and Sales Agreement Schedules may be updated to reflect confirmed production commitments. 

Phase 4: Executive S&OP — The analytics layer

The executive S&OP meeting is a decision-making forum, not a data review. The CFO, VP of Supply Chain, and VP of Sales should walk in with a pre-read dashboard that shows them the plan, the risks, and the decisions that need to be made. The meeting is for resolving trade-offs, not for reading spreadsheets aloud.

This is where the CRM Analytics layer of Manufacturing Cloud becomes critical. The executive S&OP dashboard should show:

• Demand vs. supply gap by product line: Where demand exceeds confirmed production, and by how much.
• ‍Forecast accuracy trend: How accurate was last month's forecast? Is accuracy improving or degrading? MAPE by region or product family.
• ‍Top risk accounts: Accounts where the forecast has changed significantly from last month, or where actuals are trending significantly below plan.
• Revenue bridge: How does this month's plan compare to last month's plan, and what drove the change? Design wins, allocation cuts, distributor adjustments.
• Scenario comparison: Upside scenario versus committed scenario versus prior plan.

Building these views requires CRM Analytics and clean underlying data. The accuracy of what appears in the executive S&OP dashboard is a direct function of how well the Phases 1–3 data inputs were managed.

The executive S&OP meeting is where Manufacturing Cloud either proves its value or loses it. If the dashboard shows accurate, timely data and drives  better decisions than the previous spreadsheet-based process, the system earns its place. If the dashboard is incomplete or months behind actual,  leadership goes back to their own spreadsheets and the S&OP cycle never  fully migrates to Salesforce. 

S&OP vs. IBP: What's the difference?

Anyone working on S&OP in Salesforce will eventually run into Integrated Business Planning (IBP) — and the two terms are often used interchangeably, which is a mistake.

For Manufacturing Cloud purposes, the practical difference is which Forecast Set structure you build. An S&OP-aligned implementation typically uses one operational Forecast Set with a 12–18 month rolling horizon. An IBP-aligned implementation usually adds a second Forecast Set with a longer horizon and tighter Finance integration — sometimes in CRM Analytics, sometimes through a connected Excel layer that lets FP&A model scenarios against live forecast data. (The Finance adoption challenge is covered in detail in our analysis of Salesforce adoption in finance teams.)

If the company calls their process IBP, do not assume Manufacturing Cloud is the only system involved — IBP almost always implies a tighter dependency on a financial planning tool than pure S&OP does.

The full S&OP-to-manufacturing cloud mapping

Configuration decisions that affect S&OP alignment

Several Manufacturing Cloud configuration decisions have outsized impact on S&OP process alignment and should be made with the process in mind:

Forecast set structure

The Forecast Set defines the planning horizon, period granularity (monthly vs. weekly), and product family scope. A common mistake is creating a single Forecast Set that tries to serve all purposes — the 18-month rolling demand plan, the 3-month near-term operational plan, and the annual financial plan. These often have different period structures, different locking rules, and different user populations. Separate Forecast Sets for each planning horizon reduces complexity.

Lock rules and approval workflows

S&OP has formal lock points— when the demand review closes, when the supply plan is finalized, when the executive plan is approved. Manufacturing Cloud Forecast Set configurations should reflect these lock points. A Flow automation that locks Account Forecast Period records after the demand review closes prevents late adjustments that were not part of the formal process.

Period granularity

Monthly periods work for most S&OP processes. Weekly periods create a data volume problem quickly — 52 periods per account per year versus 12. Unless the business genuinely needs weekly visibility in the S&OP cycle, monthly is the right configuration.

Actuals load timing

ERP actuals need to be in the system before the demand review opens. If the actuals integration runs on a monthly batch schedule and the demand review starts on the 5th, the integration needs to complete by the 4th. Build the integration schedule around the S&OP calendar, not the other way around.

Frequently asked questions

What is the S&OP process?

The S&OP process — sales and operations planning — is a monthly management cycle that aligns demand forecasts, supply capacity, and financial plans into a single agreed view of the business. It runs in four phases: data gathering, demand review, supply review, and executive review. The output is a locked consensus forecast that drives production, procurement, hiring, and financial guidance.

What are the 4 phases of the S&OP process?

‍The four phases are: (1) data gathering and cleansing — collecting actuals, distributor data, and pipeline updates; (2) demand review — building the bottom-up demand plan; (3) supply review — comparing demand to capacity and identifying gaps; (4) executive S&OP — reconciling trade-offs and locking the plan. Salesforce Manufacturing Cloud natively supports phases 1 and 2; phase 3 lives in ERP and supply planning systems; phase 4 is a CRM Analytics layer.

What is S&OP in supply chain?

In a supply chain context, S&OP is the formal process for converting a demand forecast into a feasible production and procurement plan. It is where the sell-side view (what we expect to sell) meets the supply-side view (what we can actually build and ship), and where allocation decisions are made when demand exceeds supply.

Whatis the difference between S&OP and IBP?

‍S&OP is a monthly operational planning process focused on a 12–18 month horizon. IBP — integrated business planning — is the broader evolution: longer horizon, explicit financial scenario modeling, and strategic planning integrated alongside demand-supply reconciliation. IBP is what S&OP becomes when finance is a first-class participant rather than a downstream consumer.

How does Salesforce Manufacturing Cloud support the S&OP process?

Manufacturing Cloud supports S&OP through three primary objects: Sales Agreements (the long-term commercial commitments), Account Forecasts and Account Forecast Periods (the working demand plan), and Account Manager Targets (the top-down view). Add CRM Analytics for the executive layer and Experience Cloud for distributor data collection, and the platform covers most of the S&OP cycle natively. Phase 3 — the supply review — still happens in ERP and dedicated supply planning tools.

Final thoughts

S&OP is not a technology challenge — it is a process challenge that technology can either support or undermine. Manufacturing Cloud, configured and integrated correctly, can be a genuine S&OP enabler: faster data consolidation, transparent adjustment tracking, accountable forecasts, and executive dashboards that drive better decisions. Configured without the S&OP process in mind, it becomes an expensive data entry system that runs parallel to the spreadsheets that actually run the business.

The mapping exercise — aligningeach phase of the S&OP cycle to specific Manufacturing Cloud configurationsand workflows — is the most valuable design activity in any implementation. Itshould happen before any configuration begins.

‍

‍