Product Sync Mechanisms

Syncing a large number of items at a time can slow down product updates. This can happen when you upload a large CSV file or make mass updates in NetSuite, which might update more items than necessary.

When you send item updates to NetSuite Connector, the process follows the mechanisms of these two product syncs

Sync Mechanism	Description
Real-Time Sync	As the mass update changes item records, real-time sync processes each updated record and sends the data to NetSuite Connector. Sometimes, real-time sync won't work with mass updates, and that's outside of NetSuite Connector's control. Instead, the process follows the NetSuite SuiteScript governance model, which uses usage units to optimize performance. For more information about script usage limits in NetSuite, read Script Type Usage Unit Limits.
Scheduled Script (Runs every 15 minutes)	The scheduled script checks for any missed item updates and sends them as soon as it can. However, NetSuite has a limit of around 1000 items per script execution that the scheduled script can handle. The script sends what it can every 15 minutes. If the number exceeds the allowed limit, the process stops the script. If you don't adjust your workflow or the number of items to sync, the script will get stuck in a cycle of timeouts and terminated processes before it finishes.

Sync Mechanism

Description

Real-Time Sync

As the mass update changes item records, real-time sync processes each updated record and sends the data to NetSuite Connector. Sometimes, real-time sync won't work with mass updates, and that's outside of NetSuite Connector's control. Instead, the process follows the NetSuite SuiteScript governance model, which uses usage units to optimize performance. For more information about script usage limits in NetSuite, read Script Type Usage Unit Limits.

Scheduled Script (Runs every 15 minutes)

The scheduled script checks for any missed item updates and sends them as soon as it can. However, NetSuite has a limit of around 1000 items per script execution that the scheduled script can handle. The script sends what it can every 15 minutes. If the number exceeds the allowed limit, the process stops the script. If you don't adjust your workflow or the number of items to sync, the script will get stuck in a cycle of timeouts and terminated processes before it finishes.

The item data upload time depends on the marketplace/cart's API access limits within a certain time frame. Most APIs, like NetSuite, have limits to prevent too many requests from crashing the system.

When setting API limits, use the lowest limit as the deciding factor. For instance, if NetSuite can handle 1000 units per execution but Shopify can only handle 500, set the limit to 500 when syncing from NetSuite to Shopify.

If NetSuite Connector keeps failing to process your entire product queue, first check how many items are updated per hour. The more product updates you have, the longer it takes for NetSuite, NetSuite Connector, and the marketplace/cart to process them.

If you notice more than 1000 items updating per hour, you'll need to adjust the conditions in your NetSuite workflow. Your workflow conditions might include items that don't need updates. When you set up your workflow conditions correctly, only the relevant items get updated, not your entire catalog.

You should add a workflow condition to check if the field is already set and updated. This ensures the workflow only runs when necessary.

For example, if you have a workflow that sets a field to True, it should first check if the field is already True. If you skip this step, the workflow will still trigger an update on the item record, even if nothing's changed. This step will also cause the SuiteApp to push an update to NetSuite Connector. For more information, read Workflow Conditions.

Related Topics