Duration: 18:49
PART 1 — Analytical Summary
Context 🚀
Presented by Teros Salonan from ATROFT (a Finland-based software company specializing in industrial software, integrations, and support), this session showcases a practical integration between SolidWorks and Odoo. The aim is to bridge CAD/PDM/PLM workflows with business processes in ERP to avoid data silos and automate downstream handoffs. After a brief company intro (700+ industrial projects, deep CAD/ERP integration expertise), the talk moves into a live demo connecting product design in SolidWorks to product and BOM management in Odoo Manufacturing.
Core Ideas & Innovations ⚙️
The integration centers on using a SolidWorks add-in (referred to as CustomTools) that synchronizes product master data, BOMs, documents, and key attributes with Odoo via remote calls. Designers can create parts in CAD using predefined numbering sequences and compose dynamic descriptions from CAD parameters (e.g., diameter, length), ensuring descriptions auto-update if the model changes. Critical master data like product categories, units of measure, and routings are not duplicated: they are pulled live from Odoo picklists, so lists are maintained in one place.
On export, the tool creates or updates Products and BOMs in Odoo, along with preview images and manufacturing documentation. Native CAD drawings are converted to PDF and attached to the product; additional file types (e.g., STL for 3D printing, DXF for laser cutting) can be included. The integration supports field-level “mastership”: for each attribute, teams can define whether CAD or Odoo is the system of record. A change-detection UI highlights differences (e.g., cost updated in Odoo) and lets users accept imports back into SolidWorks when Odoo is the master.
For assemblies, the tool computes BOMs with rule-based behavior. For instance, if a component is flagged as “purchased,” it won’t generate a product in Odoo, keeping the BOM clean. It also respects Odoo-side additions: if manufacturing adds a label or glue in the Odoo BOM that isn’t modeled in CAD, designers can choose “do not remove” during export to preserve those lines. Conversely, the add-in supports “virtual items” on the CAD side—letting users insert existing Odoo products (e.g., a packaging box) into the CAD BOM without creating a 3D model. The integration works both in basic SolidWorks and within SolidWorks PDM: exports can be triggered automatically on PDM workflow transitions or manually without needing a full SolidWorks license.
Impact & Takeaways 💼
This integration brings design-to-business continuity: fewer manual entries, less duplication, and more accurate data across CAD, PDM, and ERP. Designers benefit from dynamic descriptions and weight/material synchronization; manufacturing gains instant access to up-to-date BOMs and attachments; purchasing can safely own cost fields in Odoo while keeping designers informed through controlled sync. The live picklists and per-field mastership reduce errors and rework. Document automation (CAD-to-PDF) and rules (skip purchased items, protect Odoo-only lines) align engineering reality with operational needs, accelerating handoff to production while preserving governance.
Key takeaways: - Single source of truth for lists and routings in Odoo, consumed live in SolidWorks 🧠 - Automated product/BOM creation with controlled data ownership per field - End-to-end documentation flow: CAD → PDF → attached to Odoo products - Mixed-model BOMs supported: CAD-modeled parts, Odoo-only lines, and CAD-side virtual items - PDM workflow integration for hands-free, state-driven publishing
Taken together, the approach simplifies ERP adoption for engineering teams, lowers integration friction, and improves PLM-to-ERP continuity—without forcing designers to leave their native tools. 💬
Viewpoint: Odoo Perspective
Disclaimer: AI-generated creative perspective inspired by Odoo’s vision.
The value here is not just an integration—it’s a demonstration of what happens when information flows without friction. When designers trust that Odoo is the single source for categories, routings, and cost, and Odoo trusts the CAD model for geometry-based attributes, we unlock a simpler way to run operations. That’s the spirit of Odoo: make the complex feel obvious.
I appreciate the attention to details like protecting Odoo-only BOM lines and allowing virtual items. These choices respect how companies really work. Integration should adapt to teams and processes, not the other way around. And when we keep everything in one coherent platform, the community can build on it and move faster together.
Viewpoint: Competitors (SAP / Microsoft / Others)
Disclaimer: AI-generated fictional commentary. Not an official corporate statement.
This is a thoughtful, practical bridge from engineering to ERP. Field-level mastership, document publishing, and rules around purchased items address real pain points. For mid-market manufacturers aiming for speed and usability, this approach is compelling—particularly the UX that keeps designers in their comfort zone.
At larger scale, governance, compliance, and lifecycle control (ECR/ECO, versioning, auditability) become critical. The integration will need strong alignment with PLM processes, quality management, and regulatory frameworks. Enterprise depth—across multi-company structures, segregation of duties, and change control—will be the differentiation arena. Still, as a UX-forward path to integrated BOMs and documents, it sets a high bar for usability that the market will notice.
Disclaimer: This article contains AI-generated summaries and fictionalized commentaries for illustrative purposes. Viewpoints labeled as "Odoo Perspective" or "Competitors" are simulated and do not represent any real statements or positions. All product names and trademarks belong to their respective owners.