Engineer-to-Order with BOM Output
Every configuration produces an indented bill of materials that lands on the quote line and prints on the output document for manufacturing handoff.
The problem
In engineer-to-order business, the gap between what sales quoted and what manufacturing builds is where projects lose money. Bills of materials assembled by hand after the deal closes invite transcription errors and missed components. Manufacturing needs a BOM it can trust, derived from the exact configuration the customer approved.
How it works in Neblex CPQ
Neblex CPQ includes BOM as one of its eight typed rule kinds. As a rep configures the product, BOM rules assemble the bill of materials from the choices made, so the BOM is a direct output of the configuration rather than a separate authoring step. The result lands on the quote line together with pricing and lead time.
The validation gate protects the input: a configuration cannot be committed while violations, missing required fields, or conflicts remain, so every BOM comes from a valid configuration. Data-driven rules can pull component data from data tables and master data through DQL. Where-used dependency analysis shows what a change touches before you make it.
For handoff, the BOM prints on the output document through the drag-and-drop template builder, alongside line items, tables, and totals blocks. Downstream systems can read the same data through the REST API and the integration event feed. Request a demo to see a configuration turn into a manufacturing-ready document.
Step by step
Author BOM rules
Define how configuration choices map to components using the BOM rule kind.
Configure the product
Reps work through the configurator while BOM rules assemble the bill of materials in the background.
Commit through the gate
The validation gate blocks commit until violations, required fields, and conflicts are resolved.
Review on the quote
The generated BOM lands on the quote line with pricing and lead time.
Print for manufacturing
Document templates print the BOM on the quote output for handoff.
Feed downstream systems
ERP and manufacturing tooling reads quotes and configurations through the REST API and event feed.
Platform capabilities used
- BOM rule kind
- Validation gate on commit
- BOM printed on documents
- Data tables and DQL
- Where-used dependency analysis
- REST API and event feed
Common questions
Where does the BOM show up?
The BOM is generated by BOM rules during configuration, lands on the quote line, and prints on the output document through the template builder. External systems can read the same data through the REST API.
Can BOM rules use component data we already maintain?
Yes. Data-driven rules query data tables and master data through DQL. Sandboxed JavaScript functions can also call named external API endpoints when logic needs data from other systems.
How do we keep BOM logic safe as products evolve?
Where-used dependency analysis shows what a change affects before you make it. Rule conflict detection flags contradictory rules, and rule and function version history records every revision.
Related use cases
Configure-to-Order Quoting
Sales teams configure complex products against live product logic while a validation gate stops invalid configurations from ever reaching a quote.
ConfigurationVisual 3D Configuration
A live 3D viewer inside the configurator reacts to every choice, driven by the same rules that drive the quote and fed directly from your CAD files.
Quotes & DocumentsBranded Quote Documents
Build branded, localized quote PDFs with a drag-and-drop template builder, a shared document library, and per-quote output settings.
See it on your own catalog
Bring your product model and pricing rules and we will walk this workflow with your data.