Multi-Level BOM Configuration for CPQ
Quote approved. Production still waits for someone to rebuild the BOM in ERP. Explode sales configuration into multi-level BOMs with sub-assemblies and derived quantities on order.
On configure
BOM generated from selections
Multi-level
Assemblies and sub-assemblies
ERP-ready
Hierarchy export on order
The challenge
Quote approved. Production still waits for someone to rebuild the BOM in ERP.
A manufacturer of industrial dust collection and fume extraction systems closes configured quotes daily: filter module, fan stack, duct runs, controls. Each combination is valid in CPQ and priced correctly. Manufacturing opens the ERP and asks engineering to translate the sales configuration into a production BOM with sub-assemblies, derived duct lengths, and procurement quantities. That rebuild adds days before material release.
A missing sub-assembly stops the shop floor. A filter spec copied wrong from the quote PDF triggers rework. Procurement orders the fan for the previous revision because the BOM in ERP never matched the configuration the customer signed. Sales thinks the order is clear because the quote looks complete.
Modular configuration composes platforms from slot-filling modules. Parametric configuration calculates dimensions and derived attributes. Component libraries centralize reusable parts across models. Configuration templates start repeat builds from saved baselines. Multi-level BOM configuration is different: Mercura maps each configuration choice to BOM lines, sub-assemblies, and calculated quantities so manufacturing receives a hierarchy that matches what was sold.
Inquiry to config to price to approval to order should hand operations a multi-level BOM, not a quote PDF that engineering must reinterpret.
How it works
How Mercura generates multi-level BOMs from configuration
Product engineers model how options, parameters, and modules map to BOM structure in Mercura: top-level assembly, sub-assemblies, components, and quantities derived from configuration inputs. When a rep or customer completes a configuration, Mercura generates the multi-level BOM as hierarchical output. Engineers can preview the BOM during configuration for non-standard builds. ERP integration transmits the hierarchy without manual re-entry. Product model updates propagate to new configurations. Someone must maintain BOM mapping when components change and define which configurations still require engineering sign-off before release.
What's included
What multi-level BOM configuration covers
- Multi-level BOM generation when configuration completes
- Sub-assembly hierarchy with roll-up quantities
- Derived component quantities from parametric inputs
- Option-driven BOM variation per configuration path
- BOM preview during configuration for engineering review
- BOM versioning aligned with product model changes
- Hierarchy export formatted for ERP integration
- Works with rules, parametric models, and component libraries
The difference
Configuration to BOM before and after multi-level BOM
- Engineering translates every quote into ERP BOM by hand
- Sub-assemblies rebuilt from memory or old projects
- Procurement works from PDFs instead of hierarchy data
- Production stops when a component line is missing
- Sales-to-operations handoff depends on one engineer
- BOM generated from configuration on order release
- Sub-assembly hierarchy matches product model logic
- Derived quantities calculated from configuration inputs
- Engineering reviews exceptions, not every standard build
- Hierarchy BOM export to ERP without re-entry
Real-world application
Example workflow: dust collection BOM from configuration
A builder of industrial dust collection systems configured filter type, airflow, and duct layout in Mercura for every quote. Manufacturing received approved quotes but rebuilt multi-level BOMs in the ERP by hand, delaying material release. After multi-level BOM configuration, each completed configuration generates filter modules, fan stacks, and duct sub-assemblies with derived lengths. Engineers review non-standard layouts only, and standard orders reach the shop floor with a BOM that matches the signed configuration.
Business impact
Why multi-level BOM configuration is manufacturing output, not a quote appendix
Multi-level BOM configuration makes the bill of materials a direct output of how the product is modeled and sold. It complements modular platforms, parametric sizing, component libraries, and configuration templates. Mercura does not replace your PLM as the master for unreleased parts or engineering judgment on bespoke layouts. Someone must own BOM mapping when the product model changes. If the pain is "the quote is approved but ERP still waits for engineering to rebuild the BOM", configuration-to-BOM aligns inquiry, configuration, price, approval, and order with what production actually builds.
See a configured dust collection system explode into a multi-level BOM
Book a demo and complete a configuration until sub-assemblies, derived quantities, and ERP-ready structure appear without a manual BOM rebuild.
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.