Rule-based logic
If/then rules, formulas, hide/show actions, and set-value constraints, chained without custom code.
Produktlogik codieren, die der Vertrieb ohne Code nutzen kann
Wenn/dann-Regeln, Lookup-Tabellen, Attributfilter und Konfliktbehandlung machen Produktwissen zu Live-Validierung. Nur fertigbare Konfigurationen erreichen Angebot und Sales-BOM.
Regeln
Wenn/dann, Formeln, ein-/ausblenden
Lookups
Dimensionierung, Kompatibilität, Regionen
Sales-BOM
Nach jeder gültigen Auswahl aktualisiert
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
So passt die Configuration Engine
in den Tagesvertrieb
Die Engine hält ungültige Kombinationen aus dem Angebot und lässt den Vertrieb Routinevarianten ohne Engineering-Ticket bearbeiten.
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
Was ein gepflegter Regelsatz im Tagesgeschäft ändert
Ziel sind nicht endlose Varianten, sondern Routine ohne Engineering-Ticket und ungültige Kombinationen vor der Produktion.
01
Ungültige Configs in der Session gestoppt
Regeln halten inkompatible Optionen aus Angebot und ERP-Auftrag.
02
Routinevarianten ohne Engineering
Standardkonfigurationen validieren im Vertrieb; Engineering sieht Ausnahmen.
03
Regeln, die Vertrieb erweitern kann
Neue Optionen im Config-Panel, nicht als Excel-Ausnahme.
CPQ-Demo anfordern