- Features > Component Libraries
Component Libraries for CPQ
Define product components once and reuse them across your entire catalog — so updates propagate automatically and your product model stays consistent at scale.
Reusable
Components across product lines
Instant
Propagation of component updates
Reduced
Product model maintenance overhead
The Challenge
The Problem with Duplicated Product Definitions
Manufacturers with broad product ranges often define the same components multiple times across their product catalog — the same motor, the same seal kit, the same control module appears in dozens of product configurations, each defined independently. When a component changes — a new specification, a new price, a new compatibility rule — each of those independent definitions must be updated separately. The maintenance burden grows with every product added to the catalog.
When component definitions are not kept in sync, inconsistencies accumulate. The same motor appears in two product configurations with different pricing. A compatibility rule is updated in one configuration but not others. A discontinued component remains available for selection in configurations that were not updated. These inconsistencies erode quote accuracy and create operational problems downstream.
For manufacturers with rapidly evolving product ranges — new component generations, supplier changes, regulatory updates — the maintenance of a product model built on duplicated definitions becomes a full-time job. Changes that should take minutes take hours because every affected configuration must be located and updated individually.
The problem compounds over time. As more products are added and more duplication accumulates, the product model becomes increasingly difficult to maintain accurately — and increasingly risky to update, since every change may have unintended consequences on configurations that share the affected component.
How It Works
How Component Libraries Work in Mercura
Mercura's component library system allows you to define components once — with their attributes, pricing, compatibility rules, and BOM data — and reference them across any number of product configurations. When a component is used in a product configuration, it is referenced by its library definition rather than duplicated. Changes to the component definition — price update, new compatibility rule, specification change — propagate automatically to every product configuration that references it. No manual updates to individual configurations required. Component libraries are maintained by your product management or engineering team directly in Mercura.
What's Included
Key Capabilities
- Centralised component library with single-source definitions
- Cross-product reuse — components referenced, not duplicated
- Instant update propagation to all referencing configurations
- Component versioning with change history
- Component compatibility rules inherited by all products using the component
- Component pricing managed centrally with automatic quote updates
- Component BOM data reused across all product BOMs
- Component search and browsing for model builders
The Difference
Before and After Component Libraries
- Same components defined independently in each product configuration
- Component updates require changes in each configuration separately
- Inconsistencies accumulate across product definitions over time
- Maintenance overhead grows with every product added
- Discontinued components remain in unupdated configurations
- Components defined once and reused across all products
- Component updates propagate instantly to all products
- All products stay consistent automatically
- Maintenance effort constant regardless of catalog size
- Discontinued components removed from all products in one action
Real-World Application
Example Use Case: Motor Drive Manufacturer
A motor drive manufacturer with 340 product configurations found that their standard motor components — 28 motor variants used across the catalog — were independently defined in an average of 12 configurations each. When a motor specification changed, their product management team spent 3–4 days locating and updating every affected configuration. After migrating to Mercura's component library model, all 28 motors were defined once. The next component specification change took 15 minutes to apply across the entire catalog. Product catalog accuracy improved measurably within the first month.
Quote turnaround dropped from 3 days to under 4 hours.
Business Impact
Why Component Libraries Matter
Component libraries are the architectural foundation of a maintainable product model. They convert a product catalog from a collection of independent definitions — each requiring individual maintenance — into a structured, interconnected system where changes are made once and applied everywhere. As catalog complexity grows, the difference between a component library-based model and a duplicated-definition model grows from inconvenient to unmanageable. Mercura's component library capability is what enables large, complex product catalogs to be maintained efficiently by a small product team.
See Component Libraries in Action
Book a demo to see how Mercura's component library system makes product model maintenance scalable.
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.