Objective: To inform Clients how to set transfer their data from Duro to NetSuite through our native integration.
Difficulty: Easy
In this article:
- What Gets Created in NetSuite
- Video Demo of the integration
- How to initiate data transfer from Duro to NetSuite
- How Duro Handles BOMs and Their Children
- Data Delivery Architecture
Duro’s integration with NetSuite automates the creation and updating of inventoryItems, assemblyItems, and their associated BOMs directly through the Duro Change Order (CO) process. This ensures product data remains accurate and synchronized between systems, reducing manual entry and streamlining the handoff from engineering to operations.
What Gets Created in NetSuite
When a Change Order is approved in Duro and the integration is active, the following records may be created or updated in your NetSuite instance:
- inventoryItems – Represent individual components or purchasable parts.
- assemblyItems – Buildable items that consist of components (i.e., a BOM).
- BOMs – Define the structure of an assembly, including components and quantities.
Each item is created using the appropriate NetSuite itemType, based on data in Duro:
- Standard: Basic inventory item without tracking.
- Serialized: Item tracked by unique serial numbers.
- Lot Numbered: Item tracked in bulk by lot/batch number.
Triggering Item and BOM Creation
The integration is driven by the approval of a Change Order in Duro. Once approved:
1. inventoryItems and/or assemblyItems are created or updated in NetSuite.
2. BOMs are created or updated for assemblies.
3. Custom fields can be mapped using the integration wizard.
BOM Effectivity Date
You can set a BOM Effectivity Date when pushing a Change Order from Duro. This determines when the BOM becomes active in NetSuite. If no date is set, NetSuite uses the BOM’s creation date.
Key Benefits
- Automated record creation
- Accurate inventory tracking via correct item typing
- Controlled BOM activation via effectivity dates
Video Demo: Duro to NetSuite Integration
Initiating a Data Transfer from Duro to NetSuite
Duro’s integration with NetSuite is triggered by the approval of a Change Order (CO). When a CO is submitted and approved in Duro, the integration automatically pushes relevant item and BOM data to your NetSuite instance.
This process ensures that inventoryItems, assemblyItems, and BOMs in NetSuite stay aligned with your latest engineering data from Duro—without the need for manual exports or re-entry.
What Data Is Transferred?
For each item listed on an approved Change Order, the following attributes are sent to NetSuite:
CPN → itemID
Name → displayName
_id → externalID
(Unique Component ID shared across all integration systems)Description → Description
Revision → BOM Name
- subsidiaryID
- taxSchedule
In addition, you can map custom fields or other metadata from Duro to NetSuite using the Field Mapping options in the integration wizard. This supports syncing of fields like assestAccount, cogsAccount, MPN, UPC Code, and more.
Submitting a Change Order in Duro
To initiate the data transfer, follow these steps to create and approve a Change Order in Duro:
-
Log in to Duro
-
Go to:
- MFG: for https://www.mfg.duro.app
- ITAR: for https://www.app.govduro.us
- EU: for https://www.eu.duro.app
and sign in to your account.
-
-
Select an Items to Tranfer
Choose an Assembly or Component to use for the Change Order:From your Duro dashboard
From your Library
Using the Search bar
-
Initiate a Change Order
Click the Change Order icon (upper-right toolbar).
-
Choose a Change Order type:
ECO – Engineering Change Order
MCO – Manufacturing Change Order
DCO – Document Change Order
Enter a Name for the Change Order.
(Optional) Add a Description.
(Optional if an Assembly) Click Add Children to include Child Components and Sub-Assemblies.
-
Submit and Approve
Click Submit for Approval.
Once the Change Order loads, click Approve.
(Optional) Add approval comments in the dialog that appears.
Confirm by clicking Approve again.
Confirm Data Transfer in NetSuite
After submitting and approving a Change Order in Duro, you can confirm that the corresponding items and BOMs have successfully synced to NetSuite by following the steps below:
Log in to your NetSuite account.
Use the Search Bar at the top of the page and paste in the CPN of the item you pushed from Duro.
Click on the matching result to open the item's record.
Navigate to the Manufacturing tab (for assemblyItems) to review the BOM details.
You should now see the following fields populated based on data sent from Duro:
itemType
- itemID
- displayName
Description
- BOM Quantity (for assemblyItems)
Effective Date (for assemblyItems)
Obsolete Date (for assemblyItems)
- and more...
If you’ve configured additional field mappings via the integration wizard, those will also appear on the relevant tabs or custom fields section of the record.
How Duro Handles BOMs and Their Children
When syncing assemblyItems and their associated BOMs to NetSuite, the integration uses specific rules based on whether child components are included in the Change Order:
| Scenario | Result in NetSuite |
|---|---|
| Child is not on the Change Order & does not exist in NetSuite | The child will not be created or referenced in the BOM. |
| Child is not on the Change Order but does exist in NetSuite | The child will not be updated, but will be referenced on the BOM in its last released state. |
| Child is on the Change Order & does not exist in NetSuite | The child will be created and referenced on the BOM. |
| Child is on the Change Order & does exist in NetSuite | The child will be updated, and its updated state will be referenced on the BOM. |
🔄 You can also define a BOM Effectivity Date during Change Order submission to control when the BOM becomes active in NetSuite.
Do so via the ERP Options drop down and toggle Set Effectivity. Simple choose the relevant dates.
Data Delivery Architecture
The Duro-to-NetSuite integration uses a combination of webhooks and REST API to manage data transfer. Webhooks trigger the integration on Change Order approval, while the REST API securely transmits the full data payload to NetSuite.
This approach ensures timely, reliable, and scalable synchronization between systems.
Comments
0 comments
Article is closed for comments.