ERP master data
Business Central
- Items
- Customers
- Pricing
- Inventory
- Manufacturing
- Features > Integrations > CPQ for Microsoft Dynamics 365 Business Central
Mercura + Microsoft Dynamics 365 Business Central
CPQ for Microsoft Dynamics 365 Business Central
Configure complex products, calculate pricing, generate quotes and transfer approved configurations to Business Central.
Mercura adds configuration, pricing and quote automation to your Business Central sales process — without replacing Business Central as your ERP.
Dynamics 365 Business Central Demo data
Sales Quote
- Customer
- Nordic Manufacturing A/S
- Sales Quote
- SQ-104872
- Configured item
- CoWelder Combi
- Amount
- €85,113.00
Business Central runs your ERP processes. Mercura handles product configuration.
Configure · Price · Quote
Mercura
- Guided selling
- Rules
- Pricing logic
- Visualization
- Quote generation
Sales and manufacturing data
Business Central
- Sales quote
- Sales order
- BOM / production data
Business Central remains your core ERP system. Mercura adds the configuration layer required before a correct quote or order can be created.
See Mercura working with Business Central
Watch a real Mercura CPQ workflow connected with Microsoft Dynamics 365 Business Central.
See how configuration and sales data move from Mercura into the Business Central sales process without manually recreating the configuration in ERP.
Watch on YouTube if the embed does not load →
Configure
Guide the salesperson through valid product choices and configuration rules.
Quote
Calculate the commercial result and generate customer-ready sales documents from the same configuration.
Business Central
Transfer the approved result into the agreed Business Central sales workflow.
CPQ does not have to live inside Business Central
Airmaster uses a dedicated product configurator powered by Mercura. Customers can configure ventilation products through a branded frontend while product rules, calculations and quote logic run in Mercura.
-
Guided configuration
Only relevant and valid choices are presented.
-
Real-time rules & pricing
Configuration logic reacts as selections change.
-
Customer-facing experience
The interface can live on the web, in a portal or in another custom application.
Turn the configuration into customer-ready sales documents
The same structured configuration used to calculate the product can populate customer-ready quote documents — with configured items, article numbers, quantities, prices, descriptions and technical data.
- Configured items and article numbers
- Quantities and line pricing
- Customer-facing descriptions
- Technical specification data
- Branded PDF or Word output
Send the approved configuration to Business Central
The approved Mercura configuration can be mapped into Microsoft Dynamics 365 Business Central through standard APIs and custom AL APIs where company-specific data is required.
- Customer: Linked Business Central customer
- Sales quote / order: Created from approved configuration
- Configured line items: Items, quantities and prices
- Configuration reference: Traceability back to Mercura
What Mercura adds to Business Central
Technical reference
What data can Business Central and Mercura exchange?
The integration is designed around your Business Central environment. A typical architecture may look like this:
| Data | Direction | BC integration | Purpose |
|---|---|---|---|
| Items | Business Central → Mercura | Standard API (Item) | Reuse ERP item master data |
| Customers | Business Central → Mercura | Standard API (Customer) | Customer-specific configuration and pricing |
| Units of measure | Business Central → Mercura | Standard API | Consistent product quantities |
| Standard prices | Business Central → Mercura | Standard API / price lists | Use ERP pricing as an input |
| Inventory information | Business Central → Mercura | Standard API | Display relevant availability where required |
| Configuration | Mercura → Business Central | Field mapping / custom API | Preserve configuration information |
| Quote lines | Mercura → Business Central | Standard API (Sales quote line) | Transfer configured quote lines |
| Sales quote | Mercura → Business Central | Standard API (Sales quote) | Continue quotation workflow in ERP |
| Sales order | Mercura → Business Central | Standard API (Sales order) | Transfer approved order information |
| Components/BOM data | Mercura → Business Central | Standard or custom API | Support configure-to-order manufacturing |
| Technical values | Mercura → Business Central | Custom API where required | Transfer configuration-specific attributes |
Standard + custom APIs
Manufacturing companies often extend Business Central with custom fields, AL extensions and company-specific tables. Mercura integrates with your environment — not a theoretical standard database.
During the technical analysis we identify which data is already available through Microsoft APIs, which requires a custom API, and exactly what should return to Business Central.
Microsoft Entra authentication
For Business Central Online, Microsoft supports service-to-service authentication for external applications using Microsoft Entra application identities — so integrations can use OAuth rather than employee accounts for unattended system-to-system communication.
How does pricing work with Business Central CPQ?
Pricing can remain in Business Central, be split between Business Central and Mercura, or be calculated entirely in Mercura. There is no universal answer — the correct architecture depends on where your commercial logic lives today.
Option 1 — Business Central owns pricing
Business Central remains the pricing master. Mercura retrieves the relevant price and uses it during configuration.
Best when: Your ERP already produces the required prices and CPQ mainly solves product configuration.
Option 2 — Business Central provides base prices
Business Central provides basic item/customer pricing. Mercura calculates configuration-specific additions (base machine + width surcharge + material factor + motor upgrade + control package + accessories = configured price).
Best when: Standard items have established ERP pricing but options and dimensions introduce additional pricing logic.
Option 3 — Mercura calculates the complete configured price
Mercura owns the CPQ pricing model and transfers the resulting price to Business Central.
Best when: Pricing depends heavily on dimensions, formulas, product relationships, customer-specific logic, engineering values and configuration attributes.
Connect sales configuration with Business Central manufacturing
For configure-to-order manufacturers, a correct quote is only the beginning. Production needs to know what to build.
Microsoft Business Central uses production BOMs to define components required for manufactured products and routings to define the operations required to produce them.
Pattern 1 — Existing item and BOM
Mercura determines which existing Business Central product/BOM corresponds to the configuration.
Best suited when: The set of manufacturable variants is already represented in ERP.
Pattern 2 — Base item + configuration
A base item exists in Business Central. Mercura adds the configuration-specific information required to manufacture the customer's version.
Best suited when: You do not want a separate ERP item for every theoretical combination.
Pattern 3 — Configuration-generated component structure
Mercura calculates which components and quantities are required from the customer's selections. The resulting structure is transferred into the agreed Business Central manufacturing flow.
Best suited when: The BOM genuinely changes based on the configuration.
Pattern 4 — CPQ → engineering → Business Central
Mercura determines the commercial configuration. Structured parameters are passed to engineering or CAD. The resulting technical data can then be used to create or update the final manufacturing structure in Business Central.
Best suited when: Every order still requires an engineering step, but CPQ can automate the repeatable portion of the process.
Technical reference
Technical reference
For Business Central architects, implementation partners and technical evaluators.
Understanding CPQ for Business Central
What is CPQ for Business Central?
CPQ for Business Central connects the process of configuring, pricing and quoting complex products with Microsoft Dynamics 365 Business Central.
Business Central manages core ERP processes such as item master data, customers, sales documents, inventory, financials and manufacturing.
Mercura handles the complexity that happens before a correct order can be created:
The result is a sales process where the salesperson does not need to manually translate customer requirements into ERP data.
When does Business Central need a CPQ layer?
You probably do not need dedicated CPQ software if salespeople mainly select standard items, quantities and prices from an existing Business Central catalogue.
CPQ becomes valuable when creating the correct quote or order requires knowledge that cannot easily be represented as simple item selection.
Engineering dependency. Sales needs engineering to determine the correct product, options, components or dimensions for each customer requirement. Reusable product knowledge becomes configuration rules so repeatable engineering decisions happen automatically during sales.
Configuration complexity. Too many valid combinations exist for simple ERP item selection. Model the rules that define a valid product and calculate the correct commercial or manufacturing output from the selected configuration.
Complex pricing. Final price depends on dimensions, materials, components, customer agreements, margins and calculated values — often spread across ERP and spreadsheets. Business Central pricing can feed CPQ while configuration-specific logic is calculated during the sales process.
Manual quoting and visual selling. Quotes are assembled manually across Business Central, Excel, Word and email — while ERP item numbers give customers little visual context. Generate customer-ready quotations from the same structured configuration, with images, drawings or interactive 3D where it helps the sale.
Business Central remains your ERP. Mercura handles complex selling.
A strong CPQ architecture does not duplicate an ERP. Each system should have a clearly defined responsibility.
There is no requirement that every implementation follows the same architecture. The correct design depends on where your product and commercial logic lives today.
Real configuration example
Customer requirement
Example based on a real configurable welding robot implemented in Mercura (Migatronic CoWelder). The buyer selects from:
Configurator: Basic / Track / 360 / Combi
Hardware: Robot arm, welding machine, table system
Software: Sequence, MigaJob control, DUO Plus, Offset
Accessories: Wear parts, tooling packages
Services: Training and commissioning packages
Mercura guides the configuration
Example rule logic based on the CoWelder configuration structure (Migatronic case study):
IF Combi is selected THEN both MIG/MAG and TIG welding paths become available.
IF a larger table system is selected THEN compatible robot reach options update.
IF Offset software is added THEN engineering and pricing adjust automatically.
The salesperson does not need to remember these relationships. The configurator does.
Mercura calculates the result
Commercial result: configured price, cost, margin, discount, descriptions, customer-facing specification.
Technical data: selected components, dimensions, option values, calculated quantities, configuration ID, BOM information, technical attributes.
Mercura generates the quote
The same structured configuration can populate prices, specifications, images, technical values, optional products and commercial terms into the required quotation template.
Business Central receives the approved result
The agreed data is transferred into Business Central. Depending on the architecture, this could include sales quote, sales order, item lines, configuration reference, calculated dimensions, selected components and manufacturing data.
Configure once. Reuse the configuration throughout the process.
Implementation methodology
Select one real configurable product. Choose a representative product family. Provide product data, available options, configuration rules, pricing, an example quotation, Business Central item structure and expected ERP data.
Map the current process. Determine who configures the product today, what information they need, where pricing happens, where engineering becomes involved, what is entered into Business Central and what production ultimately needs.
Define system ownership. For every relevant piece of data, decide whether Business Central, Mercura or a calculated/shared model owns it — including items, customers, prices, costs, configuration attributes, components, documents and orders.
Define the API contract. Identify standard and custom Business Central endpoints, Mercura endpoints, authentication, data direction, sync behaviour and error handling.
Build the product model. Configure products, options, attributes, rules, constraints, formulas, pricing, documents and visualization.
Validate against historical orders. Take actual customer quotations that were previously created manually. Run the same requirements through Mercura and compare configuration, price, selected products, quantities, documents and Business Central output before automating.
Go live with a bounded scope. Start with one product family or sales workflow, then extend the same architecture after the integration and product model have been proven.
Not every object required by a manufacturer should be presented as a standard plug-and-play Business Central endpoint.
Custom fields, manufacturing structures, extensions and company-specific tables often require additional integration design. Where the required information is not available through Microsoft's standard APIs, Business Central supports building custom APIs in AL.
That is why Mercura integration projects begin with data mapping, not assumptions.
Business Central-native configurator
Experlogix, Insight Works and similar ERP-centric tools
Best when:
- • Configuration is relatively straightforward.
- • Most users work directly in Business Central.
- • Frontend flexibility is not important.
- • Keeping the experience entirely ERP-centric is the priority.
Mercura CPQ
Best when:
- • Configuration is complex.
- • Sales needs guided selling.
- • Customers or dealers configure products.
- • Visualization matters.
- • Advanced calculations are needed.
- • Multiple systems are involved.
If a simpler Business Central-native configurator is a better fit for your requirements, we would rather identify that during the initial analysis than implement unnecessary CPQ software.
Frequently asked questions
What is CPQ for Business Central?
CPQ for Business Central connects complex product configuration, pricing and quote creation with Microsoft Dynamics 365 Business Central. A CPQ platform guides the user through valid product configuration, calculates the commercial result and creates quotation data before sending the relevant information to Business Central.
Does Mercura integrate with Microsoft Dynamics 365 Business Central?
Yes. Mercura can exchange data with Business Central through Business Central APIs. The exact integration depends on your Business Central data model, extensions, pricing setup and desired sales/manufacturing workflow.
Does Mercura replace Business Central?
No. Mercura is a CPQ platform. Business Central can continue to manage ERP processes including item master data, customers, sales documents, inventory, financials and manufacturing. Mercura handles the product configuration and commercial logic required before or during the creation of those transactions.
Can Business Central remain our product master?
Yes. A common architecture is for Business Central to remain your ERP system of record for item data while Mercura maintains the configuration logic. The exact ownership is defined during implementation.
Can Mercura read Business Central items?
Yes. Business Central exposes item data through its REST API.
See Microsoft's Item API reference →Can Mercura create a Business Central sales quote?
Business Central exposes sales quote and sales quote line APIs. A Mercura configuration can be mapped into the relevant Business Central quote structure when this is the selected workflow.
See Microsoft's Sales Quote API reference →Can Mercura create a Business Central sales order?
Yes. Business Central provides API operations for creating sales orders. The resulting Mercura configuration can be mapped to a Business Central sales order according to the agreed data model.
See Microsoft's Sales Order API documentation →Can Mercura use custom Business Central fields?
Yes, but custom data requires explicit integration design. Microsoft's standard APIs expose predefined schemas. If information outside the standard API needs to be exposed, a custom API can be created in AL.
Read Microsoft's API documentation →Can Mercura generate BOMs for Business Central?
Mercura can calculate the items, components and quantities required by a configuration. How that structure is transferred to Business Central depends on your manufacturing architecture — some implementations select existing BOMs, others generate configuration-specific structures, others pass parameters through engineering before the final manufacturing structure is created.
Can pricing remain in Business Central?
Yes. Business Central can own the final price, provide base prices to Mercura, or receive a configured price calculated by Mercura. The pricing architecture should have one clearly defined source of truth for each part of the calculation.
Can users configure products without logging into Business Central?
Yes. Mercura can provide configuration experiences for internal salespeople, dealers, distributors, customers and custom applications while synchronizing the resulting configuration with Business Central.
How is Business Central authentication handled?
For Business Central Online, Microsoft supports service-to-service authentication for external applications using Microsoft Entra application identities.
See Microsoft's service-to-service authentication documentation →Does Mercura work with Business Central Online?
Yes. The integration can use Microsoft's Business Central Online API architecture.
How long does a Business Central CPQ implementation take?
The Business Central API connection is only one part of the project. Scope is usually driven by the number of configurable product families, product complexity, pricing complexity, document and visualization requirements, Business Central customizations and manufacturing output. Mercura scopes implementations around a real configurable product and quotation workflow rather than quoting a generic implementation duration.
Official Business Central resources
See how CPQ could work with your Business Central setup
You do not need another generic CPQ presentation. Show us one real configurable product and how the corresponding quote or order is handled in Business Central today. We can then demonstrate how the same process could work with Mercura.
Request a CPQ demo