Typed twice
The assembly tree is a bill of materials. Someone reads it off one screen and types it into another. It happens on the first release, and again on every revision after it.
CAD to Odoo integration · Inventor, Solidworks, Solid Edge
CoreBOM reads the assembly structure straight from your CAD and pushes products, bills of materials and drawings into Odoo. No re-keying, no export files to babysit, no consultant on the clock.
Which CAD do you use?
Free trial runs 30 days, once per customer. No card, no meeting to book.
The cost of the gap
Every part you release is already fully described inside the model — structure, quantities, codes, materials. Between the CAD and the ERP that description gets rebuilt by hand, and that is where three costs appear.
The assembly tree is a bill of materials. Someone reads it off one screen and types it into another. It happens on the first release, and again on every revision after it.
A mistyped part code doesn’t announce itself. It travels quietly into purchasing and shows up as the wrong item on the shop floor, weeks later, when it is expensive to fix.
Engineering moves the design forward. The ERP keeps the version it was given. Production works from whichever one it happens to be holding.
From install to first BOM
Nothing here is a mock-up. This is the product running against a real Odoo database, recorded end to end.
Register, download the client, install it on the workstation that runs your CAD.
Your activation code arrives by email after purchase. Load it once, from the client’s own settings.
Point the client at your Odoo instance and sign in. On-premise or hosted, same procedure.
Open the assembly, send it. Product, bill of materials and drawings land in Odoo with the metadata already attached.
What travels
CoreBOM reads the assembly and writes structured records into Odoo — then reads them back. What crosses depends on the licence you pick.
Created on first push, updated on every one after. Codes, descriptions and properties come from the model, so the ERP record matches the part that was actually released.
The assembly tree becomes an Odoo BOM — created, updated, or revised. Revision handling bumps the index and writes a new BOM instead of overwriting the old one, the way Odoo’s own PLM module does.
Revision handling is optional: it needs one extra field in Odoo and a setting switched on in the client.
The drawing follows the part. Attached to the product record in Odoo, where purchasing and production can open it without asking engineering for a copy.
Neutral and native formats attached alongside the PDF, for suppliers and machines that need geometry rather than a picture of it. Includes the PDF attachments above.
Both directions
Most integrations stop at export: data leaves the CAD and never returns. CoreBOM reads records from Odoo and writes them into the model’s properties, so the ERP stays the single source of truth for codes and descriptions — and the designer sees them without leaving the CAD.
Included in every licence.
How we sell it
Most CAD–ERP connectors are sold as projects: the price arrives after a call, the demo after an appointment. CoreBOM is sold as a product. Here is what that changes.
| Criterion | CoreBOM | Typical alternative |
|---|---|---|
| Price | Published on this page | On request |
| Buying | Checkout, licence by email | Sales conversation |
| Trial | 30 days, self-service | Demo by appointment |
| CAD systems | Three | Usually one |
| Data direction | Both ways, included | Varies |
| Documentation | Public and complete | Limited |
Nothing above names a competitor, because the point isn’t who they are. It’s that you should be able to price a tool, try it, and decide — without putting a meeting in your calendar first.
Pricing
One licence, bought once. Below is every line item that exists — there is no second page.