Salesforce ERP Demand Planning: Map Pipeline Signals to Forecasts
Updated: Oct 29
Salesforce opportunities can reveal demand before it becomes a confirmed ERP order. Connecting that pipeline context with ERP history, inventory and replenishment information can support planning. It does not turn uncertain opportunities into committed demand, and the integration must preserve that distinction.

Choose signals with a defined planning purpose
Salesforce signal | Planning question |
|---|---|
Product or configuration | Which mapped ERP items or families may be needed? |
Quantity | Is this an estimated requirement or an approved commitment? |
Expected date | Does the date represent close, order, shipment or customer need? |
Opportunity stage | Which opportunities qualify for this planning view? |
Probability | How was confidence assigned, and is it reliable enough to use? |
Map identifiers and time periods consistently
Product families, configurations and selling units may differ between CRM and ERP. Agree mappings, unit conversions, company/site context and the time buckets used in planning. A deal expected to close in November may require materials earlier and shipment later; one date should not silently stand for all three.
Prevent pipeline and order double-counting
When an opportunity becomes an ERP order, preserve the relationship between them. Decide when the forecast signal is removed, reduced or replaced by a firm requirement. Test partial orders, split deliveries, reopened opportunities and cancelled lines where those scenarios are in scope.
Separate visibility from automated action
A planning dashboard, a recommendation and an automatic procurement change have different consequences. Start with the information planners need to review. Any downstream order or production action requires supported interfaces, agreed thresholds, permissions and approvals. Do not assume that connecting the data automatically changes the ERP planning engine.
An illustrative manufacturing scenario
Several qualified opportunities show interest in one component family. Planning compares their dates and quantities with confirmed orders, inventory, supplier lead times and available capacity. The team investigates the exposure and decides whether a purchasing or production adjustment is justified. The scenario illustrates how combined context supports judgment; it is not a prediction of demand or a guaranteed operational result.
Validate forecast usefulness
Choose a forecast horizon and product level, then compare predictions with actual demand using consistent definitions. Track bias, large errors, missing mappings and stale updates. Keep early-stage interest separate from accepted orders, and record when a salesperson or planner overrides an assumption.
Scope the first planning view
Begin with one product family or operating entity and a few dependable fields. Confirm the Salesforce and ERP release, interfaces, source ownership, refresh timing and exception process. Endowance can assess how Duet360 should coordinate the agreed data and business handoffs for that environment.


Comments