What we do
Tools
Industries
Department
How we workLet's talk →
Home/ShipStation/ShipStation NetSuite Workflows and Missing Orders
ShipStation + NetSuite

ShipStation NetSuite Integration: Four Workflows, and the Orders That Don't Import

Orders get approved in NetSuite, the warehouse prints labels in ShipStation, and someone still copies tracking numbers back by hand. That part has an answer now: ShipStation connects to NetSuite directly, with no middleware in between, and it's included on every ShipStation plan. Orders come in from NetSuite, and fulfillment and tracking go back. The fulfillment workflow you choose decides which NetSuite records ShipStation reads, so it's the setting to get right first.

ShipStation's four NetSuite fulfillment workflows

You choose one when you add NetSuite under Settings, then Selling Channels, in ShipStation. A NetSuite admin has to enable SuiteCloud Client and Server SuiteScript first.

How your warehouse works Workflow to pick What to watch
Orders ship straight from the approved sales order, with no picking step in NetSuite Sales Order, the default. Orders still in Pending Approval stay in NetSuite, and so does any order without a Ship-To address.
Staff pick in NetSuite, then hand the order to shipping PickPackShip (Picked): ShipStation reads item fulfillments in Picked status. An order only reaches the label queue once its item fulfillment exists and is marked Picked.
Picking and packing both happen in NetSuite, and ShipStation only labels PickPackShip (Packed): item fulfillments in Packed status. If packers forget to mark the fulfillment Packed in NetSuite, ShipStation never sees the order.
Stock moving between your own warehouses Transfer Orders. This one is for moves between locations. Customer orders need one of the other three.

NetSuite orders that never show up in ShipStation

The integration has a few firm rules about what it imports. These are the ones that leave the queue short.

The order is still waiting for approval

How you'll know: It's in NetSuite with every line filled in, but ShipStation doesn't have it.

Fix: Orders in Pending Approval don't import. Approve it, or loosen whatever approval rule is holding orders like it.

No Ship-To address on the order

How you'll know: Web orders arrive, but orders keyed in by staff, such as phone or wholesale ones, are missing.

Fix: ShipStation needs a Ship-To address before it imports an order. Make that field required on the forms your team uses to enter orders.

One filter, and a warehouse rule that needs two

How you'll know: The second warehouse's orders land in the first one's queue, or nowhere.

Fix: The integration takes a single order filter, by location, class or department. When the real rule mixes those, n-frames writes a NetSuite script that sets the one value the filter reads, from the rule you actually use.

Packers need a fourth NetSuite field

How you'll know: Gift note, customer PO and delivery window are mapped, and now someone wants the dock instructions too.

Fix: The native integration maps up to three extra NetSuite body fields into ShipStation's custom fields 1, 2 and 3. Past that, the extra details have to be combined into one of those fields before import, which a small script in NetSuite can do.

The same store order arrives twice

How you'll know: A Shopify order sits in ShipStation once from the store connection and once from NetSuite.

Fix: Give each sales channel one route in: either the store connection in ShipStation or the order coming through NetSuite, not both. Whichever one you drop, confirm how tracking will reach the storefront afterwards.

ShipStation's own NetSuite link or Oracle's NetSuite Connector

Two routes carry both product names. They work quite differently.

Built by ShipStation

Direct NetSuite integration

  • Set up inside ShipStation with your NetSuite Account ID, over OAuth 2.0. The NetSuite role you use must allow OAuth 2.0 access tokens.
  • Four fulfillment workflows, one order filter and up to three mapped custom fields.
  • Included on every ShipStation plan.
  • Orders come in from NetSuite. Fulfillment and tracking information go back.
Part of NetSuite Connector

Oracle's ShipStation Connector

  • NetSuite Connector acts as the marketplace, and ShipStation picks orders up from it through a ShipStation custom store.
  • Sends orders or pick tickets over and brings fulfillment data back into NetSuite.
  • It only syncs fulfillments for orders it sent itself, and each custom store needs its own connector account.
  • Weight doesn't come back from ShipStation, so item fulfillments show 1 pound by default.

Starting fresh, the direct integration is the shorter path. Oracle's route mainly makes sense when NetSuite Connector already runs your other sales channels.

Label cost, package weight and the books

ShipStation's own pages describe fulfillment and tracking going back to NetSuite. They don't spell out where each label's cost lands. Ship one test order, open its item fulfillment, and look before finance builds a shipping margin report on the assumption that it's there.

Where the cost or the real package weight is missing, n-frames writes it in: each label's cost and weight read from ShipStation's shipment records through the ShipStation API, then posted to the item fulfillment, a custom field or a freight line in NetSuite, wherever your accountant reports from and NetSuite's API allows.

Stores that send orders to ShipStation straight from the storefront have the same cost question in another shape, covered on the ShipStation and Shopify page. And if QuickBooks Online keeps the books instead of NetSuite, ShipStation's QuickBooks integration sends sales receipts one way, which leaves invoiced customers and per-order label cost to a separate build.

Before you switch the NetSuite connection on

Does ShipStation integrate with NetSuite?

It does, directly. ShipStation's own NetSuite integration imports orders from NetSuite and returns fulfillment and tracking information, without a third-party integrator. You add it from the selling channels settings in ShipStation, and it's included on every plan.

Is there a ShipStation connector for QuickBooks?

There is one for QuickBooks Online. It sends sales receipts from ShipStation into QuickBooks, in one direction. ShipStation's page for it doesn't mention QuickBooks Desktop, invoices or label costs, so a business that bills on invoices, or wants shipping cost per order in its books, needs that part built.

Can middleware tools connect ShipStation to NetSuite?

Yes, and before the direct integration they were the way to do it. Oracle's NetSuite Connector links through a ShipStation custom store, and NetSuite partners sell their own connectors, some built on Celigo's integrator.io. They earn their place when one connector already runs your other channels. For a plain NetSuite and ShipStation link, try the free direct integration first.

What data actually needs to move between ShipStation and NetSuite?

Orders into ShipStation with a Ship-To address and the extra fields packers rely on. Coming back: tracking, carrier and shipment status against the order or its item fulfillment, plus label cost and package weight if anyone reports on shipping margin. Test those last two on a real order, since ShipStation's pages don't list them.

Does the ShipStation NetSuite integration work with pick, pack and ship?

Yes. The PickPackShip (Picked) and PickPackShip (Packed) workflows read NetSuite item fulfillments in those statuses, so the picking or packing step happens in NetSuite and ShipStation prints the label after it.

Who builds the pieces the native integration leaves out?

That's the work n-frames takes on for ShipStation and NetSuite users: label cost and weight written onto the NetSuite record finance uses, extra order details folded into the three custom fields, and orders from systems that never pass through NetSuite sent to ShipStation through its API.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.