Price and Quantity Sync Testing Procedures in NetSuite

This article outlines the testing procedures for price and quantity synchronization in NetSuite, including setup and syncing methods.

·2 min read·View Oracle Docs

To ensure accurate price and quantity synchronization in NetSuite, this article details the testing procedures required for successful integration.

What is Price and Quantity Sync?

Price and quantity synchronization allows businesses to maintain consistent inventory levels and pricing information across multiple sales channels, making it essential for effective inventory management.

How to Test Price and Quantity Sync

To validate the price and quantity sync, ensure your mappings are configured correctly. Critical components include the mapping of the required Category field, price fields, and quantity fields.

Pulling the Product into NetSuite Connector

Before testing, you must pull the product into the NetSuite Connector.

Steps to Retrieve the Product:

  1. Go to Data Flows > Products to open the Products dashboard.
  2. Click Retrieve to open the Retrieve Product window.
  3. Enter the Product SKU or Internal ID for the product.
  4. Click Retrieve to add the product to your dashboard.

Sending the Product to Marketplace or Cart

After the product has been pulled in, you can send it to the desired marketplace or cart.

Steps to Send Product:

  1. Navigate to Data Flows > Products.
  2. Find the product in the list, ensuring it shows the correct status.
  3. Click the pencil icon on the product line.
  4. Select Update Inventory and Price on X, where X is the specific marketplace or cart.
    • The product status will initially show Posting in Progress.
    • If successful, it will change to Product Synced to X. Errors will be indicated on the line.

Additional Testing Procedures

Testing Fulfillment Sync

Before testing price and quantity sync, ensure order fulfillment has been completed to send fulfillment information to the marketplace. Retrieve the appropriate orders and check the status for successful shipments.

Testing Full Product Sync

Incorporate the required Category mapping and at least one additional field to ensure full product sync testing is effective, following the outlined procedures above.

Testing Matrix Items

Matrix items require additional consideration for their parent and child posting attributes. Set the Flag field appropriately for both item types and synchronize accordingly.

Key Takeaways

  • Ensure correct mappings to test price and quantity sync effectively.
  • Follow precise steps for pulling products into the NetSuite Connector and sending them to marketplaces.
  • Understand the nuances of matrix item posting for accurate data management.

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

Frequently Asked Questions (4)

What are the prerequisites for testing price and quantity sync in NetSuite?
Before testing price and quantity sync, ensure that your mappings, including Category, price fields, and quantity fields, are configured correctly. Additionally, products must be pulled into the NetSuite Connector.
Do I need to retrieve product information before sending it to a marketplace or cart?
Yes, you need to retrieve the product information using the Product SKU or Internal ID in the NetSuite Connector before sending it to the desired marketplace or cart.
What steps should be followed to ensure successful product sync to a marketplace?
First, retrieve the product information in the NetSuite Connector. Then, navigate to Data Flows > Products, locate your product, and use 'Update Inventory and Price' to sync it to the marketplace. Check that the product status changes from 'Posting in Progress' to 'Product Synced'.
How should I handle matrix items during price and quantity sync testing?
Matrix items require special attention to their parent and child attributes. Make sure to set the Flag field appropriately for both item types and synchronize them accordingly.
Source: Testing Price and Quantity 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 Integration

View all Integration articles →