Features > Parametric Product Configuration
Configuration

Parametric Product Configuration

When the customer sends millimetres and kilograms, not a catalog code, quote from formulas. Sales engineers stop owning every dimension change in Excel.

Parametric · session

Industrial enclosure / platform

Illustrative formulas
Width 4200 mm · valid range 1000–8000 · VALID

Derived outputs

Support posts3
Panel typeP-120
BeamB-240
Fastener kitFK-8
Price + BOM€7,630

What this controls

By formula

Price and BOM follow the parameters entered

Range-checked

Min and max validated before the quote leaves

Derived

Components selected from engineering formulas

The challenge

The quote lives in a sales engineer's spreadsheet, not in your CPQ

A dealer emails length 12.4 m, load 850 kg, belt type X. There is no SKU for that exact combination. Someone opens a personal workbook, pastes the numbers, and waits for formulas to spit out price and parts. That someone is usually the same sales engineer every busy week.

Inside sales cannot finish the loop. Channel partners escalate any non-step size. When the customer shortens the run by half a metre, the whole Excel path restarts, and approval waits on a new PDF that still has no shared audit trail.

Option-list CPQ and variant pickers do not solve this. You cannot pre-list every millimetre. Teams either invent fake size steps that production ignores, or they keep parametric quoting outside the system that owns price and approval.

Inquiry to configuration to price to approval to order breaks at the spreadsheet. The product knowledge exists. It is trapped in cells only one person trusts.

How it works

Four steps from parameters to a priced path

1) Product publishes numeric inputs with units and allowed ranges. 2) A rep or dealer enters length, load, flow, or capacity in the configurator. 3) Mercura validates bounds, derives components and BOM lines from the same formulas engineering signed off, and recalculates line price. 4) The configuration moves into approval and order transfer with the parametric values attached. Discrete catalog browsing is the variant page. IF/THEN option logic is rules-based configuration. This page is continuous inputs that calculate a sellable result without a private workbook.

Derivation

Inputs → formulas → derived components

Width 4200 · Height 2800 · Load 1200
↓
Formulas + constraints
↓
Supports 4 · Panel P-120 · Beam B-240 · FK-8
↓
Price + BOM

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 you put in the parametric model

Input

  • Numeric fields for dimensions, capacities, flow, load, and similar inputs
  • Min/max and unit checks with clear guidance when a value is out of range

Calculate

  • Formula-based price from the live parameter set

Validate

  • Derived components and BOM lines from engineering formulas

Derive

  • Mixed checks that combine parameters with discrete options
  • One parametric model for inside sales, dealers, and self-service
  • Parametric values written into quote documents and ERP-ready fields
  • Hybrid CTO / ETO lines alongside rules and constraints

The difference

What changes when formulas leave Excel

Personal workbooks

  1. 01 Sales engineers recalculate every custom dimension inquiry
  2. 02 Price logic lives in files named after people
  3. 03 Dealers cannot quote non-standard sizes alone
  4. 04 One changed length restarts the entire quote cycle
  5. 05 ERP gets specs retyped from email threads

With Mercura

  1. 01 Parameters entered in a shared configurator
  2. 02 Product-owned formulas calculate price and BOM
  3. 03 Out-of-range inputs blocked before the PDF goes out
  4. 04 Dimension changes update price on the same configuration
  5. 05 Parametric values travel with approval and order

Business impact

Where parametric CPQ fits (and where it stops)

Parametric configuration is for products defined by continuous engineering inputs, not for picking a finished catalog code. It sits between discrete variant selection and full engineer-to-order design. Mercura does not replace CAD, FEA, or one-off structural calculation. Formulas and ranges need an owner when products change. If your team already knows how price and BOM should follow length or load, putting that logic in CPQ keeps inquiry, configuration, price, approval, and order on one path instead of a private spreadsheet.

Business impact

Quote custom dimensions faster

Parameters drive price and BOM without a side spreadsheet.

Less spreadsheet engineering

Ranges and formulas evaluated in the configurator.

Automatic component derivation

Supports, panels, and kits follow the inputs entered.

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

Derived product · ranges valid

Walk a length-and-load quote without Excel

Book a demo and enter real parameters until you see a ranged, priced configuration ready for approval.

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.