Testing Full Product Sync in NetSuite Connector

Learn to test full product sync in NetSuite Connector, ensuring accurate category mapping and item flags for successful integration.

·2 min read·View Oracle Docs

To test full product sync, it is crucial to have proper category mapping set up alongside at least one additional field. This mapping informs the NetSuite Connector about the fields designated for your products. Here are the key components involved in the testing process:

  • Category Field: Establish a required category mapping, as this helps in correctly categorizing products in your chosen marketplace.
  • Price and Quantity Fields: Ensure you have mapped your inventory and pricing fields as these are often integral for most connectors.
  • Pulling and Sending Products: Items must have their Flag field set to Add/Update Item in NetSuite before being pulled into the NetSuite Connector. Once pulled, you can then send these products to your respective marketplace or cart.

Testing Matrix Items

When testing matrix items, the process is somewhat similar to that of standalone items, but with additional considerations:

  1. Set the Flag field for both parent and child items appropriately. Use Add/Update Item for both to post them together. If you want to post child items individually, the parent item should have Post Children as Standalone selected while child items should be marked for Add/Update Item.
  2. Manually pull the parent item of all associated child items into NetSuite Connector.
  3. Post only the parent item to your marketplace or cart; child items will automatically be included with this post.

Important Considerations

  • Ensure that the Flag fields are set correctly to avoid complications during product sync.
  • Different sync types can be utilized across different accounts and connectors; however, ensure that a specific connector does not mix sync types like Price and Quantity sync with Full Product sync, as only one can be used at a time per connector/account combination.

As you proceed with these tests, refer to relevant resources for detailed instructions on category mapping, inventory, and pricing to ensure a seamless product sync process in NetSuite Connector.

Frequently Asked Questions (4)

What category mapping is required for testing full product sync in NetSuite Connector?
Category mapping is necessary to correctly categorize products in your chosen marketplace. It is a key component that informs the NetSuite Connector about the designated fields for your products.
How should the Flag field be set when testing matrix items in NetSuite Connector?
When testing matrix items, both parent and child items should have the Flag field set to 'Add/Update Item'. If you want to post child items individually, the parent item should have 'Post Children as Standalone' selected while child items should be marked for 'Add/Update Item'.
Can you mix sync types like Price and Quantity sync with Full Product sync for a single connector/account combination?
No, different sync types should not be mixed for a single connector/account combination. Only one sync type can be used at a time per connector/account.
Is it necessary to pull matrix parent items manually into NetSuite Connector?
Yes, you need to manually pull the parent item of all associated child matrix items into the NetSuite Connector for proper testing.
Source: Testing Full Product Sync Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Commerce

View all Commerce articles →