Rule-based logic
If/then rules, formulas, hide/show actions, and set-value constraints, chained without custom code.
Productlogica vastleggen die sales zonder code kan draaien
Als/dan-regels, lookup-tabellen en conflictoplossing. Alleen maakbare configuraties bereiken offerte en verkoop-BOM.
Regels
Als/dan, formules, tonen/verbergen
Lookups
Dimensionering, compatibiliteit, regio's
Verkoop-BOM
Bijgewerkt na elke geldige selectie
Configuration logic
Logic building blocks for every product
Combine rule types the way your products work: option dependencies, lookup tables for sizing, and attribute-driven filtering on the catalogue.
Lookup tables
Matrix lookups for sizing, compatibility, pricing tiers, and regional mappings, editable in spreadsheets or the config panel.
Attribute-based rules
Product properties and tags drive filtering, visibility, and logic so rules stay aligned with the catalogue.
Conflict resolution
When selections clash, Mercura suggests alternatives instead of blocking the user, respecting explicit choices over automatic defaults.
Bill of Materials
Every valid configuration produces a sales BOM, updated after each selection, including multi-level structures.
Needs-based questions
Guide sales reps and customers through plain-language questions that map to technically valid configurations.
Configuration lenses
Three lenses on your configuration logic
See how customer input flows through rules, how modules reuse across lines, and how the engine behaves on large product models.
Rule logic flow
Trace how needs and selections flow through rules and lookups into a validated configuration.
- Needs to rules to valid configuration
- Implicit vs explicit selections
- Paths to resolve conflicts
Product modelling
Reuse assemblies, modules, and attributes across product lines to reduce maintenance work.
- Module reuse across lines
- Shared attribute libraries
- PLM structure import
Engine at scale
Keep configuration responsive on large rule sets and deeply nested BOM structures.
- Large rule sets supported
- Modular system configuration
- Batch import for project quotes
How it works
How the Configuration Engine
fits daily quoting
The engine keeps invalid combinations out of the quote while letting sales handle routine variants without opening an engineering ticket.
Conflict resolution
When a selection breaks a rule, Mercura offers alternatives instead of stopping the session, catching errors before they reach production.
Needs-based configuration
Map customer requirements to valid configurations through guided questions. Sales and dealers do not need to read engineering drawings.
Modular complex systems
Split large systems into modules. Sales can rearrange components while the engine keeps the overall configuration valid.
Live quote updates
BOM, net prices, and visuals refresh after every selection, including multi-level bills of materials.
Configuration flow
From product model to valid configuration
Import structure from PLM where needed, maintain rules in the config panel, and validate every selection before it reaches sales or manufacturing.
Product model
Assemblies, modules and attributes
Configuration Engine
Rules, lookups and constraints
Valid output
Sales BOM Quote 3D visual ERP PLM
- Import product structure from PLM
- Rule builder for commercial and product teams
- Validation on every selection
- External calculation hooks for technical checks
What a maintained rule set changes in daily quoting
The goal is not infinite variants for their own sake. It is to keep routine deals out of engineering while blocking invalid combinations before production.
01
Invalid configs stopped in the session
Rules and conflict handling keep incompatible options out of quotes and ERP orders.
02
Routine variants without an engineering ticket
Standard configurations validate in sales; engineering sees exceptions and new product, not every deal.
03
Rules your commercial team can extend
New options, modules, and lines are added in the config panel, not as one-off spreadsheet exceptions.
Fit and limits
When the configuration engine is not the right layer
Mercura validates what sales can sell and build. It does not replace every system that touches the product.
Fixed catalogue, no dependencies
If you sell one SKU or options that never change manufacturability, a price book or simple option list is enough. Do not buy a rules engine for that.
True one-off engineered projects
If every quote is designed from scratch with no reusable modules, start with engineering process, not CPQ rules. Revisit when variants start to repeat.
ERP, PLM, or CAD as the system of record
The engine does not replace ERP execution, PLM master data, or CAD design authority. It sits on the selling path and consumes structure and costs where you connect them.
Pricing or documents alone
If the pain is only price lists or PDF templates, use the pricing engine and quote documents pages. Configuration logic is for option validity and a correct sales BOM.
Related
If your bottleneck is not “sales cannot safely configure what we build,” fix that bottleneck first.
Vraag een CPQ-demo aan