Free BOM Templates for SolidWorks Teams (Excel Download)

Five Excel BOM templates in one workbook — EBOM, MBOM, CBOM, ServBOM and SBOM — plus how to build a clean EBOM from a SolidWorks assembly and the point where a spreadsheet stops keeping up.

You can walk away from this page with a working Bill of Materials for every stage of your product — design, production, configuration, service, and sales — in one Excel workbook, built around the part numbers, revisions, and configurations you already maintain as custom properties.

Download Free BOM Templates (Excel) — a single .xlsx workbook, no email gate and no account. Then read on for which BOM type each job needs, how to pull a clean EBOM out of a SolidWorks assembly, and the point at which a spreadsheet stops being the right tool.

Sibe is a collaboration-first CAD Document Management platform with a native add-in for SOLIDWORKS® 3D CAD. When the spreadsheet stops keeping up, you check the assembly in directly in SolidWorks and Sibe builds the indented BOM from the assembly’s own references instead — see BOM management for SolidWorks.

What is inside the workbook

One Excel file, six tabs. A short “Start here” tab explains the color legend and how the tabs relate, then each BOM type gets its own sheet with headers, a filled example row, and working cost formulas.

• EBOM: the product as designed, mirroring your SolidWorks assembly tree
• MBOM: the product as built, including the consumables and packaging your CAD tree never holds
• CBOM: variants and options, mapped to SolidWorks configurations
• ServBOM: spares and field-replaceable kits for aftermarket support
• SBOM: bundles and kits as sold, mapped back to real part numbers

Every tab carries a Part Number column. Keep that column identical across tabs and engineering, purchasing, and service stay in step. Let it drift and you get the classic failure: production quotes a revision that no longer exists.

What a Bill of Materials actually does

A Bill of Materials is the list of everything that goes into a product, how many of each, and how they nest. That sounds simple until you notice that five different teams need five different views of the same product.

Engineering cares about design intent and revision. Manufacturing cares about work centers, lead times, and the adhesive that was never modeled. Sales cares about what the customer ordered. Service cares about what a technician can swap in the field. Forcing all of that into one sheet is why BOMs get abandoned.

So you keep separate BOMs, linked by part number. The templates below give you a starting structure for each.

The five BOM types, and which one you need

1. Engineering BOM (EBOM)

What it covers: the product as engineering designed it. For a SolidWorks team, the EBOM is the assembly tree written down: parts, subassemblies, quantities, revisions, and materials, in the structure of the model rather than the structure of the factory.

When you use it: during design, for design reviews and prototyping, and when you hand a product definition to manufacturing.

What to fill in:

• Level: indent position, so the tree stays readable (1, 1.1, 1.1.1)
• SolidWorks File Name: the actual .SLDPRT or .SLDASM, so anyone can find the model
• Part Number: your custom property, not the file name
• Description, Revision, Material: pulled from the properties you already maintain
• Qty per Parent: how many at that level, not the rolled-up total
• Drawing Number: the .SLDDRW that releases the part

SolidWorks note: keep the EBOM tied to the CAD data rather than retyped from it. A single stale quantity is enough to order the wrong number of housings. BOM management for SolidWorks closes that gap by reading the assembly references instead of asking you to transcribe them.

Pro tip: use real revision letters (A, B, C). “Latest” is not a revision.

2. Manufacturing BOM (MBOM)

What it covers: the product as the factory builds it. The MBOM restructures the EBOM around production sequence and adds everything that ships but never gets modeled: adhesives, grease, fasteners bought by the box, packaging, labels.

When you use it: production planning, ERP and MRP, and standardizing assembly across sites.

What to fill in:

• Operation / Work Center: which station consumes the part
• Source: make, buy, or consumable
• Supplier and Supplier Part No.: for procurement
• Lead Time: the number that decides your build date
• Unit Cost: Extended Cost calculates itself
• Routing / Instructions: the step notes the shop floor needs

SolidWorks note: the MBOM is where SolidWorks users feel the limits of the model. Toolbox fasteners, weld consumables, and cardboard have no .SLDPRT, so they get added by hand and then forgotten on the next revision. In Sibe’s BOM management for SolidWorks you check out the generated BOM, add those rows, and check it back in. The packaging, adhesives, and fasteners live on the BOM itself instead of in a separate spreadsheet nobody opens.

Pro tip: reconcile the MBOM against the EBOM every release. Mismatches between the two show up as rework on the shop floor.

3. Configurable BOM (CBOM)

What it covers: one product family with many valid builds. Instead of a fixed list, the CBOM holds a base assembly, the optional modules, and the rules for which options can sit together.

When you use it: configure-to-order products, sales configurators, and ERP integrations where writing out every variant is impractical.

What to fill in:

• Option Group and Option Code: the choice and the specific option
• SolidWorks Configuration: the configuration name in the model, so sales and CAD speak the same language
• Rule: written as logic (REQUIRES, EXCLUDES), not prose
• Price Delta and SKU Mapping: what the option costs and what it maps to when ordered

SolidWorks note: SolidWorks configurations and design tables already encode most of this. The work is naming them so a non-CAD colleague can read them. Config_750W tells a salesperson something. Config2 does not.

Pro tip: keep rules machine-readable. A configurator can act on “EXCLUDES CTL-BASIC”. It cannot act on “not usually available with the basic controller”.

4. Service BOM (ServBOM)

What it covers: only the parts a technician replaces in the field. It drops production consumables and adds spares, kits, and the documentation that goes with them.

When you use it: aftermarket support, service manuals, spare parts stock, and field technician prep.

What to fill in:

• Service Part Number: often different from the engineering number
• Engineering Part No.: the cross-reference that keeps service tied to design
• Replacement Kit ID: what a technician actually orders
• Service Interval: for preventive maintenance planning
• Field Replaceable: yes or no, decided once, not argued about on site

SolidWorks note: exploded views and the drawings you already produce are the fastest way to make a ServBOM usable. Share them as a link a technician opens in a browser rather than a 40 MB attachment, and the parts desk stops guessing.

Pro tip: write descriptions a customer can read. Internal jargon on a service part list costs you support calls.

5. Sales BOM (SBOM)

What it covers: the product as sold. Bundles, kits, and promotions under customer-facing names, mapped back to the part numbers behind them.

When you use it: quoting, CPQ and ERP systems, and any bundle that does not exist as a single assembly.

What to fill in:

• Sales SKU and Customer-Facing Name: what appears on the quote
• Component Part No.: the link back to EBOM and MBOM
• Qty in Bundle: how many of each component ships in the kit
• List Price and Discount %: Net Price and Extended Price calculate themselves

SolidWorks note: the SBOM is the one BOM your CAD model cannot generate, because it describes a commercial decision rather than a physical structure. What it does need is a trustworthy part number list to point at, which is why the EBOM has to be right first.

Pro tip: map every SBOM line to an internal part number. Unmapped bundle lines are where fulfillment errors come from.

How to build an EBOM from a SolidWorks assembly

The other four BOMs all descend from the EBOM, so this is the one worth getting right. Four steps.

Set your custom properties before you start typing

Open a part, go to File > Properties, and confirm you have Part Number, Description, Material, and Revision as custom or configuration-specific properties. If they are inconsistent across the assembly, fix that first. Copying a BOM out of a model with half-populated properties just moves the mess into Excel.

Decide what counts as a line

Toolbox fasteners, weldment cut lists, and purchased subassemblies all need a rule. A common one is to roll Toolbox hardware up to a single line per size and treat purchased subassemblies as one buy item rather than exploding the supplier’s tree. Write the rule down once, in the Notes column, so the next engineer follows it.

Handle configurations deliberately

If the assembly has configurations, decide whether you are documenting one build or the family. One build goes in the EBOM tab. The family belongs in the CBOM tab, referenced by configuration name. Mixing the two produces a BOM that is wrong for everybody.

Cross-check against the drawing

Your .SLDDRW already carries a BOM table. Compare quantities line by line. Where the drawing table and your spreadsheet disagree, the model is right and the spreadsheet is stale, which tells you how old your copy is.

Where a spreadsheet BOM stops keeping up

Templates are the right tool for a first pass, a quote, or a product you touch twice a year. They run out of road in four predictable places.

• The BOM ages the moment the model changes. An engineer adds a bracket at 4pm and the spreadsheet still says 14 parts. Nothing tells anyone.
• Copies multiply. BOM_v3_final_JM.xlsx on a shared drive, another in an email thread, a third in the buyer’s downloads folder.
• Quantities get counted by hand. Sixteen M4 screws across three subassemblies is an easy number to get wrong, and an expensive one.
• Nobody can prove which revision was released. When a customer asks what shipped in March, the answer is a search through file names.

These are the same pressures that push teams into a formal engineering change order process, and they are worth understanding before you decide the spreadsheet is fine.

When you can stop filling these in

At some point the honest answer is that the BOM is not a document you maintain at all. It is a view of the assembly, generated from the model and refreshed on every check-in.

You check in your assembly directly in SolidWorks and the BOM is already there. BOM management in Sibe reads the references and builds an indented BOM, with Filename and QTY populated from the assembly itself. Every new version you check in refreshes it. Here is what that changes day to day:

• Quantities counted from the assembly references, so nobody tallies parts by hand
• Your existing SolidWorks custom properties mapped to BOM columns — part numbers, materials, descriptions, finishes
• Check out the BOM to add packaging, fasteners, adhesives or grease, then check it back in; Undo Check-Out discards the edits
• Export to Excel (XLSX) or CSV from the Web Dashboard when purchasing or a supplier wants a file
• Editors and Contributors generate, view, edit, and export BOMs; Viewers see them read-only

Straight about the scope, so nothing surprises you in a trial: the current release builds one indented BOM from the assembly’s Default Configuration, all BOM work happens in the Web Dashboard, and it carries a Feature Preview label in-product. BOMs are on the Business Plus plan, alongside automatic version control for SolidWorks.

You still get a spreadsheet when you need one. You just stop being the thing that keeps it accurate.

If you are comparing options first, our rundown of the top 10 Bill of Materials software tools is a reasonable place to start.

Frequently asked questions

Are these BOM templates really free?

Yes. Download the workbook, use it, and share it with your team. No email gate, no account.

Which BOM template should I start with?

The EBOM. Every other BOM in the workbook cross-references its part numbers, so getting the engineering view right first saves rework in the other four tabs.

Can I generate a BOM from a SolidWorks assembly automatically?

Yes. SolidWorks produces a BOM table inside a drawing, which works well for a released drawing but not as a shared list everyone reads. For a BOM that lives outside the drawing and refreshes on its own, Sibe builds an indented BOM from the assembly on check-in and updates it with every version.

What is the difference between an EBOM and an MBOM?

The EBOM describes the product as designed and follows the CAD structure. The MBOM describes the product as built and follows the production sequence, adding consumables and packaging that never appear in the model.

Do I need custom properties set up in SolidWorks before I use these templates?

Not for the spreadsheet. You can type the values in. If you want them populated automatically, you need Part Number, Description, Material, and Revision as custom properties in your parts. In Sibe, every BOM starts with Filename and QTY out of the box, and custom properties are optional columns on top of that.

Can I add items that are not modeled in SolidWorks?

In the templates, add a row. In Sibe, check the BOM out, add rows for packaging, fasteners, or adhesives, edit quantities where needed, and check it back in.

What file format are the templates?

A single .xlsx workbook with six tabs. It opens in Excel, Google Sheets, and LibreOffice. Formulas for extended cost and net price are already in place.

Where Sibe fits

Templates get a small team a long way. What they cannot do is tell you the model moved. Sibe puts the parts list on the same footing as the CAD:

• Check-in and check-out directly in SolidWorks, with every version tracked automatically
• Indented BOM built from the assembly’s own references at check-in, quantities counted for you
• Assembly references resolved automatically, including parts shared across projects
• Free public share links and QR codes — a technician, buyer or client opens the model in any browser, with no account and no viewer install
• Revision and approval workflow, with an audit trail of what was released and when

Live in under 20 minutes. No servers, no VPNs, no admin hassles.

Book a free 20-minute demo or try Sibe free for 14 days — no credit card.