Published at: 2026-09-17
Sales BOM overview
Sales BOM breaks a complex product down from a single item into a configurable, constrained, and priceable combination structure. For the business, it is not just a bill of materials display. It is a sales configuration capability that can be used directly in quote and ordering workflows.
What problem this capability solves
The value of Sales BOM is mainly reflected in several common pain points:
- Quoting complex products often requires multiple people and is slow.
- Sales may promise configurations that exceed the company’s actual delivery scope.
- Too many optional combinations are hard to control consistently by hand.
- Pricing rules change dynamically and are difficult to manage through memory alone.
The core value of Sales BOM is to move these rules out of individual sales experience and into the system.
If the company sells a broad product portfolio with complex structures, offers both products and services, wants to speed up quote generation, and needs to manage dependencies or system integrations among options, Sales BOM is usually the more suitable solution.
Core components
Sales BOM is not a single object. It is composed of several layers:
- Product combinations: define the parent product, child items, BOM type, purpose, and version.
- Groups and child-item structures: define which components can be sold together and how they are displayed hierarchically.
- Constraint and dependency rules: define required choices, forbidden choices, and quantity relationships.
- Order configuration modes: define how sales complete configuration on the front end.
- ERP integration: hand over the final result to downstream systems.
Applicable scenarios
Sales BOM is usually a good fit when the business has the following characteristics:
- The product portfolio is wide and structurally complex.
- One order may contain both standard products and combination products.
- Customer requirements often involve different child items, models, and quantity combinations.
- The business wants sales to complete configuration and quoting more accurately on the front end.
Typical usage flow
Combined with the page structure and configuration path, Sales BOM usually enters the workflow in this order:
- An administrator enables CPQ and the related switches.
- Product combinations, child-item groups, and hierarchical structures are created.
- Constraints, quantity relationships, and configuration modes are defined.
- Sales use the combination product in quotes or orders to perform configuration.
- The final result continues into order execution or ERP integration.
Relationship with product attributes
Sales BOM focuses more on structure and combinations, while product attributes focus more on parameters and price differences. In real business scenarios, they are often used together: Sales BOM defines the parent-child structure, and product attributes refine the specific parameters of parent or child items.