NetSuite integration behaviour – Dotdigital Help Centre

Learn about the behaviour of the NetSuite integration for each of the data types it syncs.

Overview

The NetSuite integration syncs the following kinds of data:

For each of these kinds of data, there are certain behaviours that you should be aware of. These are listed in the relevant section below.

Only customers that are people entities with an email address in NetSuite are synced, company entities are ignored.
Customers should be deduplicated by email; duplicate customers are not synced.
We cannot sync contact deletions from Dotdigital to NetSuite.
Calculated fields cannot be synced, only stored fields can be synced
All email addresses are made lowercase.
The companyname field must be mapped to assign a new customer to the correct company.
The default billing address is exposed through the following fields for mapping purposes:
- addr1
- addr2
- addr3
- city
- country
- state
- zip
The status of a customer can be updated if the entitystatus field is mapped to a numeric field in Dotdigital that holds the customer status id.
When syncing back to NetSuite we will update a customer’s entitystatus with the default status for the customer stage if:
- The customer's current stage differs for the address book’s associated stage.
- We need to create a new customer record in NewSuite.
Email addresses are validated prior to synchronisation. Invalid email addresses cannot be processed.
We cannot update a record’s email address if it conflicts with an existing customer, because the NetSuite API prevents duplicate records.
If a NetSuite customer has their email address removed then any Dotdigital contact associated with this email address is deleted.
Calculated fields cannot be synced, only stored fields can be synced

Only contacts that are people entities in NetSuite and who have an email address are synced.
Contacts should be deduplicated by email; duplicate contacts are not synced.
We cannot sync contact deletions from Dotdigital to NetSuite.
Calculated fields cannot be synced, only stored fields can be synced
All email addresses are made lowercase.
It’s not possible to update a contact’s address in NetSuite from Dotdigital due to NetSuite API limitations.
The default billing address is exposed through the following fields for mapping purposes (read only):
- addr1
- addr2
- addr3
- city
- country
- state
- zip
Email addresses are validated prior to synchronisation. Invalid email addresses cannot be processed.
We cannot update a record’s email address if it conflicts with an existing contact because the NetSuite API prevents duplicate records.
If a NetSuite contact has their email address removed then any Dotdigital contact associated with this email address is deleted.

You can use either the NetSuite marketing subscriptions or a field to store opt in/out status.
A single configuration is used for both customer and contact entities.
We optionally allow the creation of a contact if we can’t find a match in NetSuite. This is to ensure that NetSuite has the opt out status for this email address.
Email addresses are validated prior to synchronisation. Invalid email addresses cannot be processed.

The NetSuite product catalog is named in this format:
catalog_<Parent company name><Company name><Country code>_NetSuite
Example:
catalog_ParentCompanyAcmeIncUS_NetSuite
Only active products are listed and synced initially.
Products that have no price mapped will not be included in the catalog.
When a product is flagged as inactive it will be removed from the catalog at next sync.
Custom multi-select fields cannot be mapped.
A fallback product URL can be set if we cannot map one from NetSuite.
A fallback product image URL can be set if we cannot map one from NetSuite.

Only orders that can be linked to an existing contact in Dotdigital are synced, therefore you should sync orders in conjunction with customer syncing.