NetSuite Field Mapping

Objective: To provide Clients with a comprehensive list of NetSuite fields that can be mapped from Duro, enabling Controllers and Finance teams to run a proper gap analysis.

Difficulty: Easy

In this article:

1. What Fields Can Be Mapped from Duro to NetSuite

2. Using Custom Fields

3. Example Mapping Strategy

4. Key Benefits

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 Fields Can Be Mapped from Duro to NetSuite

When a Change Order is approved in Duro, you Initiate a Data Transfer from Duro to NetSuite. The integration supports mapping of the following standard NetSuite fields. This list is most commonly used by Controllers for financial and compliance reviews:

Subsidiary
Tax Schedule

GL Accounts

• Asset Account

• COGS Account

• Customer Return Variance Account

• Deferral Account

• Deferred Revenue Account

• Drop Ship Expense Account

• Gain/Loss Account

• Income Account

• Inter-Company Deferred Revenue Account

• Inter-Company COGS Account

• Inter-Company Income Account

• Revenue Reclass FX Account

• Vendor Return Variance Account

Item Attributes

• ItemNumber* (currently CPN only)

• Display Name*

• Description*

• Purchase Description

• Weight

• Supply Type

• Minimum Quantity

• Cost

• Manufacturing

• PMN (Part Manufacturer Number)

• Vendor Name

• UPC Code

• Lead Time

• externalID (commonly used as the lynchpin for mapping strategy)

Units of Measure

• Base Unit

• Stock Unit

• Purchase Unit

• Sales Unit

• Consumption Unit
   

Using Custom Fields

In addition to the standard fields listed above, you may map any field with a callable name.
For example:

• customItem1

• customItem2

This allows flexibility for company-specific metadata, such as compliance tags, financial codes, or operational notes.
 

Example Mapping Strategy

Fields marked with an asterisk (*) — such as ItemNumber and Display Name — are always mapped over to NetSuite.

For all other fields (those without an asterisk), you can decide when and how they should be pushed to NetSuite. Currently, the integration offers two toggle options for these fields:

1. Push on Create

   • When enabled, the field’s value is sent to NetSuite when the item is first created.

   • Example: Creating a new inventoryItem with its Cost or Vendor Name already populated.

2. Push on Update

   • When enabled, the field’s value is updated in NetSuite whenever it appears directly on a Change Order.

   • Note: This does not apply if the item only appears as a nested child in a Change Order. See How Duro Handles BOMs and Their Children.

Combined Behavior

• Both toggles on → The item is created with the field populated, and it stays continuously updated with future Change Orders.

• Neither toggle on → The field is never pushed by Duro. In this case, you can rely on NetSuite workflows or manual updates to manage those attributes instead.

This flexibility allows Finance and Operations teams to choose whether Duro should be the system of record for a given attribute, or whether NetSuite should remain the source of truth.

Key Benefits

• Complete Financial Visibility – Controllers can validate whether all necessary financial attributes are flowing from Duro to NetSuite.

• Configurable – Standard mappings cover most use cases, while custom fields allow for company-specific extensions.

• Audit-Ready – Ensures consistent and traceable item and account information across Engineering, Operations, and Finance.