On this page

Onshape BOM to CSV, from assembly export to approved purchasing

To export an Onshape BOM to CSV, choose the structured or flattened view and use Export to CSV from the BOM table's overflow menu. Record the source version or release and configuration first. Reconcile quantities, item identities and revision applicability before approving the exported data for purchasing.

Use R-01 as a fictional example. One robot has two DM-100 A drive modules. Each contains a motor, a bracket and four SC-130 A screws. Two more SC-130 A screws mount the sensor. The correct robot total is ten screws, with two motors and two brackets.

The buyer also needs the selected harness drawing and an approved sensor source. A correct CAD count alone does not answer those release and sourcing questions.

Export an Onshape BOM to CSV with its source recorded

Follow the documented assembly BOM workflow with the source and output recorded together.

  1. Capture the Onshape document URL, assembly tab, selected version or release and configuration values.
  2. Choose structured or flattened view for the task. Record the shown columns, item properties and relevant exclusions.
  3. Use Export to CSV from the table's overflow menu, as described in the BOM-table documentation.
  4. Keep the CSV, export time and source record together. Record the engineering release decision separately from the download.

A structured view retains the assembly context. A flattened view supports total-item reconciliation, though the purchasing boundary still needs review. Onshape also documents bulk export of released items through Tab Manager. Use that when relevant to the associated released files, preserving the same source identity for the package.

Released properties can be read-only where Onshape's release rules apply. Review the appropriate source record and change process when a controlled property needs correction. Editing the exported CSV does not repair that property in the CAD release.

Place missing BOM items and purchasing fields under the right owner

Onshape documents non-geometric BOM items through company item setup in Professional and Enterprise plans. Confirm the team's plan, item setup and permissions. If a harness or purchased item belongs in the engineering assembly but has no useful model, represent it through that supported BOM mechanism and review it upstream. Avoid keeping a second unofficial list of design parts beside the assembly.

Purchasing information has a different owner. For SN-400 A, the approved synthetic manufacturer number SEN-X12, distributor SKU DIST-1204 and S-01 source relationship may be added in a reviewed sourcing view. Preserve the internal item identity and selected revision through that enrichment.

Manufacturing-only AD-900 adhesive or threadlocker, consumed at 2 mL per robot, belongs to the manufacturing view if it is process material rather than an engineering assembly item. The EBOM-to-MBOM guide explains that boundary. Adding it directly to a spreadsheet without an owner, quantity basis and approval would leave its authority unclear.

Perform three reconciliations on the exported table

Reconciliation R-01 check Discrepancy to resolve
Structure and quantities Two DM-100 A modules give two motors, two brackets and eight screws, plus two sensor screws A flattened list showing four screws may have lost the parent multiplier
Item identity and source SN-400 A remains the internal ID beside SEN-X12, DIST-1204 and S-01 A SKU in the internal-ID column prevents a clean match to the released item
Revision and applicability BOM-R01 A selects HR-300 A for 001–002, B selects HR-300 B for 003–005 An export of only B cannot represent the complete mixed pilot

Check the actual source before deciding why a count differs. A missing row might be an exclusion, an absent non-geometric item or an incorrect assembly relationship. Preserve the discrepancy and fix the responsible source. The template provides the expected R-01 relationships and totals for comparison.

Approve the mixed-pilot purchasing requirement

ECO-017 approves the harness strain-relief manufacturing improvement from serial 003. DW-HR-300 changes from A to B. The controlled installation interfaces and acceptance requirements stay the same. Mechanical reference DW-R01 A, ECAD CB-200 A and firmware 1.2.0 remain selected.

For the five-unit pilot, the released purchasing requirement is two HR-300 A and three HR-300 B. It also needs ten motors, ten brackets, fifty screws and five each of the PCBA, sensor and chassis plate. Build the ten drive modules in house. Buy the complete PCBA rather than buying its children again.

Attach BOM-R01 A/B, CFG-R01-A/B, ECO-017 and the applicable harness drawings to the purchasing authorisation. The buyer reconciles stock and open orders by revision before deciding the actual order quantities. At receipt, compare the delivered identity, revision and documentation with the authorised lines. Keep a mismatch visible for disposition.

Start with one assembly and have engineering and purchasing independently reproduce the totals from the same released export. Then use the configuration matrix to confirm which serial receives each harness. If evaluating another system downstream, ask it to demonstrate this exact reconciliation with the source record retained.

Move faster without compromising engineering rigour.

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