Troubleshooting Amazon Connector Issues in NetSuite

Resolve common issues with the Amazon Connector in NetSuite, including order imports and missing field errors.

·2 min read·View Oracle Docs

TL;DR Opening

This article provides guidance on troubleshooting common issues with the Amazon Connector in NetSuite. It covers order import problems, missing field errors during settlement sync, pending product statuses, and incomplete customer information from Amazon MFN orders.

Common Amazon Connector Issues

The Amazon Connector in NetSuite may present several issues that users need to troubleshoot. Some of the most common problems include:

  • Orders stuck in Pending status, which are not imported by default.
  • FBA (Fulfillment by Amazon) orders that have not yet synced, which typically occurs every five hours.

Troubleshooting Order Import Issues

For general order import issues, users should refer to the related documentation on troubleshooting order import problems within the NetSuite Connector. Ensure that only non-pending orders are imported, and monitor the synchronization schedule for FBA orders.

Handling Missing Field Settlement Errors

Missing field errors occur when a required transaction field is not mapped in NetSuite Connector. Here are the steps to resolve these errors:

  1. Mapping Missing Fields:

    • Log in to the FarApp platform at app.farapp.com.
    • Select the Amazon connector and the relevant account.
    • Navigate to Mappings > Settlements.
    • If the issue is related to an item level, click the Settlement Item tab; otherwise, proceed to the Settlement tab.
    • Click Add Mapping and follow the prompts to select the appropriate transaction type and NetSuite field to map.
    • After mapping, save your settings to apply the changes.
  2. Changing the Transaction Form:

    • If the required field is set incorrectly, clear the Mandatory option in the transaction form settings. This adjustment can help avoid future missing field errors.

Troubleshooting Incomplete Customer Information

When dealing with Amazon MFN orders, ensure that customer information is fully captured to prevent incomplete data submissions. Monitor imported orders for completeness and verify customer data accuracy.

Who This Affects

This troubleshooting guidance is primarily relevant for:

  • Administrators: Those configuring and managing the Amazon Connector.
  • Developers: Individuals integrating and customizing the connector functionality.
  • Order Management Teams: Users reliant on accurate order and customer data through the integration.

Key Takeaways

  • Monitor order statuses; pending orders aren't imported by default.
  • Ensure all required fields are properly mapped in the connector to avoid settlement errors.
  • Regularly verify Amazon MFN order data for completion and accuracy.

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

Frequently Asked Questions (4)

Do I need to import pending status orders for Amazon Connector in NetSuite?
No, pending status orders are not imported by default in the Amazon Connector for NetSuite. You should ensure only non-pending orders are set to import.
How often does the synchronization occur for FBA orders in NetSuite's Amazon Connector?
The synchronization for FBA (Fulfillment by Amazon) orders typically occurs every five hours in NetSuite's Amazon Connector.
How can I resolve missing field errors in NetSuite Amazon Connector's settlement sync?
To resolve missing field errors, map the necessary fields by logging into the FarApp platform, navigating to Mappings > Settlements, and adding the required mappings. Ensure all transaction fields are appropriately assigned.
What step should be taken if a required transaction field is incorrectly set in NetSuite?
If a required transaction field is incorrectly set, clear the 'Mandatory' option in the transaction form settings to avoid future missing field errors.
Source: Troubleshooting Amazon Connector Issues 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 Order Management

View all Order Management articles →