Bill of materials
At a glance
- One physical package contributes one BOM identity even when its symbol has several units
- Assembly variants, DNP, hand-fit, THT, SMT and BOM-only treatment stay explicit
- Saved sourcing evidence keeps provider, MPN, package, stock state, price freshness and decision time
- JLCPCB and PCBWay have separate BOM and placement profiles; generic CSV columns are configurable
- Every assembly file joins to occurrence-qualified physical package identities
Open BOM from the Output group. The engineering BOM is built from physical package identities, not from the number of symbol units. U1A through U1D remain one LM324 package.
What separates a line
Part identity, value, footprint variant, pinned MPN, assembly variant and fit state determine the line. DNP, hand-fit, THT, SMT and BOM-only parts stay explicit. Sources, power symbols and instruments never appear because they are not physical packages.
Sourcing columns come from the saved project decision. They retain provider, exact manufacturer and MPN, package, SKU, stock as known or unknown, price breaks, currency, fetched time and expiry. Stale or missing data remains visible. A pinned MPN is never replaced automatically.
Assembly output
The Fabrication Bundle compiler owns the production BOM and placement files. JLCPCB and PCBWay use separate filename and column profiles; a generic profile supports a bounded configurable column set. Bottom coordinates and rotations use the same transform reviewed in Board Layout and Populated 3D.
Vendor placement output contains eligible fitted parts. DNP and hand-fit parts remain present in the engineering BOM and assembly drawings so their treatment can be reviewed.
Every placement row resolves to one occurrence-qualified physical package and BOM identity. Duplicate or stale identities block assembly compilation. The prepared fabrication manifest records each file's exact byte count and SHA-256 hash.