A configurator is a promise machine. Every time it lets a user finish a configuration, it is promising that the plant can build it, purchasing can buy it and finance can price it. The quality of a configurator is measured by how rarely it breaks that promise.
What's inside
- An option model: attributes and their allowed values.
- constraints: which combinations are allowed, required or impossible.
- Output logic: conditions that select lines from the 150% BOM, operations from the routing, and adders for the price.
- A user experience: the order of questions, defaults and the messages people see when they hit a rule.
Two styles
| Rule-based | Constraint-based | |
|---|---|---|
| How rules are written | If this, then that, in sequence | Statements that must always be true |
| Order of questions | Usually fixed | Any order |
| Strength | Easy to read and debug | Handles large option spaces gracefully |
| Risk | Gets tangled as products grow | Harder for newcomers to reason about |
The Infor LN Product Configurator (PCF), which I've worked in, sits inside ERP and generates the manufacturing BOM and routing for each order. CPQ tools usually sit in front of it, closer to the dealer.
Good configurators guide, bad ones scold
When a user picks something incompatible, a bad configurator says “invalid configuration” at the end. A good one either hides the impossible choice or changes the conflicting one and says why. The Rules Lab does the second.
Questions people ask
Is a configurator the same as CPQ?
CPQ includes configuration, but adds pricing, quoting and sales workflow. Many manufacturers run a CPQ front end for dealers and an ERP configurator behind it for manufacturing outputs.
Who maintains the rules?
Configuration analysts or engineers, working from engineering releases. It's specialised work: part data modelling, part logic, part testing.
Updated November 2026. Think I've got something wrong? Tell me.