Rule-based logic
If/then rules, formulas, hide/show actions, and set-value constraints, chained without custom code.
Encoder la logique produit que les ventes peuvent exécuter sans code
Règles si/alors, tables de lookup, filtres d'attributs et gestion des conflits. Seules les configurations réalisables atteignent le devis et la nomenclature commerciale.
Règles
Si/alors, formules, afficher/masquer
Lookups
Dimensionnement, compatibilité, régions
Nomenclature
Mise à jour après chaque sélection valide
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
Ce qu'un jeu de règles maintenu change au quotidien
L'objectif n'est pas des variantes infinies, mais sortir la routine de l'ingénierie et bloquer les combinaisons invalides avant production.
01
Configs invalides stoppées en session
Règles et conflits tiennent les options incompatibles hors devis et commandes ERP.
02
Variantes routine sans ticket ingénierie
Les configs standard se valident en ventes ; l'ingénierie voit exceptions et nouveautés.
03
Règles extensibles par le commerce
Nouvelles options dans le panneau de config, pas comme exceptions Excel.
Demander une démonstration CPQ