- Features > Integrations > Microsoft > Add product configuration and CPQ to your Dynamics 365 Sales process
Mercura CPQ + Microsoft Dynamics 365 Sales
Add product configuration and CPQ to your Dynamics 365 Sales process
Keep accounts, contacts, and opportunities in Dynamics 365 Sales while Mercura handles guided product configuration, commercial rules, pricing, and configuration-specific quotes.
Dynamics 365 Sales continues to own accounts, contacts, opportunities, and sales activity. Mercura adds the specialized configuration layer required when selling the product depends on rules, dependencies, calculations, pricing, or documentation that goes beyond picking items from a catalog.
Microsoft partner?
When one of your manufacturing customers reaches the limits of spreadsheet-based configuration or ERP customizations, Mercura can add the commercial configuration layer without replacing the systems you already implement.
What is CPQ for Dynamics 365 Sales?
Dynamics 365 owns the customer relationship. Mercura owns product complexity.
Dynamics 365 Sales
- • Accounts
- • Contacts
- • Opportunities
- • Activities
- • Sales pipeline
- • Forecasting
- • Customer context
Mercura CPQ
- • Guided selling
- • Product selection
- • Rules and constraints
- • Dependencies
- • Calculations
- • Configuration pricing
- • Visualization
- • Documents
- • Technical configuration data
Approved outcome
- Configured lines
- Commercial description
- Price
- Configuration reference
- Quote document
- Other fields defined in the integration contract
The exact mapping depends on the data model and sales process in each Dynamics 365 environment.
When the CRM knows the customer but cannot decide how the product must be configured
Dynamics 365 Sales is strong at managing who the customer is, which opportunity is open, what sales activity has happened, and where the deal stands in the pipeline. In complex manufacturing, another layer of knowledge appears: which product fits the requirement, which options are compatible, which dimensions are valid, which accessories are mandatory, how price changes when configuration changes, what specification belongs in the proposal, and what production or ERP needs next. Mercura turns those repeatable decisions into configuration logic so sales can work with more autonomy without routing every quote through engineering.
Common architecture patterns with Dynamics 365 Sales
There is no single correct CRM + CPQ design. The right pattern depends on which system owns quoting, pricing, and downstream order execution.
A
Pattern A — CRM-led process with return to the opportunity
Dynamics 365 Sales → Mercura CPQ → Dynamics 365 Sales
A common pattern when the opportunity in Dynamics 365 Sales remains the commercial anchor. Mercura handles configuration and quote output; agreed lines, references, documents, or prices map back to the opportunity or related CRM records as defined in the project.
B
Pattern B — Dynamics 365 Sales with Business Central
Dynamics 365 Sales → Mercura CPQ → Business Central
Typical when CRM runs in Dynamics 365 Sales and operational quoting or orders continue in Microsoft Dynamics 365 Business Central. Mercura sits between customer-facing configuration and the ERP sales objects your team already uses.
C
Pattern C — Dynamics 365 Sales with Finance & Supply Chain Management
Dynamics 365 Sales → Mercura CPQ → Finance & Supply Chain Management
Common in enterprise manufacturing where opportunities live in Sales and execution moves to Microsoft Dynamics 365 Finance & Supply Chain Management. Mercura defines the sellable configuration before data crosses into ERP manufacturing and finance processes.
These are common architecture options, not a promise that every customer uses all three. Ownership of each data object is agreed during integration design.
One sales experience, even when the logic lives in several systems
Configure from opportunity context
The CPQ process can start from commercial context already in Dynamics 365 so basic customer and opportunity data does not need to be searched for or retyped.
Avoid technically invalid configurations
Mercura rules and constraints guide users through allowed combinations instead of asking sales to memorize the full product logic.
Calculate configuration pricing
Pricing can combine external sources with configuration-specific calculations. The source of truth for each price component is defined during implementation.
Generate the proposal from the same data
Structured configuration can feed commercial documents with products, options, quantities, specifications, images, and prices.
Continue the process without rebuilding the quote
After approval, agreed fields and lines can move into the next commercial step to reduce manual data entry.
How can Mercura connect with Dynamics 365 Sales?
Dynamics 365 Sales uses Microsoft Dataverse as its data platform. The integration is designed around the tables, fields, customizations, and sales process in each environment. A typical architecture may use information such as the following. Exact objects, sync direction, and ownership are defined during integration analysis.
Into Mercura
- Account
- Contact
- Opportunity
- Currency
- Commercial context
- Products or prices when applicable
Mercura calculates
- Product selection
- Options
- Rules
- Attributes
- Quantities
- Calculated values
- Configured price
- Documentation
Back to the CRM process
- Configuration reference
- Description
- Commercial lines
- Price
- Document
- Agreed fields
Dynamics 365 Sales + Mercura + ERP
In many manufacturers, the CRM is not the final step in the process. The opportunity may start in Dynamics 365 Sales, commercial configuration may happen in Mercura, and the approved result may continue to Business Central, Dynamics 365 Finance & Supply Chain Management, or another ERP. The architecture should state clearly which application is responsible for each stage.
Dynamics 365 Sales
- Account
- Opportunity
- Sales activity
Mercura CPQ
- Requirements
- Configuration
- Rules
- Price
- Quote
ERP
- Order
- Items
- Components
- Manufacturing
- Invoicing
When should a Microsoft partner bring Mercura into a project?
- Sales depends on engineering to validate standard quotes.
- Product configuration logic lives in spreadsheets.
- ERP customizations are becoming difficult to maintain.
- The customer needs guided selling in Dynamics 365 Sales.
- The customer wants dealer or customer self-service configuration.
- Pricing depends on configuration rules, not list prices alone.
- Quotes require configuration-specific documentation.
- Product complexity is decided before the ERP transaction.
Frequently asked questions
What is CPQ for Dynamics 365 Sales?
It is a configuration, pricing, and quote layer connected to the Dynamics 365 Sales process. The CRM keeps the customer relationship and opportunity; Mercura handles the logic required to turn requirements into a valid, quotable configuration.
Does Mercura replace Dynamics 365 Sales?
No. Dynamics 365 Sales remains the CRM. Mercura complements the process when selling the product requires rules, dependencies, calculations, or configuration-specific documentation.
Can Mercura use data from a Dynamics 365 opportunity?
Yes. An integration can use account and opportunity context. The exact fields depend on the Dataverse model and environment customizations.
Can configuration results return to Dynamics 365 Sales?
Yes. Mercura output can map to the agreed commercial process, for example configuration reference, lines, prices, documents, or other fields. The structure is defined in the project.
Where should prices be calculated?
That depends on architecture. Prices may come from ERP or CRM, combine with configuration logic in Mercura, or be calculated primarily in CPQ. Define a clear source of truth for each part of the price.
Can Mercura work with an ERP as well as Dynamics 365 Sales?
Yes. A common pattern connects CRM, CPQ, and ERP so opportunity, configuration, and order stay in one flow without duplicating data manually.
See how this would work in your Dynamics 365 environment
Show us a real configurable product, a typical opportunity, and how you prepare quotes today. We can use that process to show where Mercura fits and what information should be exchanged with Dynamics 365.
Request a CPQ demo