Visual BOM: Bills of Materials Your Sales Team Can Use
A bill of materials (BOM) is the list of parts needed to build a product. But traditional BOMs are designed for engineers and production teams—not sales reps or customers. A visual BOM changes that by adding images, context, and interactivity to the parts list.
This guide explains what a visual BOM is, how it works in Salesforce CPQ, why it reduces order errors, and how it connects product configuration to manufacturing without manual re-entry.
What Is a Visual BOM?
A visual BOM is a bill of materials that includes:
• Part images (so you see what each component looks like)
• Descriptions in plain language (not just engineering codes)
• Quantities and pricing (broken down by component)
• Hierarchy visualization (showing assemblies, sub-assemblies, and parts)
Traditional BOMs look like spreadsheets. Visual BOMs look like product catalogs.
Traditional BOM (text-only):
Part Number | Description | Qty
--------------|--------------------|----
CB-48-STL | Cabinet body 48" | 1
DR-18-LH | Drawer 18" LH | 2
HD-500-SS | Handle stainless | 2
SH-36-ADJ | Shelf adjustable | 3
Engineers understand this. Sales reps and customers? Not so much.
Visual BOM:
• Cabinet Body (48" steel) — [image] — Qty: 1 — $450 • Drawer (18" left-hinged) — [image] — Qty: 2 — $85 each • Drawer slides (soft-close) — [image] — Qty: 2 pairs — $25/pair
• Handle (stainless steel) — [image] — Qty: 2 — $12 each
• Adjustable Shelf (36") — [image] — Qty: 3 — $40 each
Now everyone—sales, customer, production—understands what's included.
How Visual BOMs Work in Salesforce CPQ
Visual BOMs are generated automatically during product configuration.
The Workflow:
1. Sales rep or customer configures a product (dimensions, materials, options)
2. CPQ builds the BOM in the background based on configuration rules
3. CPQ adds images and descriptions to each line item (pulled from a product library)
4. CPQ displays the visual BOM in the quote or on-screen during configuration
5. Customer approves the quote with full visibility into what they're ordering
The BOM is not static—it updates in real-time as configuration changes. Add an option? The BOM updates. Change a material? The BOM reflects the new components.
Why Visual BOMs Reduce Order Errors
Problem 1: Customers Don't Understand Text-Only BOMs
A traditional quote might say:
"Industrial workstation with (2) accessory rails, pegboard backing, and reinforced frame"
The customer approves it. Then production builds it and ships it. The customer receives it and says: "This isn't what I expected."
The problem? "Accessory rails" could mean 12 different things. The customer imagined one configuration; the factory built another.
Solution: Visual BOMs Show Exactly What's Included
With a visual BOM, the quote includes images of the accessory rails. The customer sees them before approving. If they're wrong, the customer says so before the order is placed—not after it's built.
Result: Order errors drop by 60-80% in most implementations.
Problem 2: Sales Reps Misconfigure Products
Sales reps aren't engineers. They don't always understand which components work together. Text-based BOMs don't help—"part CB-48-STL" means nothing without context.
Visual BOMs show components with images and descriptions. Sales reps see what they're quoting. Mistakes are caught during configuration, not after the sale.
Problem 3: Manufacturing Receives Incomplete Data
A text-only BOM might say "cabinet door." But which door? Left-hinged or right-hinged? Glass insert or solid panel?
Visual BOMs eliminate ambiguity. Each line item includes an image, detailed specs, and the exact part number. Manufacturing knows what to build.
Visual BOM Configuration: How It's Built
Creating a visual BOM requires three things:
1. Product Component Library
Every component (part, sub-assembly, material) needs:
• Part number
• Description (customer-facing, not engineering jargon)
• Image (photo or 3D rendering)
• Specifications (dimensions, material, finish)
• Cost and pricing
This library lives in your CPQ system or PLM system. CPQ pulls from it during configuration.
2. Configuration Rules
Configuration rules define:
• Which components are required for each product variant
• Which components are optional (add-ons)
• Which components are mutually exclusive (you can't have both)
• Which components are conditional (if A is selected, B is required)
Example: "If cabinet width > 48 inches, reinforced frame is required."
3. BOM Assembly Logic
When a customer configures a product, CPQ applies the rules and assembles the BOM automatically:
• Base product → pulls required components
• Selected options → adds optional components
• Configuration rules → enforces dependencies and constraints
• Output → visual BOM with images, quantities, pricing
Visual BOM vs. Engineering BOM vs. Manufacturing BOM
There are actually three types of BOMs:
1. Engineering BOM (eBOM)
Purpose: Design and documentation
Owner: Engineering (lives in PLM or CAD)
Contents: Every component of the product as designed
2. Manufacturing BOM (mBOM)
Purpose: Production instructions
Owner: Manufacturing (lives in ERP)
Contents: Parts to build, with quantities, work instructions, and routing
3. Sales BOM (Visual BOM)
Purpose: Quoting and customer communication
Owner: Sales (lives in CPQ/CRM)
Contents: Customer-facing description of what's included, with images and pricing
A complete CPQ system generates all three from the same configuration:
• eBOM for engineering review
• mBOM for production
• Visual BOM for sales and customer approval
Learn more about connecting engineering and sales data: </blog/what-tools-integrate-plm-workflows-erp-crm-systems|PLM, ERP, CRM integration →>
Visual BOM Platforms: What to Look For
If you're evaluating visual BOM tools, prioritize:
1. Automatic BOM Generation
The BOM should be created during configuration—not after. If your sales team has to manually build BOMs, you don't have automation.
2. Image Management
Every component needs an image. Look for:
• Support for product photos, 3D renderings, or CAD thumbnails
• Automatic image tagging (so images pull correctly during configuration)
• Image versioning (when a part is updated, the image updates too)
3. Multi-Level BOM Support
Real products have assemblies within assemblies (a cabinet contains drawers; drawers contain slides and handles). Your visual BOM must support hierarchical BOMs with nested components.
4. Integration with CPQ and ERP
The visual BOM should:
• Pull component data from your product library (PLM or ERP)
• Feed into Salesforce CPQ for pricing
• Export to ERP for production
One system, one source of truth.
5. Customer-Facing Output
The visual BOM should appear in:
• Quotes sent to customers
• Configuration interfaces (web configurators, portals)
• Proposal documents
If the BOM is only visible internally, you're missing half the value.
Bill of Materials Automation: The ROI
Automating visual BOM generation delivers measurable ROI:
• Faster quoting: No manual BOM creation (saves 30-60 minutes per quote)
• Fewer errors: Configuration rules enforce validity (60-80% reduction in order errors)
• Better customer experience: Customers see what they're buying before approving
• Faster manufacturing handoff: BOMs flow directly into ERP (no re-entry)
One modular furniture manufacturer reduced quoting time from 2 hours to 15 minutes by automating visual BOM generation. Order errors dropped from 22% to 3%.
The Bottom Line
A visual BOM transforms the bill of materials from an engineering document into a sales tool. It shows customers exactly what they're ordering, eliminates ambiguity, and ensures manufacturing receives accurate data.
If your current quoting process produces text-only BOMs—or worse, no BOMs at all—you're losing deals to confusion and drowning in order errors.
Visual BOM configuration connects product configuration to manufacturing without manual translation. What the customer approves is what the factory builds.
Want to see how visual BOM works for your products?
Let's talk →https://renderdraw.com/contact