Why the ERP is not enough for the commercial side
An ERP records orders after they exist. It is rarely the place where a sales team tracks an opportunity for months, where a distributor registers a deal, or where a service manager sees every machine a customer owns. Salesforce complements the ERP by covering the front of the process: pipeline, quotes, partner collaboration, and service history, then passing confirmed orders to the ERP for fulfillment.
The line between the two systems is the first design decision. Customer and product masters usually originate in the ERP, while opportunities, quotes, and cases originate in Salesforce.
Dealer and distributor portals
Channel partners want to check order status, register leads, find documentation, and place orders without calling a rep. Experience Cloud lets you give each partner a branded portal with access to only their data. Partner onboarding, deal registration, and lead distribution can follow rules that reflect territory and performance.
- Give partners self-service order status and product documentation to reduce calls.
- Use deal registration to protect partner effort and avoid channel conflict.
- Show partners their own performance against targets so conversations are fact-based.
Configured quotes and sales agreements
Products that can be configured need quoting rules so reps cannot promise combinations that cannot be built. Configure-price-quote tooling enforces compatibility and pricing, and approvals handle discounts. For long-term customers with planned volumes, sales agreements record the commitment and track actuals against it, which gives both sides a basis for forecasting and rebates.
Revenue and pricing solutions →Forecasting that reflects how manufacturers sell
A manufacturer's forecast depends on recurring orders and agreed volumes more than on one-time deals. Account-based forecasting uses the expected quantities from existing customers, adjusted for known changes, to produce a projection that production planners can trust. Compare the forecast with actual shipments from the ERP regularly and use the differences to refine it.
Service, warranty and the installed base
After the sale, customers expect fast repairs. Track each machine as an asset linked to the customer, with warranty dates, service contracts, and history of cases and work. Field Service adds scheduling and mobile tools for technicians, while knowledge articles reduce repeat calls for common issues. The installed-base view also reveals sales opportunities: ageing equipment, expiring warranties, and parts that wear on a schedule.
Salesforce Field Service →A realistic first 90 days
- Days 1 to 30. Map the customer, partner, and product data you have, decide which system owns each record, and clean the account hierarchy for your top customers.
- Days 31 to 60. Launch the core sales process for one region or product line, connect the ERP for customers and orders, and build the first forecast view.
- Days 61 to 90. Pilot the partner portal with a few distributors and bring asset and case history into the service console.
Decisions to settle before configuration starts
- Who owns the customer master? Decide whether accounts originate in the ERP or in Salesforce, and how new customers are created without duplicates.
- How are discounts governed? Set approval thresholds by margin or by deal size so sales speed and pricing discipline are both protected.
- What counts as a partner-sourced deal? Write the rule for attribution before the portal launches, or disputes will arrive with the first commission cycle.
- Which service levels apply to which customers? Tie response and repair targets to contracts so the service team does not decide case by case.
Pitfalls manufacturers meet
- Duplicating the ERP. Recreating inventory or production data in Salesforce creates two versions of the truth. Show it, do not own it.
- Overcomplicated product models. A product catalog with thousands of combinations is hard to maintain. Model options with rules instead of listing every variant.
- Ignoring distributor adoption. A portal nobody uses is wasted. Involve a few partners in design and offer a clear benefit, such as faster order status.
- Reps working in spreadsheets. If the pipeline lives elsewhere, forecasts will not be believed. Make Salesforce the only place deals are reviewed.
