Home / Glossary

Variant management

Also called: Variety management, complexity management

The discipline of deciding which product variants a company offers, how they are defined, and how their cost and complexity are kept under control over their whole life.

Every manufacturer wants to give customers choice. Every plant would rather build one thing. Variant management is the work of living between those two truths without letting either win completely.

It is part engineering (how variants are structured), part data (how they are modelled and maintained) and part portfolio decision (which ones deserve to exist at all). Most companies are good at one of the three.

What it covers

QuestionWho usually owns itWhere it lives
Which variants do we offer?Product line managementPortfolio, price book
How are they built from shared parts?EngineeringModular architecture, BOM
How are they described and constrained?ConfigurationRule set, 150% BOM
When do they change or retire?Engineering change, product managementECOs, lifecycle states

Why it's hard

Variety is cheap to add and expensive to keep. Adding a finish takes a meeting. Keeping it costs a price-book column, renders, dealer content, test configurations, stock, and a line on every change impact analysis for the rest of its life. Those costs are spread across so many teams that nobody sees the total, which is how zombie variants survive.

What good looks like

  • Variety is offered where customers value it and hidden where they don't. Customers choose a finish; nobody wants to choose a screw.
  • Shared modules absorb the variety, so a new option adds a few parts, not a few hundred.
  • Every variant has a known volume and a known cost to maintain, reviewed on a schedule.
  • Retiring a variant is as normal as launching one.

Questions people ask

Is variant management the same as SKU rationalization?

SKU rationalization is one activity inside variant management: periodically pruning what you sell. Variant management also covers how variants are designed, modelled and changed.

Who should own it?

Ideally someone who can see engineering cost, configuration effort and sales volume at the same time. In practice that is often a product line manager working closely with configuration.

Updated November 2026. Think I've got something wrong? Tell me.