What is SOLIDWORKS BOM management?

SOLIDWORKS BOM management connects the assembly a design team creates in SOLIDWORKS with the product information that engineering, manufacturing, purchasing, and suppliers need to use. The CAD assembly describes the designed structure. A complete BOM management workflow adds reusable Items, usage quantities, revisions, approvals, documents, costs, and downstream decisions without treating every export as the current product definition.

For an engineering-led manufacturer, the practical question is not only how to create a BOM in SOLIDWORKS. It is where the controlled product record should live, who can change it, which revision is approved for a build, and how the selected data reaches purchasing or an ERP system.

How do SOLIDWORKS, PDM, PLM, and ERP responsibilities differ?

System Primary responsibility Boundary to keep clear
SOLIDWORKS Design the mechanical assembly and generate design views or BOM information from CAD. A CAD assembly is not the complete product, purchasing, or business record.
PDM Control product files, versions, access, and design-document context. File control alone does not define every lifecycle decision or downstream transaction.
PLM Coordinate product information, revisions, changes, approvals, releases, and lifecycle collaboration. PLM scope varies by platform; a filtered BOM view is not automatically a manufacturing BOM.
ERP Run business processes such as orders, accounting, purchasing, and enterprise planning. An ERP connection publishes mapped data and still requires verification of the receiving result.

These responsibilities can work together. A team does not have to discard SOLIDWORKS or replace every business system to improve BOM control. The useful design is a clear handoff: CAD supplies design context, PDM protects files and versions, PLM or a product-data platform manages the product definition and decisions, and ERP receives the mapped information it owns.

What should SOLIDWORKS contribute to the product definition?

SOLIDWORKS should remain the source of mechanical design intent. Its assembly structure, referenced files, properties, and design changes are valuable inputs to the product record. The next step is to connect that design context to the other Items and records needed to build and buy the product, including electrical or PCB contributions, purchased parts, supplier information, and approved revisions.

That distinction prevents a common error: treating a file export as a live BOM. Excel, PDF, and ZIP exports are snapshots. If a design changes after an export, the downloaded file does not update with the workspace. The controlled workflow must identify the applicable revision and make the next action visible to the people using it.

How does OpenBOM connect SOLIDWORKS to downstream work?

OpenBOM is a cloud-native Product Data Management (PDM) and Product Lifecycle Management (PLM) platform for product information. For the documented SOLIDWORKS workflow, OpenBOM connects local and cloud CAD project state through SmartSync with synchronization, locking, versions, and revision context. Teams can organize reusable Items in catalogs, build multi-level BOMs, and keep product data available to collaborators beyond the CAD team.

OpenBOM also provides native BOM and xBOM capabilities, revision control and releases, change requests and ECO sign-off, formula-based cost rollups, simple inventory tracking, and Order BOM creation from a selected released revision. Supplier and contractor collaboration can use controlled sharing and real-time review. Engineering and manufacturing views should be treated as documented BOM views or configured data models, not as an automatic promise that every EBOM becomes an MBOM without decisions.

OpenBOM is not an ERP, accounting system, or full production-scheduling application. ERP connections vary by system and integration path. They publish mapped data, so the receiving result must be checked rather than assumed. Start a Free Trial to test a SOLIDWORKS-centered product-data workflow with your own process.

What does a SOLIDWORKS BOM management workflow look like?

The following is an illustrative workflow, not a customer result:

  1. Capture the design context. An engineer imports the relevant SOLIDWORKS structure and identifies the reusable Items, referenced files, and properties that belong in the product definition.
  2. Complete the product record. The team adds non-CAD Items, supplier or manufacturer identifiers, quantities in the correct BOM use, and related documents. An Item is a reusable identity, not a file or a row.
  3. Review the applicable revision. Engineering and manufacturing review the structure, comments, tasks, changes, and approvals. A file version, a product revision, and an approval are different records.
  4. Release the decision. The team releases the revision that applies to the build or purchasing action. If an Order BOM is needed, it is created from that selected released revision rather than from an unqualified export.
  5. Share mapped data and verify the handoff. Purchasing, suppliers, contractors, or an ERP system receive the information appropriate to their role. The team verifies the receiving result and records any follow-up instead of treating the integration as uniformly bidirectional.

This workflow lets a team adopt stronger product-data control alongside its existing CAD and business systems. It also makes ownership visible: SOLIDWORKS owns design intent, the product-data workflow owns the controlled product definition and collaboration decisions, and the ERP owns the business transactions assigned to it.

How should an engineering team evaluate SOLIDWORKS BOM management software?

Start with the handoffs that currently cause rework. Ask whether the system can preserve the SOLIDWORKS context, distinguish Items from files and BOM usage quantities, manage revisions and releases, support change decisions, and provide a controlled path to purchasing or ERP. Then check how the platform handles the second design update, a supplier correction, a non-CAD component, and a build that must use a specific released revision.

OpenBOM is designed for teams that want a shared product-data platform without making the CAD assembly, a spreadsheet export, or an ERP record carry responsibilities it cannot safely own. Compare the documented workflow with your current process and keep the boundaries explicit.

Start a Free Trial

Related OpenBOM resources

To the top