NetSuite Plus ShipStation: Shipping Integration Guide for Ecommerce
NetSuite + ShipStation: Shipping Integration Guide for Ecommerce
Disclosure: Some links in this article are affiliate links. We may earn a commission if you purchase through them, at no extra cost to you. We only recommend solutions we've vetted through real client implementations.
Shipping is the bridge between a NetSuite sales order and a happy customer. But without a proper integration between your ERP and your shipping platform, that bridge is made of manual data entry, copy-paste tracking numbers, and warehouse staff toggling between screens. ShipStation is one of the most popular shipping platforms for mid-market ecommerce brands, and connecting it to NetSuite properly can cut your shipping processing time by 60–80%.
In our work with ecommerce brands running NetSuite, the shipping integration is often treated as an afterthought — something to figure out after the ERP goes live. That's a mistake. Shipping touches orders, inventory, customers, and financials. Getting it right from the start saves you months of workaround patches later.
This guide covers the complete ShipStation + NetSuite integration: connector options, carrier rate shopping, returns handling, and the decision framework for when ShipStation makes sense versus NetSuite's own shipping capabilities.
Key Takeaways
- ShipStation connects to NetSuite via REST API or middleware — there's no native SuiteApp for ShipStation specifically
- The core value is rate shopping and label generation — compare rates across UPS, FedEx, USPS, and DHL in real-time from within your shipping workflow
- Returns handling is the most overlooked integration flow — plan for return labels, tracking, and credit memo creation upfront
- Budget $5K–$15K for implementation plus ShipStation's subscription ($25–$180/month depending on shipment volume)
- NetSuite WMS users should evaluate native shipping first — ShipStation adds value primarily for brands without NetSuite's warehouse management module
How Does the ShipStation + NetSuite Integration Work?
Integration Architecture
ShipStation and NetSuite connect through ShipStation's API and NetSuite's REST API or SuiteTalk SOAP API. The data flow is straightforward:
- Orders flow from NetSuite to ShipStation: When a sales order is approved and ready to ship, it syncs to ShipStation as an order awaiting fulfillment.
- Shipping happens in ShipStation: Warehouse staff use ShipStation to select a carrier and service level, print labels, and process shipments.
- Shipment data flows back to NetSuite: Tracking numbers, carrier information, shipping costs, and package details sync back to NetSuite as item fulfillment records.
Connection Options
Option 1: ShipStation's Built-In NetSuite Integration
ShipStation has a NetSuite integration available on higher-tier plans. It uses NetSuite's Saved Searches to pull orders and pushes tracking information back via the SuiteTalk API.
Setup requirements:
- NetSuite Token-Based Authentication credentials
- A Saved Search in NetSuite that returns orders ready to ship
- ShipStation account on the Enterprise plan or higher
Limitations: The built-in integration is basic. It handles order import and tracking number write-back, but doesn't support complex scenarios like partial fulfillments, split shipments, or custom field sync without workarounds.
Option 2: Middleware (Celigo, Pipe17, or Custom)
For more control over the data flow, connect ShipStation and NetSuite through middleware. This gives you custom field mapping, complex fulfillment logic, and better error handling.
Why you'd choose middleware:
- You need to map custom fields (lot numbers, serial numbers, special handling instructions)
- You have complex fulfillment workflows (multiple warehouses, 3PL routing, hazardous materials flags)
- You want consolidated monitoring of ShipStation alongside other integrations (ecommerce platform, marketplace, 3PL)
Cost: $6K–$15K implementation plus middleware fees ($5K–$15K/year).
Option 3: Custom API Integration
ShipStation has a well-documented REST API. For brands with development resources, a custom integration gives full control over the data flow.
When to build custom:
- You have a developer who can maintain it
- Your shipping workflow has unique requirements that no pre-built connector supports
- You're integrating ShipStation with multiple systems and want centralized control
Cost: $8K–$20K development plus ongoing maintenance.
Our Recommendation
For most ecommerce brands, ShipStation's built-in NetSuite integration is sufficient if your fulfillment workflow is straightforward (single warehouse, standard carriers, no complex routing). If you have multi-warehouse operations or need custom field sync, invest in middleware from the start — it'll save you from rebuilding later.
How Do You Configure the Order-to-Ship Flow?
Defining "Ready to Ship" in NetSuite
Not every sales order should flow to ShipStation. You need to define which orders are ready for fulfillment. Create a NetSuite Saved Search with these criteria:
- Status: Pending Fulfillment (or your custom "Ready to Ship" status)
- Payment status: Fully paid (avoid shipping orders with pending payments)
- Fraud check: Passed (if you use fraud screening)
- Inventory available: All line items can be fulfilled from available stock
This Saved Search becomes the source for ShipStation's order import. Only orders matching these criteria appear in ShipStation for processing.
Order Data Mapping
When an order syncs to ShipStation, these fields should map:
| NetSuite Field | ShipStation Field | Notes |
|---|---|---|
| Sales Order Number | Order Number | Primary identifier |
| Ship-to Name | Recipient Name | |
| Ship-to Address | Ship-to Address | Full address with zip+4 if available |
| Ship Method | Requested Shipping | Maps to ShipStation's service codes |
| Item SKU | SKU | Must match for warehouse lookup |
| Item Quantity | Quantity | |
| Weight | Weight | Per line item or total order |
| Dimensions | Dimensions | If available for rate shopping |
| Special Instructions | Internal Notes | Gift messages, handling notes |
| Order Date | Order Date | |
| Customer Email | Customer Email | For shipping notification |
Ship Method Mapping
NetSuite's shipping methods (e.g., "Standard Ground," "2-Day Express," "Overnight") need to map to ShipStation's service codes. ShipStation supports carrier-specific service codes (ups_ground, fedex_2day, usps_priority) and generic service codes.
Best practice: Create a mapping table that translates NetSuite ship methods to ShipStation carrier/service combinations. This allows rate shopping within the specified service level — for example, "Standard Ground" could rate-shop between UPS Ground, FedEx Ground, and USPS Priority Mail to find the cheapest option.
How Does Rate Shopping Work Across Carriers?
Rate shopping is one of ShipStation's primary value propositions. Instead of defaulting to one carrier, ShipStation compares rates across multiple carriers and service levels for each shipment.
Setting Up Carrier Accounts
Connect your carrier accounts to ShipStation:
- UPS: Link your UPS account with your negotiated rates. ShipStation will show your actual discounted rates, not published retail rates.
- FedEx: Same setup — link your FedEx account for negotiated pricing.
- USPS: ShipStation provides discounted USPS rates through their platform (ShipStation stamps), or you can connect your own USPS account.
- DHL eCommerce: For international economy shipping, DHL eCommerce rates through ShipStation are often competitive.
- Regional carriers: If you use OnTrac, LSO, Spee-Dee, or other regional carriers, check ShipStation's carrier support.
Rate Shopping Configuration
Configure ShipStation's automation rules to rate-shop based on your criteria:
- Cheapest option: For standard ground shipments, automatically select the cheapest carrier for the package size and weight.
- Fastest option: For expedited shipments, select the fastest carrier that meets the delivery promise.
- Service-level matching: For orders with a specific service level (e.g., "2-Day"), rate-shop only among carriers offering 2-day delivery to that destination.
- Weight-based routing: Lightweight packages (under 1 lb) often ship cheapest via USPS First Class; heavier packages via UPS or FedEx Ground.
Real Savings
In our experience, brands that implement rate shopping across at least three carriers typically save 12–25% on shipping costs compared to using a single carrier. For a brand shipping 5,000 packages per month at an average of $8 per shipment, that's $4,800–$10,000/month in savings — enough to pay for the entire ShipStation + NetSuite integration in the first month.
Shipping Cost Write-Back
After ShipStation generates a label, the actual shipping cost should sync back to NetSuite. This is important for two reasons:
- Accurate COGS: The actual shipping cost (what you paid the carrier) should post to your shipping expense account, not the estimated cost.
- Margin analysis: Comparing what the customer paid for shipping vs. what you actually paid reveals whether your shipping pricing strategy is profitable.
Configure your integration to update the NetSuite item fulfillment record with the actual carrier, service level, tracking number, and shipping cost from ShipStation.
How Do You Handle Returns and Tracking Updates?
Returns Integration
Returns are the most overlooked part of the shipping integration. Here's the complete flow:
- Return label generation: When a customer requests a return, generate a return shipping label in ShipStation. This can be a pre-paid label (you pay) or a scan-based return label (customer pays).
- Return tracking: The return label's tracking number should sync to NetSuite's return authorization record, so your team can monitor when the return shipment is in transit and when it arrives.
- Receiving: When the return arrives at your warehouse, the warehouse team confirms receipt in NetSuite (receiving the return authorization), which triggers the credit memo or exchange process.
- Credit memo sync: If the return results in a refund, the credit memo amount should sync back to the ecommerce platform (Shopify, BigCommerce, etc.) to trigger the customer's refund.
Tracking Updates
Customers expect tracking updates. The flow works like this:
- ShipStation generates a label and creates a tracking number.
- The tracking number syncs to NetSuite's item fulfillment record.
- If NetSuite is integrated with your ecommerce platform (Shopify, BigCommerce), the tracking number flows to the platform.
- The ecommerce platform sends the customer a shipping confirmation email with the tracking link.
Important: Make sure the carrier name that syncs to your ecommerce platform matches the platform's recognized carrier list. If ShipStation sends "United Parcel Service" but Shopify expects "UPS," the tracking link won't work.
Delivery Confirmation
ShipStation can receive delivery confirmation events from carriers. Configure your integration to update the NetSuite sales order status when delivery is confirmed. This is useful for:
- Triggering review request emails
- Starting the return window countdown
- Marking the order as complete in NetSuite
When Should You Use ShipStation vs. NetSuite WMS Native Shipping?
This is a common question for brands considering or already using NetSuite's Warehouse Management System (WMS) module.
Use ShipStation When:
- You don't have NetSuite WMS: ShipStation fills the shipping gap that exists when you're running NetSuite without the WMS module. NetSuite's standard fulfillment workflow handles basic shipping, but lacks rate shopping, batch label printing, and carrier integration.
- You ship from multiple locations but don't need full WMS: ShipStation's multi-warehouse support lets you route orders to the correct warehouse and manage shipping from each location.
- You need rate shopping across carriers: NetSuite WMS supports carrier integration, but rate shopping across multiple carriers is more intuitive in ShipStation.
- Your shipping team prefers a standalone UI: ShipStation's interface is purpose-built for warehouse staff. It's simpler and faster than navigating NetSuite's fulfillment screens.
Use NetSuite WMS Native Shipping When:
- You've invested in NetSuite WMS: If you're already paying for the WMS module, its built-in shipping capabilities (carrier integration, label printing, cartonization) may make ShipStation redundant.
- You need bin-level picking and packing: WMS provides pick, pack, and ship workflows that ShipStation doesn't — ShipStation is about shipping, not warehouse operations.
- You want a single system: Reducing the number of systems your warehouse team uses reduces training, reduces integration complexity, and keeps all operational data in one place.
- You process 50K+ shipments/month: At very high volumes, the overhead of syncing data between NetSuite and ShipStation can become a bottleneck. Native shipping eliminates that sync.
The Hybrid Approach
Some brands use NetSuite WMS for pick and pack, then hand off to ShipStation for rate shopping and label generation. This gives you the best of both worlds but requires careful integration between WMS and ShipStation to avoid duplicate fulfillment records.
What Does a ShipStation + NetSuite Integration Cost?
ShipStation Subscription
| Plan | Monthly Cost | Shipments/Month |
|---|---|---|
| Starter | $25 | 500 |
| Growth | $65 | 3,000 |
| Scale | $105 | 7,500 |
| High-Volume | $180+ | 7,500+ |
Integration Implementation
| Approach | Implementation Cost | Annual Maintenance |
|---|---|---|
| ShipStation built-in | $3K–$5K | $1K–$2K |
| Middleware (Celigo) | $8K–$15K | $5K–$12K |
| Custom API | $10K–$20K | $5K–$10K |
Total Year 1 Cost
For a mid-market brand shipping 5,000 packages/month:
- ShipStation Scale plan: $1,260/year
- Middleware implementation: $10K
- Ongoing maintenance: $5K
- Total Year 1: ~$16K
- Year 2+: ~$6K/year
The ROI from rate shopping alone typically covers the integration cost within 2–3 months.
Frequently Asked Questions
Can ShipStation handle international shipping from NetSuite?
Yes. ShipStation supports international labels for UPS, FedEx, DHL, and USPS. It can generate customs forms (commercial invoices, CN22s) using product data synced from NetSuite (HS codes, declared values, country of origin). Make sure your NetSuite items have HS codes populated if you ship internationally.
How do I handle hazmat or oversized shipments?
ShipStation can flag shipments as hazardous or oversized, but carrier-specific hazmat requirements (UN numbers, proper shipping names, packaging types) may need to be managed outside ShipStation. These are typically handled through the carrier's direct portal for compliance purposes.
Can I use ShipStation for B2B/wholesale orders?
Yes, but B2B shipping has different requirements — palletized freight, LTL carriers, BOL generation. ShipStation is designed primarily for parcel shipping. For B2B freight, consider FreightPop or ShipHawk alongside ShipStation for parcel orders.
What happens if ShipStation is down?
You can't generate labels or rate-shop. Most carriers offer direct label printing through their websites as a fallback. Have carrier portal credentials available for your warehouse team as a backup. Manually enter tracking numbers into NetSuite until ShipStation comes back online.
Can multiple warehouse teams use ShipStation simultaneously?
Yes. ShipStation supports multiple users and multiple warehouses. Each warehouse can have its own view, carrier accounts, and automation rules. User permissions control what each team member can access.
What Should You Do Next?
Shipping integration might not be as exciting as ecommerce platform or marketplace integrations, but it directly impacts your customer experience, your shipping costs, and your warehouse efficiency. Getting ShipStation and NetSuite connected properly eliminates the manual work that slows down fulfillment and introduces errors.
Start by evaluating your current shipping workflow: how many shipments per month, which carriers you use, whether you need rate shopping, and how returns are handled today. That assessment will tell you which integration approach makes sense.
Take our free integration assessment to get a customized recommendation for your ShipStation + NetSuite integration, including the right connector approach, carrier optimization strategy, and expected ROI from rate shopping.