Variant Product Configuration
Replace ERP scroll-and-guess with guided selection across size, material, rating, and finish. Reps and dealers reach the right variant without memorizing catalog codes.
Variant · session
Industrial motor line
Flat SKU list
- VM-S-230-CS-IP54-B3
- VM-S-230-CS-IP54-B5
- VM-S-400-SS-IP65-B5
- VM-M-400-SS-IP65-B5
- VM-M-480-CS-IP54-B3
- VM-L-400-SS-IP65-B5
- VM-L-480-SS-IP67-B5
- … hundreds more
Structured selection
Frame
Voltage
Material
Protection
Mount
| Frame × V | 230 | 400 | 480 |
|---|---|---|---|
| S | ● | ● | ● |
| M | ● | ● | ● |
| L | — | ● | ● |
Matrix shifts with Material = Stainless. △ = limited finish/IP path (illustrative).
What this controls
By attribute
Navigate dimensions, not thousands of SKU codes
Narrowed
Each choice filters what stays valid
Current
Discontinued variants hidden from selection
The challenge
Your catalog has variants; your sales process still has SKU soup
Variant-rich manufacturers do not sell one product. They sell size × material × voltage × finish × connection type, expressed as hundreds or thousands of valid combinations and many more invalid ones. In ERP and price books, those combinations often appear as long SKU lists with opaque codes.
Inside sales searches by partial description, calls product management, or picks the closest match. Dealers quote variant numbers from outdated spreadsheets. When the wrong enclosure material or motor frame reaches the order, someone reopens the quote days later.
Spreadsheets and PDF catalogs cannot keep pace when you launch variants, retire old ones, or regionalize a line. Training new reps means teaching catalog codes, not how the product family actually varies.
Variant complexity should widen what you can sell, not widen how long every quote takes. The friction is not missing data. It is asking humans to act as the variant filter.
How it works
How Mercura turns variant catalogs into guided selection
Mercura models each product family as attributes and valid combinations, not a flat SKU table. A rep or dealer chooses size, then material, then IP rating, then finish. After each step, only compatible options remain and price updates for that variant path. Discontinued or blocked variants drop out of the configurator when product data changes. The output is a specific variant configuration with line pricing, ready for approval and order transfer. Deep IF/THEN logic lives on the rules-based configuration page; here the focus is navigating breadth without memorizing codes.
SKU explosion
Flat list vs structured attributes
Flat SKU list
- VM-S-230-CS-IP54-B3
- VM-S-230-CS-IP54-B5
- VM-M-400-SS-IP65-B5
- VM-L-400-SS-IP65-B5
- … hundreds more SKUs
Structured selection
↓ one valid variant
VM-L-400-SS-IP65-B5
Three ways products are configured
Variant · Parametric · Modular
Variant-based
Select among predefined attribute values.
Frame / voltage / IP / mount
Parametric
Enter dimensional or engineering parameters.
Width / load / flow
Modular
Assemble reusable physical or functional modules.
Base / head / controller
Bundling is commercial packaging around products — not a fourth product-definition model.
What's included
What variant configuration covers
Attribute
- Multi-attribute modeling across size, material, rating, finish, and more
- Dynamic filtering after each attribute selection
Filter
- Variant-level pricing as combinations are built
- Discontinued or regional variants excluded automatically
Resolve
- Substitution paths when a variant is no longer sold
Output
- Bulk import of variant data from ERP or PIM
- Variant-specific datasheets on the quote output
- Same guided experience for inside sales, dealers, and self-service
The difference
Variant quoting before and after guided selection
SKU lists and catalog memory
- 01 Reps search ERP or PDF catalogs for the right code
- 02 Dealers quote retired variants from old price lists
- 03 Wrong material or rating picked on busy quotes
- 04 New variant launches require retraining, not a data update
- 05 Product management validates combinations ad hoc
With Mercura
- 01 Selection by attribute, not memorized SKU numbers
- 02 Invalid combinations disappear as choices are made
- 03 Price follows the variant path being built
- 04 Catalog changes reflected when variant data updates
- 05 Dealers and reps quote the same valid variant set
Business impact
Why variant configuration belongs in CPQ
Variant configuration is how you make catalog breadth usable for sales. ERP variant engines focus on manufacturing structures; CPQ focuses on helping reps and partners find a valid sellable combination quickly. Mercura does not replace your ERP item master. Someone still owns variant data quality and compatibility rules. For teams with large configurable catalogs, guided variant selection reduces wrong-code quotes and keeps dealers aligned with what is actually available to sell.
Business impact
Faster variant selection
Attributes replace searching flat SKU lists.
Fewer wrong-SKU choices
Each choice narrows what stays valid.
Easier large-catalog navigation
Discontinued and incompatible variants stay out of path.
Compare
Variant vs parametric
Variant
Discrete predefined values
230 V / 400 V / 480 V
Narrow a catalog of existing SKUs.
Parametric
Continuous / calculated values
4375 mm
Enter dimensions; formulas derive structure.
Configuration map
Product definition → rules orchestration → commercial packaging → valid configuration, price, and BOM
Product definition
Logic
Commercial packaging
Output
Valid configuration · Price · BOM
Resolved variant · SKU locked
See guided variant selection on a real catalog
Book a demo to walk through attribute-based configuration for a variant-rich product line.
Let’s build together.
We empower manufacturers to master product modeling, streamline quoting process, reduce errors, and ultimately deliver the tailored solutions that customers demand.