Configure Order Data Exchange With NetSuite

To import NetSuite transaction data into Bronto as order data, configure the NetSuite Connector.

About this task

When a record is imported into Bronto, an Imported to Bronto custom entity field is added to the record in NetSuite. If the record changes in NetSuite, this custom entity field is turned off so that the record can be considered for the next import. Changes to the Imported to Bronto custom entity field will trigger a NetSuite SuiteFlow workflow or User Event Script that is set to run based on record changes, so you might want to add a condition to your NetSuite workflows that will prevent this from happening. See the Test NetSuite Data Imports section for steps on how to verify if there are potential conflicts. For more information about NetSuite custom entity fields see the NetSuite help topics and this NetSuite SuiteFlow topic for more information about NetSuite workflow conditions.

The Imported to Bronto custom entity field can also be used if you need to force an update of NetSuite data already imported into Bronto. If you change a NetSuite Connector mapping in Bronto, such as adding a new mapping, this change is only applied to future data exchanges. Because Bronto settings do not affect the NetSuite Imported to Bronto custom entity field, any previously imported record will have the custom entity field turned on, which means they won't automatically be imported using the new connector settings. If you want the new Bronto setting to be applied to previously imported records, you can use the NetSuite mass update functionality to turn off the Imported to Bronto custom entity fields so that Bronto will update all of these records, using the new Bronto settings, the next time an update runs. For more information about doing a mass update in NetSuite, see the NetSuite help topics.

In Bronto, this order data can be used to trigger workflows, market to contacts based on their order history, and to track RFM metrics.


  1. Go to Settings > Integrations > Connector.
  2. Locate the connector you want to work with and click its Edit link.
  3. Click Orders.
  4. Set Enable Connection to Yes.
  5. The Email Source field is used to define what email address an order should be attributed to when it is imported into Bronto. To set the Email Source:
    1. Select your source in the Email Source pull down.
      • Customer: The email address of the customer record associated with the transaction (sales order, cash sale, or invoice).
      • Primary Contact: The email address of the contact with the Primary Contact Role on the Relationship tab of the transaction record. This will only be set if there is a relationship.
      • Custom Field: Any other user-defined field that exists on the transaction record.
    2. If you have selected Custom Field, select your Custom Email Field.
  6. To set the import schedule:
    1. Select how often you want imports to run from the Frequency list.

      By default, imports are run in 1,000 record batches, so the frequency also determines the maximum number of records Bronto will attempt to import in a day. For example, if you set Frequency to Daily, the maximum number of record imports in a day will be 1,000. Inversely, if you set Frequency to once every hour, the maximum number of imports is 24,000 per day.

    2. Optional: If you selected Minute Intervals, select a number of minutes from the Import Every list.

      For example, if you select 30, imports will run every 30 minutes. We recommend 1 minute for the initial sync, and 15 minutes after that.

    3. Set a Start Time.
    4. Set an End Time.

      If you selected daily, you will not see an option to set an End Time.

    5. In the Days section, select which days of the week you want imports to run.

      If a day box has a check mark, the import will run on this day at the interval frequency you set.

  7. Click on the tab for the NetSuite transaction type you want to map:
  8. Set Enable Connection to Yes.
  9. Optional: If you want to limit the imported orders using a NetSuite saved search, select it from the Saved Search Filter list.
    In NetSuite, multiple modules should be turned on only when these transaction types are not in conflict to avoid order duplication in Bronto. Turning on Sales Orders alone is adequate to reflect orders and attribution in Bronto, unless Cash Sales and Invoices are used to manage and create orders discretely and independently from Sales integration. Sales Orders will likely be the required transaction type for syncing, rather than Invoices. Also, Invoices and Cash Sales are bound by NetSuite accounting periods, which may limit the historical order data available for import to the existing open accounting period when you use these transaction types.
  10. For Assign this Status in Bronto, select whether you want orders import into Bronto to have a Pending or Processed status.

    In most cases, you will choose Processed unless an external process (using API or Data Loader) is in place to mark orders as Processed. Pending orders are not reflected in the RFM metrics in Bronto and do not show up in the user interface or trigger automated workflows.

  11. Optional: Change the other default Bronto Field mappings by selecting a new value from the NetSuite Field lists.

    The Bronto order and line item attributes are provided on the left and can be mapped to any valid NetSuite order or line item attribute. Most attributes are mapped to their expected NetSuite match and should not need to be changed, but you have the option to change them if you use different NetSuite attributes. If you do not want to import any of the mapped, non-required attributes, click the X to the right of the NetSuite Field value.

    When you are not using NetSuite storefront, you might need to avoid mapping the Category, Product URL, and Image URL fields. These are the recommended default values for these fields when you are using Suite Commerce Advanced or Site Builder:
    • Description: Line Item Description
    • Category: Category (preferred)
    • Product URL: Item URL
    • Image URL: Image URL
  12. Optional: Include the Source field in your order data. The NetSuite transaction record field that maps to the Source field is labeled Originator.
    The following chart shows how the NetSuite Connector maps Originator field values onto the Source field in Bronto.
    Table 1. Bronto and NetSuite Source Field Mapping
    NetSuite Originator Field Bronto Source Field
    Web Store WEBSITE
    Any other value null
    null null
    • The enhanced order attribution model currently only considers orders where the Source field is equal to WEBSITE.
    • NetSuite Connector assigns the WEBSITE value only to a transaction record created by SuiteCommerce or SiteBuilder.
  13. Optional: If you use contact fields to track order data:

    This data will only be imported from NetSuite into Bronto.

    1. Click Map Transaction Field to Contact Field.
    2. Select the NetSuite field from the NetSuite Transaction Field list.
    3. Select the contact field from the Bronto Contact Field list.
  14. Repeat the previous steps, as necessary, to map additional NetSuite transaction types.
  15. When you have finished configuration for all of the import settings on the Orders page, click Save Changes.
    Note: Only transaction body fields are available and will only sync data to contact fields related to the related contact's last transaction. These fields will be overwritten on each subsequent transaction.