Exploded View vs Parts List vs BOM

A side-by-side comparison of exploded views, parts lists and bills of materials — what each one contains, who maintains it, where they overlap, and where they diverge in spare-parts catalog data.

An exploded view is a visual diagram. A parts list is a flat table keyed by position number. A BOM is a hierarchical component tree. They describe the same product from different angles, for different audiences, and they almost never agree completely.

Side-by-side comparison

	Exploded view	Parts list	BOM (bill of materials)
What it is	A diagram showing components pulled apart along assembly axes	A table mapping position numbers to part numbers, descriptions and quantities	A structured tree of every component, organized by parent-child levels
Format	Image (raster or vector), embedded in a PDF or displayed on a portal	Table (rows and columns), in a PDF, spreadsheet, ERP or catalog database	Hierarchical data structure in ERP, PLM or MES
Scope	One assembly	One assembly	Entire product (may contain hundreds of assemblies)
Depth	What can be drawn — excludes components too small or too internal to illustrate	One level: position → part	Multi-level: product → assembly → sub-assembly → component → fastener
Primary audience	Technician identifying a part visually	Technician or buyer ordering a part by number	Engineering, manufacturing, service planning
Who creates it	Technical publications or engineering	Catalog team or technical publications	Engineering (eBOM), manufacturing (mBOM), service (sBOM)
Update frequency	Rarely — redrawing is expensive	When part numbers change (supersession, new revisions)	When design, manufacturing process, or service procedure changes
Supersession awareness	None — the diagram shows the original part number	May or may not track supersession, depending on the system	ERP BOM usually updated; PLM eBOM may lag
Applicability data	Header note (free text: 'For model XR-700')	May include a header note or a separate fitment table	Implicit in the product structure; serial-range variants handled by BOM effectivity

Where they overlap

All three describe the same product’s components. In a well-maintained system:

Every position in the exploded view corresponds to a row in the parts list
Every part in the parts list corresponds to a node in the sBOM (service BOM)
The quantities agree

In practice, these three conditions rarely hold at the same time. The exploded view was drawn once and not updated. The parts list was updated for some supersessions but not others. The BOM is in a different system maintained by a different team.

Where they diverge

Exploded view shows things the BOM does not. The diagram shows spatial relationships — where a part sits in the assembly, how components nest together. The BOM is a list, not a picture.

BOM contains things the exploded view does not. Internal components too small to draw (o-rings, pins, set screws), process assemblies (phantom BOMs that exist for manufacturing but are not physical subassemblies), and consumables added by the sBOM but absent from the original design.

Parts list is the bridge, but an imperfect one. It maps the diagram positions to part numbers, but it is flat (one level) while the BOM is hierarchical. A parts list says “position 14 = HY-3200, qty 1.” The BOM says “assembly A1 → sub-assembly A1.3 → component HY-3200, qty 1, level 3.”

When the disagreements matter

The divergence becomes a business problem when:

A customer searches by the old number from the exploded view and the parts list has the new number but the exploded view does not, so they see the right diagram pointing at the wrong number.
A service team orders from the sBOM but the sBOM does not include a consumable that the parts list carries, so the order is incomplete.
An engineering change updates the eBOM but the sBOM and the parts list are not updated, so the service catalog shows the old part while manufacturing uses the new one.

How Claro fits

Claro sits at the identity layer that connects these artifacts. When a position in a parts list references a part number, Claro resolves it to the canonical product identity — following supersession chains, checking cross-references, and surfacing mismatches between the parts list and the BOM. The exploded view stays visual; the data behind it stays current.

Glossary

Exploded view, parts list and BOM

Definitions and where each lives in your data.

Guide

Parts book data model

The four layers and why separating them keeps the book current.

Playbook

Convert a PDF parts book

Extraction and structuring workflow.

Glossary

Position and callout numbers

The reference numbers linking diagram to table.

FAQ

What is the difference between a parts list and a BOM?

A parts list is a flat table that maps position numbers to part numbers, descriptions and quantities for one assembly. A BOM is a hierarchical tree that shows every component in a product, organized by parent-child relationships across multiple levels. A parts list is one view of one assembly; a BOM is the full structure.

Can an exploded view replace a BOM?

No. An exploded view shows the spatial arrangement of parts in a single assembly but does not represent multi-level hierarchy, manufacturing sequences, or components too small to draw. It is a visual reference, not a data structure. A BOM is the structured data that the exploded view illustrates — incompletely.