- Features > Integrations > Salesforce
Mercura CPQ + Salesforce
Configure complex products without leaving the Salesforce opportunity
Keep accounts, contacts, and pipeline in Salesforce while Mercura handles configuration logic, commercial rules, and configuration-specific quotes.
Salesforce remains the system of record for customer relationships and opportunity management. Mercura adds a dedicated configuration layer when the sellable outcome depends on options, constraints, calculated attributes, or documentation that a simple product pick list cannot express.
What Salesforce typically owns in the sales process
In manufacturer deployments, Salesforce often centralizes account hierarchies, contacts, opportunities, activities, forecasting, and partner or channel structures. That context is exactly what should feed a CPQ workflow, but it is not where deep product logic usually lives.
- Account and contact master data for the deal
- Opportunity stages, amounts, and ownership
- Price books and currency when modeled on the opportunity
- Activity history and collaboration around the deal
- Partner or territory models when used
- Commercial metadata agreed for the opportunity (terms where modeled)
Clear boundaries between Salesforce and Mercura
Salesforce
- CRM objects and sales process
- Pipeline reporting and forecasting inputs
- User access aligned to sales roles
- Non-configuration commercial fields on the opportunity
Mercura CPQ
- Guided configuration and valid combinations
- Rules, dependencies, and calculated values
- Configuration-specific pricing logic
- Visual or structured quote output
- Configuration references for downstream systems
Typical handoff after configuration
- Configuration reference or external key
- Commercial line description agreed in the integration design
- Price outcome for the configured solution
- Quote document or link when part of the process
Field mapping, direction of sync, and timing are defined per project. Mercura does not assume a single standard Salesforce CPQ data model.
Common architecture patterns (customer-specific)
Depending on the customer landscape, Mercura may be invoked from a Salesforce action, embedded experience, or parallel tab while the opportunity remains open. Designs often pass Account, Opportunity, price book, and currency context into configuration; the integration contract defines which objects receive results.
Embedded on the Opportunity (Canvas or Lightning Web Component)
Reps stay on the Opportunity record while Mercura opens in a Canvas app or Lightning Web Component. Authentication may use OAuth or SSO via a Connected App; field and product mapping is defined per project. Lightning Experience and mobile layouts are considered when scoping the UX.
Opportunity-led configuration
Sales opens or updates an opportunity in Salesforce, launches Mercura with opportunity context, completes configuration, and returns structured results to the opportunity or related custom objects.
Quote document alongside CRM
Mercura generates the technical-commercial quote while Salesforce stores the customer narrative, stage movement, and forecast. PDF or document links may be attached where the customer process requires it.
ERP remains fulfillment system of record
When an ERP carries items, costs, or orders, Mercura often sits between Salesforce and ERP: CRM context in, configured commercial outcome out, with ERP receiving manufacturing-relevant data through a separate interface.
Middleware, iPaaS, or custom services are common. Mercura exposes integration points as agreed in the project; it does not imply a shipped Salesforce AppExchange package.
Manufacturing scenarios that show up on Salesforce opportunities
Engineered-to-order lines on a standard opportunity
The opportunity lists a platform product, but the sellable outcome requires dimensions, modules, or service bundles validated against engineering rules before price is presented.
Dealer or regional sales on the same catalog
Different Salesforce accounts see different option families or price books while Mercura enforces the same underlying configuration rules.
Long-cycle deals with revisioned quotes
Multiple configuration revisions attach to one opportunity; Mercura holds configuration history while Salesforce tracks stage progression.
When Mercura alongside Salesforce is a fit
When Mercura helps
- Product logic is too complex for static price books alone
- Engineering or product management must govern options centrally
- Quotes must reflect configured BOM or specification fragments
- Sales needs guided selling without opening a separate ERP UI
When it may not be needed
- Catalog is small, fixed SKU list with list price only
- Salesforce CPQ (or another CPQ) already covers configuration with acceptable governance
- No repeatable configuration rules exist yet
Mercura vs native Salesforce CPQ in manufacturing conversations
Salesforce CPQ can cover many configure-price-quote flows, including native pricing steps on the opportunity. Mercura is discussed when configuration depth, manufacturing-oriented rules, or cross-system architecture (ERP, PIM, CAD) needs a specialized engine; some architectures use Mercura for complex configuration and keep Salesforce-native CPQ components for agreed commercial steps.
| Topic | Salesforce | Mercura |
|---|---|---|
| Primary strength | CRM process, forecasting, ecosystem | Deep configuration, rules, manufacturing quote output |
| Typical trigger | Pipeline and account management | Valid product combinations and calculated commercial data |
For implementation partners
Scope Connected App setup, object and product field mapping, Opportunity page embedding, and which Salesforce edition and objects are in play before promising timelines. Mercura configuration content is maintained in Mercura; Salesforce customization stays in Salesforce.
FAQ
Does Mercura replace Salesforce?
No. Salesforce continues to own CRM. Mercura adds configuration, pricing logic for configured outcomes, and quote generation where product complexity requires it.
Is there a standard Salesforce connector?
Projects define APIs, middleware, and field mappings case by case. Mercura does not claim a single prebuilt Salesforce connector for all customers.
Can Mercura work alongside Salesforce CPQ?
In some architectures Mercura handles complex product configuration while Salesforce CPQ or other native components remain part of pricing or quote approval. The split is defined per customer; Mercura does not assume it replaces every Salesforce CPQ function.
Why keep heavy configuration logic outside Salesforce?
Very large rule sets and frequent engineering changes can be costly to maintain entirely in CRM application logic or Apex governor limits. Mercura centralizes configuration models while Salesforce keeps accounts, opportunities, and commercial workflow.
Can configuration data flow to ERP?
Often yes in manufacturing architectures, but ERP integration is a separate design from CRM context. Many customers route configured results to ERP after commercial approval.
Where is product master data maintained?
It varies: ERP, PIM, PLM, or Mercura depending on governance. Mercura consumes the sources agreed during implementation rather than assuming one master.
Explore more connections on the integrations hub .
Book a workflow review