# OpenBOM and Oracle NetSuite: from CAD BOM to assembly items

> Source: https://netray.co/stack/openbom-for-netsuite-cad-bom-integration
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

OpenBOM for NetSuite takes BOMs captured from CAD tools such as SOLIDWORKS and creates NetSuite assembly items and bills of materials. It offers push and embedded-pull modes, the latter through an Engineering tab inside NetSuite. It is a paid add-on and is a good fit for engineering teams without a full PLM.

## Erp

Oracle NetSuite

## Erp Key

netsuite

## On Prem

false

## Product

OpenBOM for NetSuite

## Vendor

OpenBOM

## Category

PLM / CAD BOM integration

## Integration

**Method:** Embedded NetSuite integration

**Detail:** OpenBOM's guide describes an Engineering tab inside NetSuite from which users can pull a BOM from OpenBOM into NetSuite items and BOMs, so planners do not have to leave NetSuite.

**Method:** REST API (push)

**Detail:** In push mode, OpenBOM sends the BOM and item data to NetSuite using its API integration with the NetSuite account. Both modes are vendor documented, but check the OpenBOM user guide for the current feature set before planning.

## Data Flows

**From:** CAD tool (e.g. SOLIDWORKS)

**To:** OpenBOM

**Data:** Assembly structure, part numbers, quantities, properties

**Trigger:** Engineer publishes or syncs the BOM

**From:** OpenBOM

**To:** NetSuite

**Data:** Assembly items and their BOM lines

**Trigger:** Push from OpenBOM or pull from the Engineering tab

**From:** OpenBOM

**To:** NetSuite

**Data:** Component items, descriptions and custom properties

**Trigger:** Same BOM transfer

**From:** NetSuite

**To:** OpenBOM

**Data:** Existing item numbers so parts are matched not duplicated

**Trigger:** Mapping or lookup before transfer

## Setup

### Confirm licensing

**Detail:** OpenBOM for NetSuite is a paid add-on. Confirm the OpenBOM plan and the NetSuite roles needed for the integration user.

### Install and authorise

**Detail:** Follow the OpenBOM user guide to connect your NetSuite account and grant the integration role the permissions it lists.

### Choose push or pull

**Detail:** Decide whether engineers push BOMs from OpenBOM or whether planners pull them from the Engineering tab, and document who owns the release.

### Map properties

**Detail:** Map OpenBOM columns to NetSuite item fields and custom fields, including item type, UoM and class.

### Settle part numbering

**Detail:** Make sure CAD part numbers match the NetSuite item naming convention before the first transfer.

### Test in a sandbox

**Detail:** Transfer a multi-level assembly and verify every level and quantity in NetSuite.

### Define the re-release rule

**Detail:** Decide what happens when a BOM that already exists in NetSuite changes in CAD.

## Pitfalls

- CAD part numbers that do not match existing NetSuite item names create duplicate items.
- Phantom or virtual CAD assemblies appear as stocked assembly items unless you handle them in mapping.
- Units of measure and quantity formats in CAD properties do not always match NetSuite units types.
- Re-pushing a changed BOM can overwrite edits that planners made directly in NetSuite.
- Custom NetSuite required fields on items block the transfer if they are not mapped.
- Multi-level assemblies need each sub-assembly to exist as an assembly item first.

## Ai Layer

### Part number cleanup

**Description:** A private model compares CAD part numbers with NetSuite item names and proposes matches and likely duplicates for an engineer to confirm before transfer.

### Transfer error explanation

**Description:** It reads failure messages and the BOM that triggered them, explains the missing field or item type in plain language, and drafts the correction.

### BOM difference review

**Description:** After a re-release, it summarises what changed between the NetSuite BOM and the latest CAD BOM.

## Alternatives

- If you already run Arena or another PLM with ECO control, use that instead of a CAD BOM tool.
- For a few assemblies, a CSV import of BOMs into NetSuite may be enough.
- A formal change process needs a PLM; OpenBOM alone is a BOM transfer, not a full engineering change system.

## Faq

### Which CAD tools does OpenBOM read?

**Answer:** OpenBOM documents SOLIDWORKS and several other CAD integrations. Check the current OpenBOM documentation for your CAD version, since supported tools and versions change.

### What is the difference between push and pull?

**Answer:** Push means an engineer sends the BOM from OpenBOM to NetSuite. Pull means a NetSuite user fetches it from the Engineering tab. Pull gives planners control of timing; push gives engineering control of release.

### Does it create assembly items automatically?

**Answer:** Per the vendor description, it creates NetSuite assembly items and BOMs from the OpenBOM data. You still need correct item naming, types and units so the result is usable for production.

## Source

https://help.openbom.com/users-guide-openbom-for-netsuite/

## Search terms

openbom netsuite integration, solidworks bom to netsuite, openbom netsuite assembly item, cad bom to netsuite, netsuite engineering tab openbom, import bom into netsuite

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json