Rule-based logic
If/then rules, formulas, hide/show actions, and set-value constraints, chained without custom code.
Koda produktlogik som sälj kan köra utan kod
Om/så-regler, uppslagstabeller och konflikthantering. Endast byggbara konfigurationer når offert och försäljnings-BOM.
Regler
Om/så, formler, visa/dölj
Uppslag
Dimensionering, kompatibilitet, regioner
0 kod
Regler som ditt team självt underhåller
Konfigurationslogik
Logikbyggstenar för varje produkt
Kombinera regeltyper som dina produkter faktiskt fungerar efter — från enkla optionsberoenden till flerdimensionella uppslagstabeller och attributbaserad filtrering.
Lookup tables
Matrix lookups for sizing, compatibility, pricing tiers, and regional mappings, editable in spreadsheets or the config panel.
Attributbaserade regler
Produktegenskaper och taggar styr filtrering, synlighet och logik — i linje med din produktkatalog.
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.
Konfigurationsperspektiv
Tre perspektiv på din konfigurationslogik
Förstå hur regler hänger ihop, hur moduler återanvänds och hur motorn förblir snabb när komplexiteten ökar.
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
Så fungerar det
Hur Mercuras konfigurationsmotor
skapar värde
Gör produktkomplexitet från en försäljningsflaskhals till en konkurrensfördel — med logik som ditt team självt styr.
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.
Konfigurationsflöde
Från produktmodell till giltig konfiguration
Importera din produktstruktur från PLM, definiera regler i konfigurationspanelen och låt motorn validera varje val innan det når försäljning eller produktion.
Produktmodell
Sammansättningar, moduler & attribut
Konfigurationsmotor
Regler, uppslag & konfliktlösning
Giltigt resultat
Sales BOM Quote 3D visual ERP PLM
- Importera produktstruktur från ditt PLM-system
- Regelredigerare utan kod för verksamhetsanvändare
- Realtidsvalidering vid varje val
- Externa beräkningar för teknisk validering
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
Skalbar produktportfölj
Lägg till nya val, moduler och produktlinjer utan att skriva om kod — regler och uppslag växer med din katalog.
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.
Boka en CPQ-demo