NetSuite is an enterprise resource planning (ERP) system for managing ecommerce, CRM, financials, and more. This article covers how to set up and use the ShipStation NetSuite integration.
There are several steps to the NetSuite connection process, please review the overall process steps below to ensure you are ready to connect:
-
Enable SuiteCloud Client and Server SuiteScript in NetSuite.
-
(optional) Create an Order Filter in NetSuite.
-
Determine which Import Fulfillment Workflow best fits your needs.
-
Connect your NetSuite store to ShipStation.
-
(optional) Customize your store settings and custom field mapping in ShipStation.
If you do not already have an account with NetSuite, contact NetSuite for a Free Demo.
Netsuite OAuth 2.0
This article covers ShipStation's new Native NetSuite integration using OAuth 2.0. If you're using the legacy integration, see NetSuite Legacy. Please note the legacy integration will be sunset on June 30, 2026.
Do not deactivate your legacy connection until you have confirmed the migration process is complete.
Connection Requirements:
-
Your NetSuite account must have SuiteCloud Client and Server SuiteScript enabled.
-
NetSuite Account ID
Order Import Requirements:
-
Orders must have a Ship-To address
-
Orders in the Pending Approval status will not import
Admin Account with OAuth 2.0 Access Required
The role used for ShipStation access must have Log in Using OAuth 2.0 Access Tokens. A role with OAuth 2.0 Authorized Applications Management cannot be used for access.
A NetSuite administrator must complete the following steps before connecting to ShipStation:
-
Login to your NetSuite administrator account.
-
Go to
Setup > Company > Setup Tasks > Enable Features. -
Click the SuiteCloud tab.
-
Under SuiteScript, enable both:
-
Client SuiteScript – click I Agree on the Terms of Service prompt.
-
Server SuiteScript – click I Agree on the Terms of Service prompt.
-
-
Check the OAuth 2.0 box under Manage Authentication and click I Agree.
-
Click Save.
-
Go to
Setup > Users/Roles > User Management > Manage Rolesto configure the role used for the ShipStation integration. -
On the Permissions subtab, click Setup and add:
-
Log in Using OAuth 2.0 Access Tokens
-
OAuth 2.0 Authorized Applications Management (Administrator role only)
-
-
Go to the
ellipsis menu > SuiteApps > Install ShipStation Native. -
Click on the ShipStation app.
Once the ShipStation app is enabled you will see ShipStation as an option in your Navigation bar.
To connect your NetSuite store to ShipStation:
-
Select NetSuite.
-
Select a Workflow from the dropdown. You will be able to change this setting as needed from the store settings page.
See the Import Fulfillment Workflows section for guidance on which option is right for your setup.
-
(optional) Enter an Order Filter Name if you created one in NetSuite. If no order filter is set, all eligible orders are imported.
-
Click Connect. You will be redirected to NetSuite to authorize the connection via OAuth.
-
Review and approve the permissions request in NetSuite. You will be redirected back to ShipStation.
-
Click Save to complete setup.
After connecting, the store's Settings page will open. You can adjust store-specific settings like branding and customer notifications, or click Save to close.
NetSuite with ShipStation has four available workflows. Each workflow sets status mapping and differs slightly in how they handle shipment notifications.
-
Sales Order: This is the default workflow that most merchants use. If you select this option you can also leverage some o ShipStation's other features, such as the pick and pack process.
-
PickPackShip - Picked: Item Fulfillment Records (IFR) are created against Sales Orders in NetSuite to manage the Pick/Pack process within NetSuite, but utilize ShipStation for the fulfillment process. Checks for Item Fulfillment Records in the Picked status, as defined in the Connection Steps.
-
PickPackShip - Packed: Checks for Item Fulfillment Records in the Packed status, as defined in the Connection Steps.
-
Transfer Orders: Import item fulfillment records for transfer orders in NetSuite. This setting is best for wholesale teams that move inventory between warehouses.
When connecting a new NetSuite account to ShipStation you will have the option to enter an order filter name from NetSuite. ShipStation will use the NetSuite Order Filter to limit which orders are imported into ShipStation. If no order filter is set, all eligible orders are imported.
Notes About Using Order Filters:
-
Filter names can contain letters, numbers, hypens, or underscores. Other characters will cause issues with syncing.
-
Values must exactly match what's displayed in NetSuite.
-
Only one order filter is supported per connection.
-
You can filter by location, class, and department in NetSuite.
-
If no order filter is set, all eligible orders are imported.
ShipStation's Native NetSuite integration supports importing up to three additional fields from NetSuite to custom fields 1, 2, or 3. The following fields can be mapped to standard order fields or any custom body field (custbody_*).
|
Field Name |
Description |
|---|---|
|
(createddate) |
Create Date |
|
(currencyname) |
Currency |
|
(email) |
Customer Email |
|
(entityname) |
Customer Number |
|
(custbody_cp) |
Customer Priority |
|
(exchangerate) |
Exchange Rate |
|
(custbody_fmt_finance_app) |
Finance Approved |
|
(custbody_fmt_finance_app_date) |
Finance Approved Date |
|
(custbody_fmt_finance_declined) |
Finance Declined |
|
(lastmodifieddate) |
Last Modified Date |
|
(locationname) |
Location |
|
(memo) |
Memo |
|
(trandate) |
Order Date |
|
(tranid) |
Order Number |
|
(total) |
Order Total |
|
(custbody_pfc_pfitemid) |
Picture Frame Item ID |
|
(otherrefnum) |
PO / Reference Number |
|
(custbody_cust_priority) |
Priority |
|
(custbody_promisedate_2) |
Promise Date (2) |
|
(custbody_reasonforreturn) |
Reason for Return |
|
(custbody_fmt_req_financial_app) |
Requires Finance Approval |
|
(custbody_fmt_req_sales_manager_app) |
Requires Sales Manager Approval |
|
(custbody_fmt_sales_manager_app) |
Sales Manager Approved |
|
(custbody_fmt_sales_manager_app_date) |
Sales Manager Approved Date |
|
(custbody_fmt_sales_manager_declined) |
Sales Manager Declined |
|
(custbody_fmt_senior_executive_app) |
Senior Executive Approved |
|
(custbody_fmt_senior_executive_app_date) |
Senior Executive Approved Date |
|
(custbody_fmt_senior_exec_declined) |
Senior Executive Declined |
|
(shipdate) |
Ship Date |
|
(shipmethodname) |
Ship Method |
|
(custbody_shpst_carrier) |
ShipStation Carrier (2) |
|
(source) |
Source |
|
(status) |
Status Code |
|
(taxtotal) |
Tax Total |
The ShipStation integration with NetSuite supports the following standard features:
|
Feature |
Supported? |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This table indicates which data ShipStation sends to Netsuite with the marketplace shipment notification:
|
Field |
Sent to Marketplace? |
|---|---|
|
Status Update |
|
|
Tracking Number |
|
|
Carrier |
|
|
Service |
|
|
Carrier Fee |
|
|
|
|
|
Item Information |
|
Your fulfillment strategy in NetSuite controls how NetSuite is updated when ShipStation creates a label for an imported order. You can select your strategy in your NetSuite account by going to the NetSuite tab > Configurations > Shipment Configuration. The current workflow options are:
-
ShipStation Default: this option will update based on the workflow you selected in the ShipStation connection module:
-
Sales Order: This is the default workflow that most merchants use. If you select this option you can also leverage some of ShipStation's other features, such as the pick and pack process.
-
PickPackShip: this workflow updates the existing Item Fulfillment record. Note: this option does not support multiple ship-from or ship-to destinations. If your fulfillment requires multiple addresses we recommend using the Sales Order workflow.
-
Transfer Order: this workflow creates a new item Fulfillment record.
-
-
Multi-Ship-To Orders: If your NetSuite account has the Multi-Ship-To feature enabled, ShipStation will split the order into multiple fulfillments grouped by ship-to location. For example, if order #123 contains 2 T-shirts shipping to Texas and 1 mug shipping to Florida, ShipStation will create 2 fulfillments for order #123 — each with its own ship-to address and item list.
-
Multi-Ship-From Orders: NetSuite assigns a Preferred Location per item, allowing you to stock the same SKU across multiple locations with different inventory levels — though only one location can be set as preferred. ShipStation does not have visibility into stock levels per location and does not prioritize locations within a single sales order. As a result, ShipStation will not split fulfillments based on differing Preferred Locations within one sales order. The sales order location will display as a read-only field on the order details page.
-
Item Fulfillment Record: ShipStation displays multiple fulfillments for the same sales order based on existing Item Fulfillment records in NetSuite. For example, if order #123 has 2 items and item 1 has already been shipped in NetSuite but item 2 still needs to be shipped, order #123 will import with 2 fulfillments: Fulfillment 1 (item 1) in Shipped status and Fulfillment 2 (item 2) in Awaiting Shipment status. This allows users to create a label for the outstanding item while eliminating the risk of double-shipping an item that has already been fulfilled outside of ShipStation.
For advanced customization, ShipStation supports custom shipment notification plugins via NetSuite's plug-in system. See Custom Shipment Notification Plugin for ShipStation in NetSuite for details.