Key takeaways
- Every 3PL integration has the same five flows: orders out, fulfillments and tracking back, inventory snapshots, inbound receipts and returns. Scope them one by one.
- Oracle says its legacy FedEx, UPS and USPS integration is closed to new customers; NetSuite Ship Central is now the standard in-house shipping option.
- ShipStation states its native NetSuite integration is included in every plan; plans start at $14.99 per month on monthly billing.
- EDI 940, 945, 944 and 846 are just one transport. The hard part is still mapping units, lots, partial shipments and cutoffs.
- A custom integration with one 3PL typically takes about 344 to 730 hours, depending on lots, returns and how many warehouses you run.
A NetSuite 3PL integration sends sales orders from NetSuite to your third-party warehouse and brings back shipments, tracking numbers, lot or serial numbers and inventory levels, usually through the 3PL’s API, EDI or a shipping platform such as ShipStation. You can buy a prebuilt connector if your 3PL or shipping tool is supported, use an EDI provider, or build a custom integration when your rules do not fit either.
We are integration engineers, not a NetSuite reseller, so this guide is about the data: which records move, what breaks, and what each path costs. Prices are list prices as published by each vendor in November 2026. We have not published a NetSuite case; the patterns below come from shipping, inventory and order syncs we built on other systems.
What moves between NetSuite and the 3PL
Whatever the transport, a 3PL or WMS integration carries five flows. Scope each one separately, because prebuilt tools often cover the first two well and the last three partly or not at all.
- Orders out. Approved sales orders (or pick tickets, if you use pick-pack-ship) go to the 3PL with ship-to, items, quantities, carrier, service level and any packing instructions. In X12 terms this is the 940 Warehouse Shipping Order.
- Fulfillments back. The 3PL confirms what shipped: quantities per line, cartons, weights, tracking numbers, and lot or serial numbers. In NetSuite this becomes an item fulfillment. In X12 it is the 945 Warehouse Shipping Advice.
- Inventory. The 3PL sends on-hand snapshots (846, or 947 for adjustments) or an API endpoint you poll. NetSuite should reconcile against them, not blindly overwrite its own numbers.
- Inbound. Purchase orders or transfer orders go to the 3PL so it can expect the goods; the 3PL returns receipts (944) that become item receipts in NetSuite.
- Returns. RMAs go out, and the 3PL reports what came back, in what condition and whether it went back to stock.
EDI is one transport among several. Plenty of 3PLs run modern WMS platforms with REST APIs or accept CSV files over SFTP. The mapping work is the same in all three cases. If you also trade with retailers over EDI, our NetSuite EDI integration guide covers the 850, 856 and 810 side, which often feeds the same warehouse flows.
Your options
Most companies combine two of these: NetSuite or a shipping platform for labels and carriers, and a 3PL link for orders and stock. Here is how the main paths compare.
| Option | Best for | What it covers | Pricing as published | Limits |
|---|---|---|---|---|
| NetSuite Ship Central | Shipping from your own warehouse | Labels on item fulfillments for FedEx, UPS and USPS, packing, manifests | Part of your NetSuite agreement; quote-based | Not a 3PL link. Oracle says the older FedEx, UPS and USPS/Endicia integration is closed to new customers |
| ShipStation native NetSuite integration | Brands shipping parcels from their own or a 3PL’s site through ShipStation | Sales order, pick-pack-ship (picked or packed) and transfer order workflows; fulfillment data back; custom body fields | Included in every ShipStation plan, per ShipStation; plans from $14.99/month (Starter, 50 shipments, monthly billing) | Parcel shipping, not stock or inbound receipts |
| NetSuite Connector (ShipStation connector) | Teams already on NetSuite Connector for storefronts | Orders or pick tickets out; shipments back as item fulfillments | Quote-based | Weight is not synced (fulfillments default to 1 lb); only orders created through the connector can be fulfilled |
| Shipwell SuiteApp | Freight and TMS workflows | One NetSuite order to one Shipwell order; shipment IDs and settlement documents back | Quote-based | Later Shipwell changes do not sync back; multiple NetSuite orders cannot be combined on one shipment |
| EDI provider (940/945/944/846) | 3PLs that require EDI | Provider handles transport, translation and partner maps | Quote-based or per-partner monthly fees | Mapping into NetSuite and exception handling still need work |
| iPaaS flow | Teams with an integration platform already licensed | Prebuilt NetSuite steps plus the 3PL’s API | Quote-based | Platform and flow upkeep; complex rules end up as scripts anyway |
| Custom integration | Several 3PLs, lots or serials, returns, unusual rules | Every flow above, your rules, your monitoring | About 344 to 730 hours for one 3PL (see estimator) | You own maintenance and changes |
Oracle lists ShipStation as the logistics option on its NetSuite Connector list of supported storefronts and 3PLs. If your 3PL is not on any connector’s list, you are choosing between EDI, an iPaaS and custom code. A TMS such as Shipwell is a different job: it books freight and tracks loads, and Shipwell says it uses EDI 204, 990 and 214 with carriers while mirroring those events in NetSuite.
A quick way to decide: if a connector covers orders, fulfillments and tracking and you ship in eaches without lots, start there. If you need lots, serials, partial shipments with backorders, multiple 3PLs or returns, price the custom option before you commit to a workaround.
Where these integrations break
These are the failures we plan for in any warehouse integration. None of them are NetSuite-specific bugs; they come from two systems that model the warehouse differently.
1. Units of measure. NetSuite may sell in cases while the 3PL picks in eaches, or the reverse. If the integration sends “2” without the unit, the warehouse ships 2 eaches instead of 2 cases of 12. Fix: map units explicitly per item, convert at the boundary and reject lines with an unknown unit instead of guessing.
2. Partial shipments and splits. A 3PL ships 7 of 10 today and 3 next week, or splits one order across cartons and carriers. A connector that expects one shipment per order either closes the order early or ignores the second shipment. Fix: create one item fulfillment per shipment, keyed on the 3PL’s shipment ID, and leave the remainder open or backordered by rule.
3. Lots, serials and expiry dates. If NetSuite tracks lots, every fulfillment needs the lot numbers the 3PL actually picked, with quantities per lot. Missing lots stop the fulfillment from saving. Fix: make lot and serial capture a required part of the 945 or API payload, and validate it against NetSuite before posting.
4. Order cutoffs and holds. Orders approved after the 3PL’s daily cutoff, or edited after release, cause ships with old addresses or cancelled lines. Fix: release orders on a schedule that matches the cutoff, lock lines once sent, and route changes after release through a cancel-and-resend flow the 3PL agrees to.
5. Duplicate messages. Retries, resent files or a 945 sent twice create duplicate fulfillments and wrong stock. Oracle’s own ShipStation connector FAQ warns that old orders can reappear when automations re-save unchanged records. Fix: make every message idempotent with a unique external ID, and only resend when a value actually changes.
6. Inventory drift. Snapshots that overwrite NetSuite’s on-hand hide shrinkage and missed receipts. Fix: compare the 3PL snapshot to NetSuite by item and location, post adjustments only within a tolerance, and send larger gaps to a person.
7. Concurrency and silent failures. NetSuite caps concurrent web services and RESTlet requests per account and shares that cap across integrations, so a busy integration can starve another. Fix: queue writes, retry with backoff, and alert on stuck records instead of letting them fail quietly.
What a custom integration costs
A custom NetSuite 3PL integration is mostly mapping, validation and error handling, not API calls. For one 3PL with orders, fulfillments with tracking, inventory reconciliation, inbound receipts, an error queue, monitoring and testing with the 3PL, plan for about 344 to 730 hours. At Eastern European rates that is about $12,000 to $58,400; at US onshore rates about $27,500 to $116,800. With two engineers, that is roughly 6 to 12 weeks of build time.
For the rate bands: 2026 outsourcing rate surveys put Eastern Europe at about $35 to $80 per hour and North America at $80 to $180 or more; we use $80 to $160 for US onshore. Lots and serials, returns, EDI transport and a second 3PL each add hours. Tick what you need below.
The low end assumes a 3PL with a documented REST API, a clean item master and one warehouse. The high end assumes EDI through a provider, lot-controlled items, several fulfillment workflows and a 3PL that needs more test rounds.
How to run the project
- Map every flow and field. List the five flows, which ones you need at launch, and the fields in each. Pull a sample of real orders: multi-line, kits, lot-controlled items, international ship-tos.
- Agree on transport and IDs. API, EDI or SFTP; how each side identifies items, orders and shipments; schedules; who resends what when something fails.
- Build in a NetSuite sandbox against the 3PL’s test environment, with a dedicated integration role and token-based or OAuth 2.0 credentials.
- Test with the 3PL. Run scripted scenarios together: split shipments, short picks, lot picks, address changes after release, a cancelled line, a return. Most 3PLs have a test window; book it early.
- Parallel run. Keep the old process alive for a week or two and reconcile stock daily.
- Go live and watch. Turn on alerts for stuck orders and failed messages, and keep the team close for the first weeks.
If you sell through Shopify or other channels, decide where orders enter NetSuite before you wire the warehouse; our Shopify NetSuite integration guide and NetSuite ecommerce integration guide cover that side, and the NetSuite integration overview maps all the common connections.
From related work
We have not published a NetSuite case. These patterns come from shipping, inventory and order syncs we built on other systems.
- One Motion ERP. We develop and support an internal ERP for a manufacturing and shipping business. Shipping and receiving gained validation, shipment reversal, purchase-order exports and material-certificate mapping, and weights convert between LB, KG, STON and MTON, which is the unit problem above in practice. It also runs a two-way QuickBooks sync.
- Custom ERP with QuickBooks sync. Inventory, orders, vendors and purchase orders in one system, with orders fulfilled 20% faster after launch.
- Aspect. Orders from 7 Amazon marketplaces with order and stock sync every 15 minutes, routed to production lines.
- Peregrine Ship. Sourcing and shipment tracking inside a dropshipping and fulfillment platform: the system places supplier orders, imports tracking numbers and updates warehouse inventory on arrival.
- SaaS ETL platform. Connectors, scheduled transfers and real-time monitoring of each run, with failed records counted separately, which is the monitoring layer a 3PL sync needs.
For the general sync design questions (IDs, conflicts, retries), see our two-way QuickBooks sync guide, and for system choice, best ERP for wholesale distribution.
Where OSKI fits
We build integrations and custom ERP modules on .NET and React, and support them in production. If a connector covers your 3PL, use it. If it does not, or your lots, splits or returns break it, we can map the flows, build the service and run the testing with your 3PL. See integrations, ERP development and e-commerce development.
- NetSuite → Sales orders or pick tickets, ship-to, carrier and service level (EDI 940 or API) 3PL / WMS
- 3PL / WMS → Shipments as item fulfillments: tracking, cartons, lots and serials (EDI 945 or API) NetSuite
- 3PL / WMS → Inventory snapshots and adjustments (EDI 846/947 or API), reconciled not overwritten NetSuite
- NetSuite → Inbound purchase orders and ASNs from suppliers 3PL / WMS
- 3PL / WMS → Receipts against those purchase orders (EDI 944 or API) NetSuite
- 3PL / WMS ⇄ Returns: RMA out, condition and restock back; rarely covered by prebuilt connectors NetSuite
● Works natively● Partial or one-way● Needs custom work
Transaction numbers are X12 warehouse sets; many 3PLs offer the same flows over REST or SFTP files.
- Fastest start
- Fixed set of flows and fields
- Fits when your 3PL or platform is on the list
- Limits show up with lots, returns and splits
- What many established 3PLs expect
- Provider handles transport and maps
- Monthly fees per partner
- Exceptions still land in NetSuite
- Any flow, any field
- Your rules for lots, splits, cutoffs
- You own monitoring and changes
- About 344 to 730 hours for one 3PL
Pricing and capabilities as published by each vendor in November 2026.
- 01 Map flows and fields
Five flows, units, lots, status codes.
- 02 Agree on transport
API, EDI or SFTP, plus IDs and schedules.
- 03 Build in sandbox
NetSuite sandbox against the 3PL test site.
- 04 Test with the 3PL
Real orders, splits, lots, returns, cutoffs.
- 05 Parallel run
Reconcile stock daily before switching off manual.
- 06 Go live and watch
Alerts, error queue, two weeks of hypercare.
Estimate your NetSuite 3PL integration
Pick the flows you need for one 3PL or WMS. Hours include design, QA and project management. Change the rate band and team size to see cost and calendar time.
Sources
Based on the following official vendor and regulator materials:
- Oracle NetSuite Help: Shipping Integration with FedEx, UPS, and USPS/Endicia
- Oracle NetSuite Help: ShipStation Connector FAQ
- Oracle NetSuite Help: NetSuite Connector Supported Storefronts and 3PLs
- ShipStation: NetSuite integration
- ShipStation: Pricing
- Shipwell Help Center: NetSuite SuiteApp current capabilities





