Balancing Customer Variety and Standardization
Every variant you add for a customer brings hidden costs. The real winners offer meaningful choice with minimal internal complexity — here is how.
Glossary
Variant Management
Zombie Variants
n. pl. (ˈzäm-bē ˈver-ē-ənts)
Definition
Zombie variants are product options that remain active in the catalog but generate little or no sales, silently consuming engineering, procurement, and service resources.
Zombie variants are product configurations or options that remain active in the product catalog but are rarely or never ordered in practice. Like their namesake from folklore, they refuse to disappear — yet they consume resources without delivering value. In variant management, zombie variants are a direct consequence of inadequate portfolio governance.
How zombie variants accumulate
Zombie variants rarely appear all at once. They build up gradually when new variant requests are approved without a clear threshold for minimum viability, and when the portfolio is never systematically reviewed.
Common entry points include:
- Customer specials — A one-time variant was built for a specific customer, formalized in the catalog, but never reordered.
- Regional options — An option was added for a specific market or regulation that has since changed, but the option was never retired.
- Predecessor variants — An older product generation remains technically active while a newer version has absorbed all real demand.
- Feature combinations — An option was listed as theoretically available but in practice is never selected alongside the product’s standard base configuration.
The cost of zombie variants
The defining characteristic of zombie variants is the gap between their catalog status and their actual demand. But catalog status is not free. Each active variant — no matter how infrequently ordered — typically requires:
- Engineering effort for maintenance and change management
- Procurement attention (minimum order quantities, supplier qualification)
- Spare parts planning and stocking
- Service documentation and training
- Entries in PLM, ERP, and CPQ CPQ – Configure, Price, Quote (ˌsē-ˌpē-ˈkyü) n. abbr. CPQ stands for Configure, Price, Quote — software that automates sales quoting for configurable products by enforcing product rules, calculating pricing, and generating output. systems that must be kept consistent
A single zombie variant may seem harmless. A portfolio of dozens or hundreds is a measurable overhead — one that accumulates invisibly unless someone specifically tracks variant-level sales and costs.
How to identify zombie variants
The most direct method is variant-level sales analysis: for each active option or configuration, how often has it been ordered in the last two to three years? Options with zero or near-zero demand relative to their maintenance cost are candidates for retirement.
Beyond frequency, consider:
- Cost-to-benefit ratio — Does the margin from the occasional order outweigh the maintenance overhead?
- Strategic relevance — Is the option retained for a specific customer relationship or regulatory requirement, even at a loss?
- Reusability — Does the variant share components with higher-volume variants, reducing its net cost?
How to eliminate zombie variants
Eliminating zombie variants requires both an analytical decision and an organizational process to act on it. Effective approaches include:
- Scheduled portfolio reviews — Treat variant reviews like financial audits, with defined criteria for retirement.
- End-of-life procedures — Communicate discontinuation to affected customers and provide migration paths to standard variants.
- Governance up front — Require a business case (minimum expected volume, margin contribution) before any new variant is added to the catalog.
Frequently asked questions
What is the difference between a zombie variant and a low-volume variant?
Not every low-volume variant is a zombie. A variant may sell rarely but still be strategically justified — for a key account, a regulated market, or as a platform component shared across the portfolio. A zombie variant is one where even this justification is absent: no strategic rationale, no meaningful demand, yet still consuming catalog and maintenance resources.
How often should a product portfolio be reviewed for zombie variants?
Most companies that actively manage variant portfolios conduct formal reviews annually, aligned with product roadmap or pricing cycles. Companies with fast-moving portfolios or high variant counts may review more frequently. The key is that reviews happen on a fixed schedule and are backed by actual sales data — not driven by gut feeling or customer pressure alone.