Map the journey from enquiry to order
A manufacturer may have a capable ERP and still lack a clear sales handoff. A quote waits for technical input, a revised price stays in an email, or a rep cannot see whether an order has changed. Identify the specific gap before adding a CRM module.
Map a real enquiry through qualification, specification, quote approval and the handoff to operations. For each step, record the owner, the source of information and the condition for moving forward. Include rework, substitutions and requests that are declined.
Choose the product around the requirement
Sales Cloud can be evaluated for the core customer and opportunity process. Manufacturing Cloud offers industry capabilities including sales agreements and forecasting. Salesforce describes a sales agreement as a long-term arrangement between a manufacturer and a customer for product sales.
Salesforce: sales agreements in Manufacturing Cloud
Quoting, partner access, service and rebate requirements may involve additional products, configuration or licences. Ask for the proposed product mix and the exact capability covered by each line of the quote. Do not assume one Manufacturing Cloud purchase includes every manufacturing workflow.
Salesforce: Manufacturing Cloud product resources
| Information | Question to settle before building |
|---|---|
| Product and price | Which system owns the catalogue, price rules and effective dates? |
| Inventory and availability | What may sales display, how fresh is it and who can commit stock? |
| Quote | Who approves changes and where is the accepted version recorded? |
| Order | What creates the order and how does the CRM receive its identifier and status? |
| Customer | How are account identifiers, locations and contacts matched? |
| Agreement forecast | How do planned volumes connect to actual orders and responsible owners? |
An example: a quote that needs technical approval
Illustrative workflow, not a customer result: a sales rep records the request and its required specifications. A technical reviewer checks the configuration. Pricing is retrieved from the approved source, and an exception goes to the named approver. Once the customer accepts, the agreed version moves to the order system and its status returns to the CRM.
The useful design detail is the handoff. If pricing is unavailable, the system should show that it cannot produce a confirmed quote. If a specification changes after approval, the process should make clear what needs to be reviewed again.
Scope the ERP connection before promising real-time visibility
Check the actual ERP version, available interfaces, permissions and middleware. Define direction and frequency for each update. An order-status feed may have different needs from a stock reservation or an approved price change.
- Use stable identifiers and make repeat messages safe to process.
- Show the last successful update where freshness affects a decision.
- Provide a visible exception queue with a responsible owner.
- Test delayed messages, partial failures and records that cannot be matched.
- Agree how to reconcile records after an outage and when to stop automated updates.
Some integrations are essential to the first release. Others can follow if the interim process is workable and clearly assigned. That decision should come from the workflow, not a blanket rule to integrate everything before launch.
Give dealers the access they actually need
For a dealer or distributor portal, define tasks before screens: submit a request, retrieve an approved document or check an order. Agree which accounts and locations each external user can access. Test with users from different organizations to confirm separation.
A portal should not imply inventory availability or an approved delivery date unless the underlying system can support that statement. Use clear status labels and show when an internal review is required.
Explore portals and custom software
Test an operational journey before release
Run an enquiry, a normal quote, a revised quote and a failed handoff with sales and operations together. Confirm that each team sees the information it needs and knows who handles an exception. Reconcile selected records between systems as well as checking a successful screen.
Track a baseline such as time waiting for approval, rework or unassigned requests. Agree what will be measured during the pilot. Faster quoting and better visibility are objectives to test, not outcomes guaranteed by purchasing a product.
What affects the estimate?
The estimate depends on scope, data condition, product configuration, integration access, external-user requirements and the availability of reviewers. A written delivery plan should identify those dependencies, acceptance checks, training and post-launch ownership.
Read the Salesforce implementation planning guide
Discuss your CRM requirements
Bring your current CRM, one representative process and the constraints that matter to your team. We can discuss the options and define the discovery work needed for a solution and estimate.