NetSuite Connector Product Sync FAQs and Best Practices

The NetSuite Connector enables integration between NetSuite and various online storefronts, but users often have questions regarding product synchronization. Understanding the behavior of flag fields and how they impact item status is crucial to optimizing your product sync workflow.

Why Does an Inactive Item Still Post?

NetSuite Connector determines whether to post an item based on its flag fields, not its active status in NetSuite. If an item is deactivated yet its flag field remains set to Y, it will still be posted. This situation arises because the Connector does not reload deactivated items and continues using the last processed data.

Why Does a Deleted Item Keep Resyncing?

Deleting an item from NetSuite Connector does not update the corresponding flag field in NetSuite. Consequently, the item continues syncing because the mapped flag field still indicates it should.

Why Is My Item Scheduled to Delete?

If an item is showing as scheduled for deletion despite being set to Add/Update Item, this discrepancy may arise from mismatches in settings:

• Verify the flag field ID under Mappings > Products for your connector and confirm it’s set to Add/Update Item in NetSuite.
• If using a custom list for the flag field, ensure the values are consistent and ordered correctly.

Why Does a Product Remain in the Storefront?

Several factors could lead to this issue:

• The Price/Qty sync method does not allow for item deletions from the storefront. Only a Full Product sync can facilitate this.
• There might be a delay in the automated sync process, which typically completes within an hour.

Why Didn't My Update Appear in the Storefront?

Updates to lists, records, or images do not directly modify the item record in NetSuite. To trigger a storefront update, ensure the item record is modified sufficiently or force a reload operation if possible.

SKU Changes in NetSuite

Changing an SKU in NetSuite doesn't reflect in the storefront automatically. NetSuite Connector does not update the SKU in the storefront since it relies on the itemID for matching. Manually changing the SKU in both places is necessary.

Mapping Multiple Storefront Products

You can successfully map multiple storefront products to a single product in NetSuite, provided they have unique SKUs.

Why Are Items Still Importing if Sync Is Disabled?

The processes to import items flagged to sync and to sync those items to the storefront maintain independence. If items are visible in the Connector, they are still tagged for syncing in NetSuite.

Impact of Disabling Inventory Mapping

When you disable inventory mapping, existing inventory values won't be removed instantly. If a marketplace or cart tracks inventory based on prior postings, inventory levels will deplete as orders are placed.

Can Quantity or Price Be Synced Separately?

Yes, you can sync either quantity or price during both price and quantity syncs or full product syncs. Only mapped fields will sync, so avoid creating mappings for fields you don’t wish to sync.

Noninventory Item Syncing

NetSuite Connector can sync various item types— including noninventory items. However, storefront visibility may depend on how these items are managed. Typical item types to sync include:

• Assembly
• Kit/Package
• Inventory

Migrating Product Data from Storefront to NetSuite

For effective data management, maintain NetSuite as the master record. If data needs migrating from a storefront, you should export it to a CSV file before importing it into NetSuite.

Key Takeaways

• Item flag fields control posting behavior, not status.
• Deleting items in Connector doesn’t prevent them from syncing.
• Changes in SKU require manual updates in both locations.
• Inventory mapping must be managed carefully to reflect storefront needs.
• Noninventory items can also be synced, but visibility varies.

Source: This article is based on Oracle's official NetSuite documentation.