Product Sync Mechanisms

Pushing a large amount of items to sync at a time causes delay in product updates. A large CSV product upload or mass update in NetSuite, which may update more item records than needed, may cause this issue.

When you send item updates to NetSuite Connector, these two product sync mechanisms govern the process.

Sync Mechanism	Description
Real-Time Sync	As the mass update changes the item records, the real-time sync processes every updated record and pushes the data to NetSuite Connector. In some cases, the real-time sync will not run with mass updates, which is beyond the control of NetSuite Connector. Instead, the process relies on NetSuite’s SuiteScript governance model, which is based on usage units intended to optimize application performance. For more information about NetSuite’s script usage limits, read Script Type Usage Unit Limits.
Scheduled Script (Runs every 15 minutes)	The scheduled script looks for any missed item updates and pushes them as quickly as possible. However, NetSuite imposes a limit on the number of products the scheduled script can process, which is about 1000 items per script execution. The script will push what it can every 15 minutes. If the number exceeds the limit of units allowed, the process terminates the script execution. If you do not adjust your workflow or number of items for syncing, the script loops in a cycle of timeouts and terminated processes before it completes.

Sync Mechanism

Description

Real-Time Sync

As the mass update changes the item records, the real-time sync processes every updated record and pushes the data to NetSuite Connector. In some cases, the real-time sync will not run with mass updates, which is beyond the control of NetSuite Connector. Instead, the process relies on NetSuite’s SuiteScript governance model, which is based on usage units intended to optimize application performance. For more information about NetSuite’s script usage limits, read Script Type Usage Unit Limits.

Scheduled Script (Runs every 15 minutes)

The scheduled script looks for any missed item updates and pushes them as quickly as possible. However, NetSuite imposes a limit on the number of products the scheduled script can process, which is about 1000 items per script execution. The script will push what it can every 15 minutes. If the number exceeds the limit of units allowed, the process terminates the script execution. If you do not adjust your workflow or number of items for syncing, the script loops in a cycle of timeouts and terminated processes before it completes.

The item data upload time depends on whether the marketplace/cart has a limitation on the number of times you can access the API within a certain period. Like NetSuite, most APIs have a limit to prevent an overload of requests that may end up crashing the system.

When you set the API limits, you must use the lowest limit as the determining factor. For example, if NetSuite can handle 1000 units per execution, but Shopify can only handle 500, then the limit per execution from NetSuite to Shopify should be 500.

When NetSuite Connector repeatedly fails to process your entire product queue, the first thing to check is the number of items updated per hour. The greater the number of product updates, the longer it will take for NetSuite, NetSuite Connector, and the marketplace/cart to process.

If you notice that you have more than 1000 items updating per hour, adjust the conditions to your workflow in NetSuite. The workflow condition may include items that do not require an update. When you set the workflow conditions correctly, the process updates only the relevant items, and not your full item catalog.

You should add a workflow condition that checks whether the field is already set and updated. This way, the workflow only runs when it needs to.

For example, if you have a workflow configured to set a field to True, the workflow should first check whether the field is already set to True. If you skip this step, the workflow will trigger an update on the item record even though there are no changes. This step will also cause the SuiteApp to push an update to NetSuite Connector. For more information, read Workflow Conditions.

Related Topics