How OpenBOM for NetSuite connects to Oracle NetSuite
Embedded NetSuite integration
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.
REST API (push)
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.
What data moves
| From | To | Data | When |
|---|---|---|---|
| CAD tool (e.g. SOLIDWORKS) | OpenBOM | Assembly structure, part numbers, quantities, properties | Engineer publishes or syncs the BOM |
| OpenBOM | NetSuite | Assembly items and their BOM lines | Push from OpenBOM or pull from the Engineering tab |
| OpenBOM | NetSuite | Component items, descriptions and custom properties | Same BOM transfer |
| NetSuite | OpenBOM | Existing item numbers so parts are matched not duplicated | Mapping or lookup before transfer |
Setting it up
- 1Confirm licensingOpenBOM for NetSuite is a paid add-on. Confirm the OpenBOM plan and the NetSuite roles needed for the integration user.
- 2Install and authoriseFollow the OpenBOM user guide to connect your NetSuite account and grant the integration role the permissions it lists.
- 3Choose push or pullDecide whether engineers push BOMs from OpenBOM or whether planners pull them from the Engineering tab, and document who owns the release.
- 4Map propertiesMap OpenBOM columns to NetSuite item fields and custom fields, including item type, UoM and class.
- 5Settle part numberingMake sure CAD part numbers match the NetSuite item naming convention before the first transfer.
- 6Test in a sandboxTransfer a multi-level assembly and verify every level and quantity in NetSuite.
- 7Define the re-release ruleDecide what happens when a BOM that already exists in NetSuite changes in CAD.
What usually breaks
- !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.
A private AI layer across both systems
Part number cleanup
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
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
After a re-release, it summarises what changed between the NetSuite BOM and the latest CAD BOM.
Try it here, free
NetSuite Assembly Build Checklist
A pre-build and post-build checklist for NetSuite assembly items and work orders, covering setup, inventory and costing checks.
When something else fits better
- 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.
Frequently asked questions
Which CAD tools does OpenBOM read?
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?
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?
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.
Pairing documented at help.openbom.com/users-guide-openbom-for-netsuite/ . OpenBOM for NetSuite is a product of OpenBOM; Netray is independent and not affiliated with either vendor.