Attributes and options
Define characteristics, selectable options, and dependencies that mirror how the product is built and sold. Reuse attribute libraries across families instead of retyping options per line.
Structure product data that every channel quotes from
Model attributes, assemblies, prices, and assets once in Mercura CPQ. Internal sales, dealers, and customer configurators pull from the same product definition instead of copying spreadsheets per market.
Da
Product data in Excel, CAD exports, and email
A
One CPQ model for quotes and configurators
Da
Engineering approves every sales variant
A
Structured attributes feed the configuration engine
Da
Price lists rebuilt for each region
A
Commercial data maintained once, synced where needed
Product catalogue
Commercial data built on structured product models
Mercura CPQ holds the data sales needs to configure and quote: attributes, assemblies, prices, documents, and visuals tied to the same product record. Engineering can keep PLM as the system of record while Mercura carries the commercial layer your channels actually use.
Price lists and formulas
Attach list prices, cost-plus rules, and regional mappings to the product model, ready for the pricing engine to calculate net totals during configuration.
Datasheets and quote PDFs
Link technical sheets and document templates so generated quotes pull the right content per configuration.
3D configuration views
Connect 3D assets that update with valid selections for sales, dealers, and buyer-facing configurators.
Variant imagery
Store marketing and option-specific images that appear in configurators and quote documents.
Market localisation
Translate names, descriptions, units, and assets for each country or language you sell into.
Modelling lenses
Three lenses on your product model
See how assemblies reuse across lines, which data must be quotable before launch, and what changes when you add a new option.
Catalogue structure
Map how modules, assemblies, and attribute libraries repeat across product families.
- Shared assembly reuse
- Attribute libraries
- Lines fed from one model
Quotable readiness
Separate engineering-only data from what sales, dealers, and self-service need to configure and price.
- Options ready for CPQ
- Missing price or BOM data
- Markets blocked at launch
Change impact
Understand which configurators, price rules, and documents break when product data changes.
- Rules affected by edits
- Documents tied to options
- Integration sync points
How it works
How Mercura product modelling
feeds every quote
Import structure from PLM where you need it, define the commercial layer in Mercura, and publish one model to configurators, pricing, and integrations.
Structure catalogue
Attributes and assemblies
1
Attach commercial data
Prices, copy, documents
2
Validate with rules
Configuration engine
3
Publish
CPQ, dealers, ERP
01
Structure attributes and assemblies
Model options, modules, and dependencies that match how manufacturing builds and how sales describes the product. The same structure powers BOM output and guided selling.
02
Attach commercial data
Add price lists, cost drivers, localized copy, and documents to the same record the configuration engine will use.
03
Connect engineering sources
Import BOM or attribute data from PLM or spreadsheets, then maintain the sales-facing layer in the config panel.
04
Publish to sales channels
Release the model to internal CPQ, dealer portals, and integrations without rebuilding data per market.
What a maintained product model changes in daily quoting
The goal is not a bigger catalogue file. It is to stop rebuilding product data for every channel and keep invalid variants out of quotes.
01
One source for sales and dealers
Internal reps and partners configure from the same attributes, prices, and documents.
02
Less engineering rework on routine deals
Standard variants draw from maintained modules; engineering sees exceptions, not every quote.
03
Faster launches for new options
Add options or markets in the model once, then publish to CPQ and integrations without new spreadsheets.
Fit and limits
When product modelling in CPQ is not the right layer
Mercura structures attributes, rules, and commercial data for configurators and quotes. It is not a PLM replacement and not needed for every catalogue.
Fixed SKU catalogue
If you sell standard products with no options that change BOM or price logic, a simple product list in ERP is enough. Product modelling is for configurable portfolios.
PLM already owns the full model
When engineering structure, revisions, and effectivity are fully managed in PLM with clean exports to sales, CPQ modelling focuses on the commercial layer and rules, not duplicating PLM.
Every quote is a one-off project
True one-off engineered deals without reusable modules do not benefit from a shared CPQ model. Standardise repeatable variants first.
Documents or visuals only
If the gap is PDF templates or renders without changing product logic, use quote documents or visualizations. Modelling is the foundation for rules, BOM, and price.
Related
If your bottleneck is not “our product data is scattered and sales cannot reuse it,” fix data ownership before you model everything in CPQ.
Richiedi una demo CPQ