NetSuite Connector Product Sync Test Configuration Guide

To ensure a smooth product sync experience with NetSuite Connector, it is crucial to test product sync using sample products before deploying in a live environment. This not only safeguards live sales but also provides insights into possible issues during integration. Here’s how you can effectively set up and test product sync with sample products.

What is Needed for Testing Product Sync?

Start by creating or selecting test products ready for monitoring any data changes. It's important to choose products that lack high customer engagement to avoid impacting your actual sales.

Product Sync Options

NetSuite Connector provides two primary options for product synchronization:

• Price and Quantity Sync: This method syncs the price and available quantities of products.
• Full Product Sync: This sync involves sending all product details, including variations.

A noteworthy restriction is that only one sync operation can be conducted at a time for each connector or account combination.

Price and Quantity Sync

For the price and quantity sync setup, ensure:

• The SKU in NetSuite matches the SKU in the associated marketplace or shopping cart exactly.
• A price value is entered at one of the price levels in NetSuite for products being synced for price changes.
• If syncing quantity, verify there’s quantity available in NetSuite or a specified custom field for the required product.

Full Product Sync

When implementing full product syncing, choose your test items with care:

• Utilize the matrix item type in NetSuite for products with variations. Specify both parent and child items along with other variation attributes like size and color.
• Maintain a matrix item family in NetSuite specifically for testing purposes.
• For effective testing, limit the number of subitems per item family to five or fewer.

If your business model includes standalone items, at least one good sample product from NetSuite will be essential for testing.

Essential Item Fields

Most marketplaces necessitate the following fields to be filled for test products in NetSuite:

• Flag Field: Used for identification by NetSuite Connector for management of specific inventory records.
• Other Data: Include any additional information required for full data synchronization across channels.

Successfully configuring and testing your product sync can lead to enhanced operational efficiency and reduced troubleshooting time during actual deployments.

Key Considerations

• Always conduct tests using non-live data to prevent disruptions in sales.
• Familiarize yourself with both sync strategies to choose appropriate ones based on your business requirements.
• Regularly verify mappings post-sync to ensure alignment with your market or platform updates.

By following these guidelines for testing product sync in NetSuite Connector, you can confidently move towards a successful product integration within your e-commerce setup.

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

Key Takeaways

• Testing with sample products is crucial to avoid disrupting live sales.
• Choose appropriate product sync methods based on your item types.
• Ensure SKUs and pricing are correctly aligned between NetSuite and marketplace.
• Use matrix item types for testing products with variations efficiently.