Certified SOLIDWORKS® Solution Partner|Built for SOLIDWORKS and SOLIDWORKS PDM Professional|Free Community Edition, no key needed

Product features

ERP Sync: Push SOLIDWORKS Items and BOMs to Odoo, ERPNext, Business Central

ERP Sync in PDMPublisher for SOLIDWORKS pushes items, properties, files and BOMs to Odoo, ERPNext or Business Central, and pulls ERP fields back through a reviewed diff.

Engineering finishes a design. Someone then re-types part numbers, descriptions and the bill of materials into the ERP, and a few weeks later the ERP description is the right one and the SOLIDWORKS property is stale. ERP Sync in PDMPublisher for SOLIDWORKS removes the re-typing in both directions. Push creates or updates ERP items, mapped fields, attachments and BOM relationships from the rows you check. Pull shows mapped ERP values as a diff before writing them into SOLIDWORKS custom properties. Official connectors exist for Odoo, ERPNext and Microsoft Dynamics 365 Business Central, and a C# contract lets you build your own.

ERP Sync window listing 52 checked assembly component rows with thumbnail, item, material, configuration and quantity columns, the BOM type and column template selectors at the top, and the connector selector, Pull and Push buttons at the bottom
The ERP Sync window: check the rows to send, pick the connector at the bottom, then Push or Pull.
Official connectorsOdooERPNextMicrosoft Dynamics 365 Business Central+ your own C# connector

What has to move

An ERP needs three things from CAD, and they arrive in this order.

  • Items. One ERP item per part and sub-assembly, keyed on a stable code. ERP Sync matches on one Item code column, by default the PartNumber property, compared exactly to the ERP item code or Internal Reference. Get that right and every later push updates the same items instead of creating duplicates.
  • Item data. Description, weight, material, sales and purchase flags, custom fields. In SOLIDWORKS these are custom properties; ERP Sync maps each one to a named ERP field.
  • The BOM. Which components go into which assembly, and how many. Odoo and ERPNext receive a manufacturing BOM per checked assembly; Business Central does not expose BOM endpoints in its standard API.

How ERP Sync works

The Odoo connector in action: connect, map, review, push.

The free Odoo connector ships with PDMPublisher for SOLIDWORKS: connecting the vault, mapping properties and pushing items with a review step.

ERP Sync lives inside SOLIDWORKS under the PDMPublisher tab. It reads the open document as a grid: the feature tree, a SOLIDWORKS BOM table, or a CSV file from purchasing. You filter and group the rows, tick the ones to send, pick a connector at the bottom of the window, then Push or Pull.

  1. Open or activate a saved part, assembly or drawing and select PDMPublisher > ERP Sync.
  2. Choose the source at the upper left: Feature tree, a BOM table and configuration, or a CSV file. Shape the view with BOM type, column template, Group by and Ignore Components.
  3. Check the rows to include. Only checked, visible rows are sent; expand collapsed branches before pushing an indented BOM.
  4. Select the connector and run Push or Pull. Review the plan, then commit or apply.
  5. Read the ERP Sync report, fix any failed item, and save the modified documents.
ERP Sync window with BOM type Parts only, Column template Default, four checked part rows for speaker frame, magnet, membrane and second_speaker with Material, Configuration and Quantity columns, the ERPNext connector selected at the bottom, and Pull and Push buttons
A parts-only view ready to push four items to the ERPNext connector.

Mapping properties without surprises

Connector settings live under Settings > ERP Sync > ERP connector settings. Each connector has a server URL, credentials for a dedicated integration user, a timeout, the Item code column and a list of property mappings. Load ERP fields asks the ERP which fields the integration user can write and lets you map a SOLIDWORKS property or an ERP Sync column to each one, using the field’s API name rather than its label.

Two rules keep it clean. Map each ERP field once. And leave Skip empty values on, so a blank property in SOLIDWORKS never erases something a buyer typed into the ERP. Connector settings are encrypted for the current Windows user and never travel with settings export or PIN sharing.

ERP connector settings dialog with the ERPNext connector listed under Official Blue Byte Systems Inc showing server version 1.0.1.0 and local version 1.0.0.0, Refresh, Download and Add new buttons, and a Connector settings grid with Server URL, masked API key and API secret, Timeout 60, Request missing part numbers and Item code column, plus Test connection and Save buttons
The connector catalog and the property grid for the selected connector. A newer server version enables Download.

Review, then commit

Nothing is written when you select Push. A review window lists every item, field, attachment and BOM line as Added, Changed or Deleted. On a first push of a small assembly that is a short list of additions; after a design change it is exactly the quantities that moved. When you select Commit changes, the connector re-reads the ERP first. If someone edited an item between your preview and your commit, the commit stops and you preview again. Plans are single-use.

Push operations are chosen per run: Properties updates mapped fields on existing items; Create items + properties also creates missing items; BOM sends the checked parent-and-child relationships (Indented view, no grouping); Include cut-list items turns weldment bodies into items. Uploads are optional: the SOLIDWORKS thumbnail and any STEP, DXF or PDF already published next to the model with the same base filename.

Pulling data back

A buyer fixes a description in the ERP; engineering wants it on the drawing. Pull reverses the mappings, reads the matching ERP items and opens Review ERP pull: green for Added, yellow for Changed, red for Deleted, and a reason on every skipped cell. Item codes, built-in columns, read-only documents and empty ERP fields are never overwritten. Apply to SOLIDWORKS revalidates and writes; Cancel writes nothing. Pull changes properties only, never assembly structure.

Review ERP pull window in PDMPublisher listing 13 proposed property changes from Odoo, with a changed Cost on the assembly and Cost values added on four parts, and the Apply to SOLIDWORKS button
The Pull diff against Odoo: one Cost value changed on the assembly, four added on parts, nothing written until Apply to SOLIDWORKS.

The three connectors

ConnectorSign-inWhat it syncs
Odoo (19+ or Odoo Online, JSON-2 API)Server URL and an API key of a dedicated integration user with the rpc scope. Optional database name for multi-database servers.Products keyed on Internal Reference, mapped product fields including writable x_ custom fields, thumbnail and file attachments, manufacturing BOMs with additions, removals and quantity changes.
ERPNextServer URL, API key and API secret of an integration user.Items with item group and stock UOM, mapped and custom_ fields, private attachments, a managed draft BOM per source file. Can generate missing part numbers from a naming series and write them back to SOLIDWORKS.
Microsoft Dynamics 365 Business Central (Online, API v2.0)Tenant, environment, company and a Microsoft Entra application with a client secret.Items keyed on item number with mapped fields such as display name, category, unit price and posting groups, with ETag revalidation. No BOM sync, attachments or number generation.
Your own connectorWhatever your settings class declares.A C# class library (.NET Framework 4.7.2) derived from ErpConnector<TSettings> in PDMPublisher.ERPExtension.dll. Advertise only the capabilities you implement and it appears under Custom in the connector catalog.

Test every connector against a sandbox company or non-production database first. Connectors stop on the first API error and do not retry or roll back, so after a timeout check the ERP before pushing again.

A sensible rollout

  1. Create a least-privilege integration user and its API key, and point the connector at a test database.
  2. Pick an item code that never changes. If your files are named by part number, the file name without extension is a good choice.
  3. Map three or four fields, no more. Push with Create items + properties on a Parts only view and check the items in the ERP.
  4. Add BOM and push again on the Indented view. Compare the ERP BOM with the SOLIDWORKS tree.
  5. Use Ignore Components for hardware and purchased parts that should not become ERP items, then turn on thumbnail and file uploads once the data is right.
  6. Run it from a macro when it becomes routine: publisher.ERPSync in Publisher Macros runs the same flow with the review step kept.

What it does not do

  • No inventory, pricing or stock levels; those stay in the ERP.
  • No creation of custom fields or missing item codes, except ERPNext naming series.
  • No BOM import from the ERP into SOLIDWORKS; Pull changes properties only.
  • No exports: attachments must already exist next to the model. Publish first.
  • Community Edition reviews and synchronizes up to 10 rows per operation; Premium removes the limit.

Availability

ERP Sync is an Integration command of PDMPublisher for SOLIDWORKS, the add-in that runs inside SOLIDWORKS. It needs a saved document and an installed, active connector. It is not part of the PDM Professional task.

Documentation and related features

Frequently asked questions

Which ERP systems does PDMPublisher ERP Sync support?

Official connectors are available for Odoo (19+ and Odoo Online, JSON-2 API), ERPNext, and Microsoft Dynamics 365 Business Central Online (API v2.0). A C# contract in PDMPublisher.ERPExtension.dll lets you build a custom connector for any other system.

Can ERP Sync push the assembly BOM to ERP?

Yes with Odoo (manufacturing BOMs) and ERPNext (managed draft BOMs). Use the Indented view without grouping and check the parent and its direct children. The Business Central connector does not support BOM sync because the standard API v2.0 exposes no BOM-definition endpoints.

Does Pull overwrite my SOLIDWORKS properties without asking?

No. Pull opens Review ERP pull, a diff of added, changed and deleted values with skip reasons. Nothing is written until you select Apply to SOLIDWORKS, and the plan is revalidated first.

Can ERP Sync upload STEP, DXF and PDF files to the ERP item?

Odoo and ERPNext connectors upload existing exported files whose base filename matches the model, plus the SOLIDWORKS thumbnail. Business Central does not support attachments. ERP Sync does not generate exports; publish them first.

How are items matched between SOLIDWORKS and ERP?

Through the Item code column, by default the PartNumber property, compared exactly to the ERP item code, Internal Reference or item number. ERPNext can also generate a missing number and write it back.

How many rows can the free Community Edition synchronize?

Community reviews and synchronizes up to 10 rows per operation. Premium removes the limit.

Where to next

PDMPublisher for SOLIDWORKS · PDMPublisher for PDM Professional · All features · Conversion guides · Pricing · Documentation · Contact

The SOLIDWORKS add-in is free to start as the Community Edition. The PDM Professional task comes with a 7-day trial. Download the add-in or start the task trial.