ShipStation Connector FAQs for NetSuite Integration

TL;DR Opening

Understand the key functionalities and limitations of the ShipStation Connector for NetSuite, including how order syncs work and common troubleshooting tips.

What is the ShipStation Connector?

The ShipStation Connector is a tool designed to facilitate the integration between NetSuite and ShipStation, enabling streamlined management of shipping and order fulfillment. This connector allows users to synchronize their order data efficiently between the two platforms.

How Does Order Syncing Work?

How long does it take for NetSuite Connector to bring my ShipStation order back to NetSuite?

The synchronization frequency is controlled by ShipStation, which picks up and drops off orders to and from the NetSuite Connector. When a shipment is notified in ShipStation, it communicates this to the NetSuite Connector, which updates the fulfillment data accordingly. Typically, this notification occurs when a shipping label is generated in ShipStation.

Can NetSuite Connector fulfill orders that were manually imported to ShipStation using a CSV file?

No, the connector only syncs fulfillments for orders that originated from the NetSuite Connector. For orders imported manually via CSV, they must first be brought into NetSuite.

Can I sync fulfillments for my other stores in ShipStation with NetSuite Connector?

No. The NetSuite Connector is limited to orders originally synced through it.

Can I sync the weight from ShipStation to my item fulfillments in NetSuite?

Weight data cannot be synced from ShipStation to NetSuite item fulfillments. The default weight for items is set to 1 pound unless otherwise specified in NetSuite.

Can I use one ShipStation custom store in ShipStation to connect to multiple ShipStation connectors in NetSuite Connector?

No, each custom store must be associated with a single ShipStation connector.

Can NetSuite Connector sync the Hold Until field to ShipStation with the orders?

No, the integration does not support syncing the Hold Until field via API, which limits its functionality in this aspect.

Why is the order number in ShipStation different from NetSuite Connector?

If NetSuite is configured to sync pick tickets, it uses the transaction ID from the item fulfillment in NetSuite as the order number in ShipStation. This ensures uniqueness and prevents duplicate order numbers.

Why are fulfillments not syncing from ShipStation back to NetSuite?

Check if ShipStation has sent the fulfillment notification to NetSuite Connector. If not, it must be resent. ShipStation usually sends this notification when marking orders as shipped.

Why do I see old or fulfilled orders in my ShipStation or ShipWorks connector?

Old orders can linger if they are either waiting for pickup or have been picked up already. Checking your NetSuite Connector credentials and automated processes can prevent unnecessary syncing of already processed orders.

How do I view the activity logs in ShipStation?

You can view activity logs for both the custom store and individual orders within ShipStation. Detailed instructions are available in their support documentation.

Who This Affects

• Administrators: Manage and configure the connector settings.
• Developers: Implement and troubleshoot the integration.
• Shipping / Fulfillment Teams: Operate daily tasks involving order processing and shipping.

Key Takeaways

• ShipStation Connector syncs only those orders confirmed through the NetSuite Connector.
• Weight information defaults to 1 pound unless specified in NetSuite.
• The Hold Until field is not supported through the current API integration.
• Order number discrepancies arise from using transaction IDs to maintain uniqueness.
• Old or fulfilled orders require careful management of NetSuite Connector settings to avoid confusion.

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