USD
CAD
EUR
GBP
AUD
NZD
CHF
SEK
NOK
JPY
CNY
INR
SGD
MXN
BRL
ZAR
KRWSOLIDWORKS ERPNext integration, inside SOLIDWORKS
PDMPublisher ERP Sync creates ERPNext items, fills their fields from your custom properties and builds the bill of materials from the open assembly. You review every change before anything is written.
No middleware, no cloud service in between and no custom code to maintain.
ERPNextSOLIDWORKS property
ERPNext field
What goes from SOLIDWORKS to ERPNext
Choose any combination on each push. The assembly stays the source, and ERPNext receives exactly what the feature tree says.
- Items
- Missing parts and assemblies are created as ERPNext items, using an item code you choose, such as the file name or a part number property.
- Fields
- Custom and configuration properties such as description, material, weight or vendor fill the ERPNext fields you map them to.
- Bills of materials
- The assembly structure becomes an ERPNext BOM for the parent item, with every component and quantity.
- Cut lists
- Weldment and sheet metal cut list rows can be sent as their own lines.
- Files
- Optionally, part thumbnails and exported STEP, DXF or PDF files are attached to the item.
How a push works
Set up the connection and mapping once. After that, every sync is three clicks, and nothing reaches ERPNext until you approve it.
Map properties to ERPNext fields
Click Load ERP fields and PDMPublisher reads the field list from your ERPNext database, so you pick real field names instead of guessing. Pair each SOLIDWORKS property with its ERPNext field and save. The mapping is reused on every push.
Review every change
Push compares the assembly with ERPNext and lists each item, field and BOM line it would add, change or remove. Skip empty values keeps a blank SOLIDWORKS property from wiping out something purchasing typed in ERPNext.
Commit and check the BOM in ERPNext
Commit writes the changes, after checking ERPNext once more so nobody overwrites a colleague’s edit. The items and the BOM are ready in ERPNext Manufacturing. Pick ERPNext from the connector list next to Pull and Push, and switch to another connector at any time.
Works with your ERPNext
If your SOLIDWORKS computers can reach your ERPNext site, ERP Sync can connect to it.
Frappe Cloud
Hosted sites such as yourcompany.frappe.cloud.
Self hosted ERPNext
Any ERPNext site reachable from your network.
API key sign in
Connects with an ERPNext API key. No user password is stored or sent.
One connector per site
Point the connector at the ERPNext site you use.
Not sure about your setup? Book a short call and we will check it with you.
PDMPublisher or a custom integration?
A custom connector has to read assemblies, configurations and cut lists, handle ERPNext field types, avoid overwriting data and keep working through every SOLIDWORKS and ERPNext upgrade. The build quote is rarely the real cost.
| PDMPublisher ERP Sync | Custom integration | |
|---|---|---|
| Time to first sync | ✓The same day | Weeks to months of development |
| Upfront cost | ✓None. Try the free Community Edition first | A development project |
| Review before writing | ✓Built in | ✕Only if you pay for it |
| SOLIDWORKS and ERPNext upgrades | ✓Maintained by Blue Byte Systems | ✕Your cost, every time |
| Other ERPs | ✓Odoo and Business Central connectors included | A new project per ERP |
| Also included | ✓Publishing to PDF, DXF and STEP, BOM Manager, Smart Pack and Go, Property Doctor | Only the integration |
What three years can cost
An example for three engineers. The custom build assumes a developer at US$120 per hour, 120 hours to build and test, and 20 hours a year of upgrades. Replace the numbers with your own quotes.
Pricing
ERP Sync is part of PDMPublisher for SOLIDWORKS, with publishing, BOM Manager, Smart Pack and Go and Property Doctor included.
Community
ERP Sync and BOM Manager on up to 10 rows. Enough to try a small assembly against your ERPNext.
Single seat
Every tool with no row limits, for one engineer.
Team, 2 to 4 seats
The most common choice for engineering teams.
Department, 5 or more
For larger teams rolling ERP Sync out across the company.
Guides
Questions
Do I need SOLIDWORKS PDM to sync with ERPNext?
No. ERP Sync runs inside SOLIDWORKS on the open assembly. SOLIDWORKS PDM is not required.
Does it create new products or only update existing ones?
Both. Choose Properties to update existing products, or Create items and properties to create the missing ones first.
Can it update a BOM that already exists in ERPNext?
Yes. The review lists every line that will be added, changed or removed before you commit.
Which SOLIDWORKS properties can I send?
Any custom or configuration specific property, plus values such as the file name and quantity. You choose the ERPNext field for each one.
Can I keep purchased hardware out of ERPNext?
Yes. Use Ignore Components for fasteners or purchased parts you do not want as ERPNext items.
What if we use another ERP?
There are official connectors for Odoo and Microsoft Dynamics 365 Business Central too. For anything else, ask us about a custom connector.
Push your first assembly to ERPNext today
Download the free Community Edition and try it on a test database, or book a demo and we will walk through your properties and BOM structure with you.