Fields Mapped to ShipStation with NetSuite Connector Integration

NetSuite Connector automatically maps required fields to ShipStation, enabling customizable order data synchronization.

·2 min read·View Oracle Docs

By default, NetSuite Connector maps all required fields when orders are synchronized from NetSuite to ShipStation. Additional field mappings can be implemented to sync more data, provided that the data is accessible in NetSuite and ShipStation supports the necessary field via the current API.

How Does the NetSuite Connector Communicate with ShipStation?

NetSuite Connector interfaces with ShipStation through the Custom Store API, which was the only API option available during its initial development. Although ShipStation has since introduced additional API implementations, the NetSuite Connector continues to utilize the Custom Store method for integration.

Mapping Order and Fulfillment Fields

Available Fields for Mapping

Order and fulfillment fields available in ShipStation are documented in the ShipStation Custom Store Development Guide. These can be accessed via the Custom Store API. If a field you wish to map isn't listed, it cannot be synchronized with ShipStation.

  • Header Level vs. Line Level: Be aware of which fields are header-level and which are line-level since mappings need to align at the same level.

Configuring Mappings in NetSuite

Mappings can be configured using the ShipStation Connector's user interface via the menu path Mappings > Orders. Note that although the shipment method from fulfillments returned to NetSuite can be mapped, you may need to submit a support ticket for any other field mapping. This support ticket should specify the ShipStation field ID you want mapped and the target NetSuite field ID.

Importance of Field Identification

To ensure that mappings can be updated or newly implemented effectively, verify that the desired fields are available in ShipStation according to its documentation. Understanding the distinction between header and line level fields is critical for successful configurations.

For further assistance and inquiries, please contact NetSuite Customer Support.

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

Frequently Asked Questions (4)

Can I add additional field mappings between NetSuite and ShipStation?
Yes, additional field mappings can be implemented if the data is accessible in NetSuite and ShipStation supports the necessary field via the current API.
How do I distinguish between header-level and line-level fields for mapping?
You need to verify whether the fields you wish to map are documented as header-level or line-level in the ShipStation Custom Store Development Guide, as mappings must align at the same level.
What should I do if I need to map a fulfillment-related field back to NetSuite?
While the shipment method from fulfillments can be mapped back into NetSuite, for mapping other fields, you will need to submit a support ticket detailing the ShipStation field ID and the target NetSuite field ID.
Does NetSuite Connector use the latest API implementation available for ShipStation?
No, NetSuite Connector continues to use the Custom Store API for integration with ShipStation, despite the availability of newer API implementations.
Source: Fields that can be Mapped to and from ShipStation 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 →