NetSuite Connector Product Sync Triggers
When you set up product sync correctly, certain events trigger NetSuite Connector to fetch items from NetSuite and sync them to your storefront.
Items will sync when either a primary or secondary trigger happens. The following section describes each trigger type.
Primary Triggers
Primary triggers are changes to item attributes that start the product sync. When a primary trigger happens, NetSuite Connector fetches the item data and syncs it to your storefront.
A primary trigger happens in the following situations:
-
The lastModifiedDate or Updated At field changes on the item record in NetSuite to a date that is later than the last date NetSuite Connector checked for changed items.
-
The item's inventory changes in one of your NetSuite locations.
Secondary Triggers
Secondary triggers occur when an item linked to another item gets a primary trigger. Secondary triggers make items re-sync to your storefront, but NetSuite Connector doesn't need to fetch new item data from NetSuite. There's no need to fetch new item data because the item record itself hasn't changed. Only the item that triggered the secondary trigger has changes, so NetSuite Connector only updates that item's data.
A secondary trigger happens in the following situations:
-
An item in the same family (either a parent or child SKU) gets a primary trigger.
-
A component of a syncing kit or assembly item gets a primary trigger.
The following table provides examples of how primary and secondary triggers occur:
Action |
Result |
---|---|
When the Class field on an item changes |
When NetSuite saves the item record, a primary trigger occurs for the item and updates the lastModifiedDate field. |
When the inventory in Location 1 for an inventory item changes |
When NetSuite Connector detects an inventory change on a location assigned to the item, a primary trigger occurs. |
When the Department field on a child item SKU Shirt-Red in a matrix family changes |
When NetSuite saves the item record, a primary trigger occurs for SKU Shirt-Red and updates the lastModifiedDate field. |
When NetSuite saves the item record, a secondary trigger occurs for the parent SKU Shirt-Red and any other child SKU in that same family (Shirt-White and Shirt-Blue). |
|
When the SKU CMP1 item has an inventory change in Location 1. This item is a component of SKU MyKit, which is a Kit item set to sync. |
When NetSuite saves the item record, a primary trigger occurs for SKU CMP1 and updates the lastModifiedDate field. Note that even if CMP1 is not set to sync, NetSuite Connector still retrieves the item record for the SKU because it is a component of SKU MyKit, which is set to sync. |
When NetSuite saves the item record, a secondary trigger occurs for the parent SKU Shirt-Red and any other child SKU in that same family (Shirt-White and Shirt-Blue). |
Related Topics
- NetSuite Connector Product Sync
- Product Sync Types
- Product Sync Mechanisms
- Product Mapping Types
- NetSuite Connector Product Sync for Items
- NetSuite Connector Storefront Flag Fields
- NetSuite Connector Product Categories
- Syncing Quantity Updates
- NetSuite Connector Push Item Update Scripts in NetSuite
- Buffered Quantity
- NetSuite Connector Product Image Handling