Integrations
Fits the systems you already run.
Cadxor keeps your ERP as the system of record and your CAD system for design work. Integrations move released configuration data between them — starting with NetSuite.
| System | Category | Status | What moves |
|---|---|---|---|
| Oracle NetSuite | ERP | Available · dry-run | Configured items, BOM members, customers, estimates, file references; sales orders and status on the roadmap |
| Any system via webhooks & REST API | API | Available | Signed events for configurations, approvals, jobs, quotes and ERP syncs |
| Microsoft Dynamics 365 | ERP / CRM | Planned | Items, BOMs, quotes, sales orders |
| SAP S/4HANA, Business One | ERP | Planned | Material masters, BOMs, sales documents |
| Epicor Kinetic | ERP | Planned | Parts, methods, quotes, orders |
| Acumatica · Odoo · Infor · Oracle Fusion | ERP | Planned | Same operation model as NetSuite |
| Salesforce · HubSpot | CRM | Planned | Configuration from opportunity; drawing and quote back to the opportunity; stage updates |
| Autodesk Vault · SOLIDWORKS PDM · Fusion Manage · Teamcenter · Windchill | PDM / PLM | Planned | Released component revisions in; generated, revision-aware outputs back |
| FreeCAD / OpenCascade | CAD engine | In use | STEP import, parametric generation, assembly, STEP export |
| Autodesk Inventor | CAD output | Optional · your licence | Native IPT/IAM generated on the CAD worker |
| DWG via ODA File Converter | CAD output | Optional · licence required | DWG from the generated DXF |
Example CRM → ERP flow
From opportunity to sales order, one record throughout.
- A sales opportunity is created in the CRM.
- The salesperson opens Cadxor from the opportunity and configures the assembly.
- Cadxor validates it and generates the model and drawing.
- The drawing and estimate are attached back to the opportunity.
- The customer approves the drawing through a secure link.
- The CRM stage updates and the ERP sales order is created.
Steps 1, 4 and 6 need the CRM connector, which is on the roadmap. Steps 2, 3 and 5 work today.
Integration principles
- Your ERP stays the system of record for items, customers and orders
- Every operation is idempotent and logged with request and response
- Dry-run mode shows exact payloads before anything is written
- Credentials live in a secrets manager, never in the database
- Field mappings are configured per customer, not hard-coded
Running NetSuite?
We will map one configured product family into your NetSuite records in dry-run mode, so you can review every field before anything is written.