On this page

SOLIDWORKS BOM to Excel, checking configurations before purchasing

To export a SOLIDWORKS BOM to Excel, right-click the BOM table, choose Save As and select .xls or .xlsx in the documented 2026 workflow. Check the assembly, drawing-view and BOM-table configurations independently first. A correct-looking drawing can still produce a harness row for the wrong build.

For a small robotics team, this is a useful release check before adding another system. The drawing, assembly file and spreadsheet export should all describe the same approved build. Purchasing then needs explicit revision and serial applicability for its own handoff.

The example is R-01, a fictional indoor inspection robot. Each robot contains two DM-100 A drive modules, one PCBA, one harness, one sensor and one chassis plate. The harness advances from A to B under ECO-017 for serials 003–005. Serials 001 and 002 remain at A.

Check the assembly, drawing view and BOM configuration independently

Use a controlled source file reference and revision for the assembly. Record its selected CAD configuration and the product configuration that selection is intended to represent. A CAD configuration can select geometry and properties. The complete product configuration also identifies the BOM, drawings, electronics and firmware.

For a drawing, record the drawing file revision and the configuration referenced by the relevant view. Inspect the BOM table's configuration selection independently. Preserve the BOM type, shown columns and relevant component exclusions with the export record.

SOLIDWORKS documents top-level, parts-only and indented BOMs. Choose the type for the question being checked. An indented view helps trace the two drive modules into their children. A parts-only view helps reconcile bought parts, subject to the way components are represented and the chosen purchase boundary.

The 2026 help describes configuration-specific quantities and different controls for top-level, parts-only and indented BOMs. For a parts-only or indented assembly BOM, choose one configuration and verify it against the active view. Follow the edition's documented settings rather than assuming every BOM type displays configuration quantities in the same way.

Diagnose a configuration mismatch before editing the export

Suppose the drawing view represents the intended CFG-R01-B build, while the BOM table still selects the assembly configuration used for CFG-R01-A. The geometry may look unchanged because ECO-017 improves harness strain relief during manufacture and retains the installation interfaces.

The harness row is the useful discriminator. If the export selects HR-300 A and DW-HR-300 A for a serial-003 build, stop the purchasing handoff and inspect the source selections.

Inspection Expected B-release reference What to do if it differs
Assembly selection CAD configuration representing CFG-R01-B Select and inspect the intended source configuration
Drawing view reference The intended B configuration Resolve the referenced model/configuration in the drawing
BOM table selection The intended B configuration Correct the table selection through the controlled source workflow
Harness definition HR-300 B with DW-HR-300 B Inspect revision properties and linked source documents
Release record BOM-R01 B, ECO-017, serials 003–005 Obtain the applicable approval record before purchasing

A revision typed into the exported spreadsheet cannot establish that the source assembly and drawing were corrected. Preserve the mismatch, make the authorised source correction and export again. If the source selection is already correct, inspect the properties supplying the row and any configuration-specific values.

Export the SOLIDWORKS BOM to Excel and reconcile the result

After resolving the source selections, export the table using the documented 2026 Save As workflow.

  1. Record the SOLIDWORKS edition, BOM type, assembly and drawing references, and the configuration selected by the table.
  2. Right-click the BOM table and choose Save As.
  3. Select .xls or .xlsx, which are supported for table-based BOMs, and save the table with its export time and source record.
  4. Open the resulting file and check its columns, quantities and release references before adding purchasing information.

R-01's repeated assemblies provide a useful quantity check. Two DM-100 A modules give two MT-110 A motors, two BR-120 A brackets and eight SC-130 A screws. The sensor mount adds two more screws. A parts-only reconciliation should therefore account for ten screws per robot across those two contexts.

Also check whether non-modelled design items are represented by the approved source process. The purchased CB-200 A PCBA is ordered as a whole assembly. Its children must not become extra purchase lines merely because they are visible in engineering data. Keep manufacturing-only AD-900 consumable in the manufacturing view, with its separate 2 mL quantity basis.

Release a purchasing list for the actual pilot

A five-unit pilot spans BOM-R01 A and B. Its harness demand is two HR-300 A and three HR-300 B. Keep those revision groups separate during stock allocation, ordering and receipt reconciliation. The other gross requirements are ten motors, ten brackets, fifty screws and five each of the controller PCBA, sensor and chassis plate.

Attach the approval and applicability record to the purchasing instruction. Reference DW-HR-300 A/B as appropriate. DW-R01 A, ECAD CB-200 A and firmware 1.2.0 remain selected in both releases. The BOM revision and configuration guide supplies a matrix that makes those unchanged references visible.

Ask a second engineer to identify which configuration the BOM represents using the recorded source evidence alone. Then have purchasing reconstruct the two-A, three-B split before authorising the order. Use the R-01 template as the expected quantity fixture for this check.

Move faster without compromising engineering rigour.

Review one product release, its change decisions and supporting evidence with Arc.