Customer specification
A readable summary of selected product, dimensions, finishes and accessories.
Proves: What the customer chose—not necessarily every physical component.
BOM and production-output guide
From one valid configuration to the exact structure operations accepts.
Product configurator BOM generation connects customer choices and dimensions to stable assemblies, components, quantities, units and revisions. The output becomes valuable when the next responsible system can understand, verify and reproduce it.
Clear definition
A BOM is a governed product structure, not a screenshot with parts.
A bill of materials identifies the components that make up a product or assembly and records how each item relates to its parent. Useful BOM data includes stable component identity, quantity, unit and structure. Configurable products add another requirement: the structure must resolve correctly for one accepted combination of characteristics, dimensions and dependencies.
The configurator does not need to replace PLM, ERP or manufacturing. It can preserve the selected product state, calculate agreed quantities, resolve component mappings and deliver a configured-order or BOM request to the authoritative system. In other implementations, it can generate an accepted sales or operational BOM directly.
Before implementation, name the output precisely. A customer specification, quote line, sales BOM, engineering structure, manufacturing BOM, cut list and installation pack serve different audiences. Calling all of them “the BOM” hides the ownership and acceptance work that makes production data dependable.
Interactive BOM lab
Configure the pergola. Watch the structure resolve.
This example exposes component-selection and quantity logic for learning. Its part codes, dimensions and rules are illustrative and are not a customer's approved engineering or manufacturing specification.
Configuration
Bioclimatic pergola
Derived state
Roof zones
1
Blades per zone
24
Mounting
Wall-mounted
Rule revision
BOM-R18
BOM · CFG-7X4P2 · Revision 3
Model PERG-BIO · Rules BOM-R18 · Status generated
ItemQuantitySourceDestination
Configured bioclimatic pergola
PERG-BIO
1 EA
Product family
Configured order
Structural frame assembly
ASM-FRAME
1 SET
Always included
Frame station
Front beam profile
BEAM-FRONT · cut 4.20 m
4.20 M
Overall width
Profile cutting
Wall connection beam
BEAM-WALL · cut 4.20 m
4.20 M
Mounting + width
Profile cutting
Side beam profile
BEAM-SIDE · cut 3.50 m
7.00 M
2 × projection
Profile cutting
Drainage post
POST-STD
2 EA
Mounting type
Frame station
Wall fixing set
FIX-WALL
1 SET
Mounting type
Hardware pick
Motorized louvered roof
ASM-ROOF
1 SET
Width zone rule
Roof station
Louver blade
LOUVER-150 · cut 4.20 m
24 EA
24 blades × 1 zone
Blade cutting
Roof drive motor
MOTOR-ROOF
1 EA
1 per roof zone
Electrical pick
Roof controller
CTRL-ROOF
1 EA
Motorized roof
Electrical pick
Integrated zip-screen package
ASM-SCREEN
1 SET
Screen selected
Closure station
Screen cassette
SCREEN-CAS · cut 4.20 m
4.20 M
Front opening width
Profile cutting
Screen fabric
SCREEN-FAB
9.66 M2
Width × example drop
Fabric cutting
Integrated LED package
ASM-LED
1 SET
Lighting selected
Electrical station
LED profile and strip
LED-CHANNEL
11.20 M
Front + side beams
Electrical prep
Dimmable LED driver
LED-DRIVER
1 EA
1 per roof zone
Electrical pick
Configured fastener and seal kit
KIT-FASTENER
1 SET
Resolved product state
Hardware pick
Visible lines
18
Unique item codes
18
Example cut length
120.40 m
Traceable structure
Every line carries a stable code, quantity, unit, selection source and intended operational destination.
Output taxonomy
Six structures people often mean when they say “BOM.”
Use the name, audience and acceptance test that matches the real next step. One implementation may create several related outputs from the same configuration revision.
Sales BOM
Commercial packages, configured items and quantities used for quotation or order review.
Proves: What is sold and priced at the agreed commercial level.
Configured order
A structured product identity with characteristic values, quantities and revision context.
Proves: Which accepted variant or made-to-order state continues downstream.
Engineering BOM
The engineering product structure, assemblies, components, documents and approved revisions.
Proves: How the designed product is technically structured.
Manufacturing BOM
The plant- and process-ready component structure used to plan and execute manufacturing.
Proves: What the responsible production system has accepted for build use.
Cut, pick or installation list
A task-specific transformation with lengths, quantities, grouping, stations or site packages.
Proves: What a particular team needs to prepare, pick, cut, assemble or install.
BOM data contract
Ten fields that make a component list operational.
Not every destination needs every field, but every required field needs one meaning, owner and acceptance example.
BOM identity
BOM ID, type, revision, status, usage, destination and effective context.
Configuration identity
Configuration ID and revision plus product-family and rule-model revision.
Hierarchy
Parent assembly, item level, position, sequence and required child relationships.
Component identity
Stable internal item ID, ERP or PLM code, description and lifecycle status.
Quantity
Value, unit, basis quantity, conversion, precision, scrap or yield where required.
Variable dimensions
Cut length, area, angle, handing, orientation or another accepted variable-size field.
Selection provenance
The product choice, dependency, formula or substitution that included the line.
Effectivity
Date, plant, market, serial, model or change context controlling which revision applies.
Documents
Drawing, specification, finish, installation note or quality evidence linked by stable reference.
Delivery state
Generated, reviewed, accepted, rejected, exported, acknowledged or superseded.
Source-of-truth design
Do not force six systems to pretend they own the same record.
Product configuration connects catalogue, engineering, commercial and production data. Assign authority per field and stage, then preserve identifiers and acknowledgements across each handoff.
DomainTypical ownershipImportant boundary
Catalogue or PIM
Product, option and component identity, descriptions, lifecycle and market availability.
Does not prove manufacturing quantity or routing by itself.
Configuration model
Accepted characteristics, dependencies, exclusions, dimensions and derived product state.
Should not invent an unapproved production component.
PLM or engineering
Engineering structures, component revisions, drawings, change orders and technical release.
May not own the customer, quote or commercial package.
ERP or manufacturing
Material master, plant-specific MBOM, units, planning, work definitions and accepted order records.
Should receive stable configuration meaning rather than a free-text description.
CPQ or commerce
Commercial lines, customer price, quote, approval and configured-order request.
A sales line is not automatically a production-ready BOM line.
Configurix workflow
Saved configuration, rule evaluation, agreed component mapping and delivery traceability.
Production authority remains where the implementation contract assigns it.
Structured handoff
Send identity and provenance—not a flattened note.
A receiving system should know which configuration and revisions created the BOM, why each component was selected, what the quantities mean and whether the structure is generated, reviewed or accepted.
{
"bom": { "id": "bom_CFG-7X4P2_r3", "type": "configured_order", "revision": 3 },
"configuration": { "id": "CFG-7X4P2", "revision": 3, "state": "valid" },
"model": { "family": "PERG-BIO", "revision": "2026.08", "ruleRevision": "BOM-R18" },
"context": { "plant": "EU-01", "effectiveAt": "2026-08-19" },
"items": [
{ "position": "10", "parent": null, "code": "ASM-FRAME", "quantity": 1, "unit": "SET" },
{ "position": "20", "parent": "10", "code": "BEAM-FRONT", "quantity": 4.2, "unit": "M",
"source": { "field": "width", "value": 4.2, "rule": "FRAME-WIDTH" } },
{ "position": "30", "parent": "10", "code": "POST-STD", "quantity": 2, "unit": "EA",
"source": { "field": "mounting", "value": "wall", "rule": "POST-QTY" } }
],
"delivery": { "destination": "ERP", "status": "pending_acknowledgement" }
}Permanent acceptance pack
Ten tests before a BOM reaches operations.
Use examples approved by engineering, production and the receiving-system owner. Keep them after launch and rerun them whenever products, components, rules or integrations change.
Known configuration
Generate a representative product and compare every expected component, quantity, unit, hierarchy and revision with an independently approved result.
Minimum and maximum dimensions
Test dimension boundaries and increments. Verify variable lengths, repeated modules, supports, hardware and rounding on both sides of each threshold.
Option inclusion and removal
Add and remove screens, glazing, motors, lighting or another dependency. Confirm all and only the related components change.
Substitution
Trigger a market, plant, stock or revision substitution. Preserve the reason, approved alternative and downstream identity.
Multi-level explosion
Verify parent assemblies, subassemblies and leaf components at the exact level expected by the receiving system.
Revision and effectivity
Generate before and after an approved component or rule change. New work uses the correct revision while historical output remains reproducible.
Invalid configuration
Attempt to generate from an incomplete or invalid state. Production-marked output must stop or enter an explicit review state.
Export acknowledgement
Send the structure to ERP, PLM or another destination. Reconcile IDs, units, quantities and revision, then record acceptance or actionable rejection.
Duplicate and retry
Repeat a timed-out delivery. The destination must not create an unintended second order or BOM revision.
Human amendment
Apply an allowed engineering or order-specific change. Record owner, reason and revision without silently rewriting the reusable product model.
Failure patterns
Six ways a plausible BOM becomes unsafe data.
A parts picture called a BOM
The output has labels and thumbnails but lacks stable component IDs, quantities, units, hierarchy or revision.
Better: Define the exact downstream contract and verify it against the receiving system.
Sales lines treated as factory lines
A commercial package such as “lighting kit” is assumed to contain every production component and operation.
Better: Map sales, engineering and manufacturing structures explicitly instead of assuming one universal level.
Quantities copied from the 3D scene
Visible objects are counted even though manufacturing uses different assemblies, consumables or yield logic.
Better: Derive BOM quantities from approved component rules; let 3D consume the same product state, not act as authority.
Text used as component identity
Renaming or translating “anthracite post” breaks an export, saved project or substitution.
Better: Use stable item and revision IDs; render audience-specific labels separately.
No effectivity policy
A component is replaced and old configurations silently explode into today's parts.
Better: Version structures and rules, then define preserve, review, migrate or regenerate behavior.
Export success without reconciliation
The configurator sent a payload, but nobody confirmed what the ERP or PLM created or rejected.
Better: Capture destination identity, acknowledgement, rejection details and a controlled retry path.
Primary references
Learn from systems that manage real product structures.
These official references inform the terminology and acceptance questions in this guide. They do not imply that every Configurix project uses SAP or Oracle.
SAP: configurable-material BOM
Official guidance for a configurable-material super BOM containing the components required across possible options, with selection conditions controlling variant parts.
SAP: super BOM
Official description of variable and non-variable parts, selection conditions, procedures, class items and configurable subassemblies.
SAP: order BOM for variant configuration
Official reference for sales-order-specific BOMs, multi-level explosion and controlled manual changes for complex made-to-order products.
Oracle: structure types
Official reference distinguishing standard, model, option-class, planning and phantom structures and their component relationships.
Oracle: structure details and revisions
Official guidance for multi-level structure components, reference dates, revisions, change control and configurator placeholders.
BOM generation FAQs
Detailed answers for buyers, product owners and operations teams.
Continue the architecture
Connect component output to the complete product system.
Product data model
Define stable product, component, configuration and revision identities before mapping outputs.
Product rules engine
Control component selection, derived quantities, substitutions, boundaries and review states.
Product pricing engine
Keep sales lines and price results connected to the same accepted configuration.
Configurator security and privacy
Protect configured orders, component data, operational files, service identities and production-system delivery.
3D asset pipeline
Keep visible modules, repeated components and generated dimensions traceable to the component identities used downstream.
Configurator testing and QA
Verify component identity, hierarchy, quantities, revisions, destination acknowledgement and recovery in one acceptance pack.
Configurator integrations
Deliver structured configuration and BOM data reliably to PLM, ERP and production systems.
Configure-to-order software
Connect the governed customer configuration to quote acceptance, configured order data and operational handoff.
Product configurator ERP integration
Map configured products, components, quantities, revisions and acknowledgements into an accepted ERP contract.
Product configurator PLM integration
Connect released engineering structures, variants, effectivity and revisions to configured BOM requests and controlled change.
Product configurator MES integration
Deliver accepted production orders, manufacturing BOMs, routings and instructions, then reconcile genealogy, quality and actuals.
Configure-to-order vs engineer-to-order
Separate rule-resolved configured BOMs from order-specific engineering changes, review and release.
Requirements checklist
Write BOM identity, hierarchy, units, revisions and acceptance cases into the vendor scope.
Maintenance and governance
Control component, rule, structure and destination changes after launch.
Bring one approved product and its real component structure.
We will map configuration fields, component-selection rules, quantities, revisions, destination ownership and acceptance examples for the exact output your workflow needs.