Key takeaways
- The core retail EDI cycle in NetSuite is 850 in as a sales order, then 855, 856 and 810 out from the sales order, item fulfillment and invoice, plus 846 inventory if the retailer asks.
- SPS Commerce, TrueCommerce and Orderful all offer NetSuite integrations; SPS and TrueCommerce price on quote, Orderful publishes Web EDI at $189 per trading partner per month and Integrated from $399 per month.
- The 856 ASN is where most chargebacks start: carton hierarchy, SSCC labels and timing have to match what actually shipped.
- VAN or AS2 is a transport choice; the mapping into NetSuite records and the exception handling are the real work.
- A custom EDI layer for the first trading partner takes about 304 to 710 hours; each further partner is mostly mapping and testing.
NetSuite EDI integration connects NetSuite to your retail trading partners so their 850 purchase orders arrive as sales orders and your 855 acknowledgments, 856 advance ship notices and 810 invoices go back automatically. Most suppliers use an EDI provider with a NetSuite SuiteApp, such as SPS Commerce, TrueCommerce or Orderful; an integration platform or a custom layer makes sense when your order rules do not fit a standard sales order flow.
We are integration engineers, not an EDI provider or a NetSuite reseller, so this guide focuses on the records, the mapping and the failure points. Prices are list prices as published by each vendor in November 2026. We have not published a NetSuite or EDI case; the patterns below come from order, shipping and inventory syncs we built on other systems.
What moves between NetSuite and the trading partner
Retail EDI uses X12 transaction sets, each with a three-digit number. A typical supplier to a big-box retailer exchanges these:
- 850 Purchase Order (in). Becomes a NetSuite sales order. You need the retailer’s PO number, ship-to or distribution center code, ship window, items by the retailer’s item number or UPC, and unit prices.
- 860 Change Order (in). Updates the sales order: quantities, dates, cancelled lines.
- 855 PO Acknowledgment (out). Confirms, changes or rejects each line, from the sales order.
- 856 Advance Ship Notice (out). Built from the item fulfillment: shipment, order, carton and item levels, with an SSCC barcode per carton that matches the GS1-128 label on the box.
- 810 Invoice (out). From the NetSuite invoice, with the retailer’s PO number and line references.
- 846 Inventory Advice (out). Available quantity by item, if the retailer wants it.
- 997 Functional Acknowledgment for every document, and often 824 Application Advice when the retailer rejects one.
If you ship through a 3PL, warehouse EDI (940 out, 945 back) sits between the 850 and the 856. That side is covered in our NetSuite 3PL and WMS integration guide. This article stays with trading-partner EDI.
VAN or AS2? A value-added network is a hosted mailbox that relays files between partners and usually bills for traffic. AS2 sends files directly over the internet with certificates and signed receipts. Many large retailers require AS2; smaller partners often sit on a VAN. An EDI provider typically supports both, which is one reason few suppliers run their own translator.
Your options
| Option | Best for | What it covers | Pricing as published | Limits |
|---|---|---|---|---|
| SPS Commerce Fulfillment for NetSuite | Suppliers to many large retailers who want a full-service model | Built for NetSuite program member; ASN module for all fulfillment models, retail packing slips, PDF orders in the same workflow; SPS manages map and spec changes, testing and partner communication | Quote-based | Works best when your process follows standard NetSuite sales order and fulfillment flows |
| TrueCommerce EDI for NetSuite | Suppliers wanting order-to-cash, procure-to-pay and warehouse EDI in one integration | Built for NetSuite certified, uses SuiteTalk web services; EDI, flat file or API connectivity; validation of prices and PO numbers | Quote-based | Prices not published; check transaction scope for your partners |
| Orderful with NetSuite SuiteApp | API-first teams, growing partner counts | Free SuiteApp per Orderful; 850, 860, 855, 856, 810, 846, 940, 945 and more; inbound sync about every 15 minutes | Web EDI $189 per trading partner per month; Integrated from $399 per month; Enterprise custom (over 20 partners) | Vendor claims (under 9 days per partner on average) depend on retailer testing |
| iPaaS with EDI steps | Teams already licensing an integration platform | Translation plus NetSuite steps in one flow | Quote-based | You own maps, partner testing and compliance changes |
| Custom layer | Unusual order models: kits, split POs, store-level allocation, custom pricing | Provider or AS2 transport plus your own NetSuite mapping and rules | About 304 to 710 hours for the first partner (see estimator) | You own monitoring and spec changes |
For most suppliers with standard flows, a provider is the shortest path, because the provider also maintains each retailer’s map as specs change. SPS says its team handles 9,000 retailer changes a year. A custom layer earns its cost when NetSuite has been customized heavily, when one 850 has to become several sales orders by store or warehouse, or when the provider’s NetSuite integration cannot express your pricing or kit rules. Often the answer is a hybrid: the provider handles transport and partner maps, and a small custom service handles the NetSuite side.
Where these integrations break
1. Item and unit mismatches. The retailer orders by its own item number, UPC or GTIN, in cases of 6, while NetSuite sells in eaches. Fix: keep a cross-reference per partner (retailer item, UPC, NetSuite item, unit and pack size) and reject unknown items to a review queue instead of creating the order with the wrong line.
2. Price disagreements. The 850 price differs from your price list. If you invoice your price, the 810 is rejected or short-paid. Fix: validate the PO price on arrival, flag differences before the 855 goes out, and invoice the agreed price.
3. Wrong or late 856. The ASN must describe exactly what is on the truck, carton by carton, and arrive before the goods. A carton hierarchy built from the order instead of the actual pack, or an ASN sent after delivery, is a classic chargeback. Fix: build the 856 from packing data (which carton holds what), generate SSCC labels from the same data, and send on ship confirmation, not at invoicing.
4. Duplicate or out-of-order documents. A resent 850 creates a second sales order; a 860 arrives before its 850. Fix: key every inbound document on partner plus PO number plus control number, hold changes until the original exists, and make outbound sends idempotent.
5. Partial shipments and backorders. You ship 80% now and the rest next week. Some retailers accept that; others want the remainder cancelled. Fix: encode each partner’s backorder rule, and make sure each shipment produces its own 856 and the 810 matches what shipped, not what was ordered.
6. Ignored acknowledgments. 997s and 824s that nobody reads mean a rejected invoice surfaces weeks later as a short payment. Fix: track an acknowledgment for every outbound document and alert when one is missing or negative.
7. Volume spikes against NetSuite limits. NetSuite caps concurrent web services and RESTlet requests per account and shares that cap across integrations, so a seasonal wave of 850s can collide with your other syncs. Fix: queue inbound documents and process them at a controlled rate, with retries.
8. Ship windows and routing rules. Each 850 carries a ship-not-before and cancel-after date, and many retailers require you to request a pickup through their routing process instead of choosing a carrier yourself. Shipping early, late or with the wrong carrier is a compliance violation even when the goods and documents are perfect. Fix: store the window on the sales order, block fulfillment outside it unless someone overrides it, and record the routing reference so it appears on the 856.
Compliance chargebacks deserve their own line in the budget. Retailers publish penalty schedules in their vendor manuals, and the deductions arrive on remittances weeks after the shipment, so nobody connects them to the cause. Before go-live, list each partner’s penalties next to the failure point that triggers them, and make the integration log enough detail (ASN send time, carton contents, label data) to dispute a deduction with evidence.
What a custom integration costs
A custom EDI layer is mostly partner mapping, validation, and the 856. For the first trading partner, with 850, 855, 856 with labels, 810, acknowledgment tracking, NetSuite field setup, transport and partner testing, plan for about 304 to 710 hours. At Eastern European rates that is about $10,600 to $56,800; at US onshore rates about $24,300 to $113,600. With two engineers that is roughly 5 to 12 weeks of build time, plus the retailer’s test calendar.
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. Change orders, inventory feeds and compliance rules add hours; extra partners are cheaper than the first. Pick your scope below.
These are engineering hours only. Provider subscriptions, VAN traffic and label hardware come on top. If a provider’s NetSuite SuiteApp covers your flows, you may need only the mapping and testing modules.
How to run the project
- Collect each partner’s EDI guide. Retailers publish implementation guides with required segments, label specs, routing rules and chargeback terms. Read them before scoping.
- Map to NetSuite. Decide which NetSuite fields hold the retailer PO, ship-to and DC codes, ship window and partner item numbers. Add custom fields where needed, and clean the item cross-reference.
- Set up transport. VAN mailbox, AS2 certificates or your provider’s network, plus test and production identifiers.
- Test with the partner. Most retailers run a test phase: test 850s in, your 855, 856 and 810 back, often with physical label checks. Script edge cases: split shipments, cancelled lines, price mismatches.
- Go live with the first real orders watched end to end, from 850 to payment.
- Add partners. Reuse the core and map each new partner; most of the work is their spec and their testing.
If retail EDI sits beside direct-to-consumer channels, see our NetSuite ecommerce integration guide and the NetSuite integration overview. For choosing the ERP itself, see best ERP for retail and best ERP for wholesale distribution.
From related work
We have not published a NetSuite or EDI case. These patterns come from order, shipping and inventory syncs we built on other systems.
- One Motion ERP. An internal ERP for a manufacturing and shipping business: shipping and receiving with validation, shipment reversal, purchase-order exports, material-certificate mapping and a two-way QuickBooks sync. Ordered, received and invoiced quantities are checked against each other, the same check an 810 needs against the 856.
- Custom ERP with QuickBooks sync. Inventory, orders, vendors and purchase orders in one system, with purchase orders and vendor data synced to QuickBooks.
- Aspect. Orders from 7 Amazon marketplaces with order and stock sync every 15 minutes, turned into production jobs without retyping.
- SaaS ETL platform. Connectors, scheduled transfers and real-time monitoring, with failed records counted separately, which is the visibility an EDI layer needs.
Our two-way QuickBooks sync guide explains the ID mapping and retry design we reuse in every order sync.
Where OSKI fits
We build integrations and custom ERP modules on .NET and React. If an EDI provider’s NetSuite integration covers your partners, use it. If your order model does not fit, we can build the NetSuite-side layer behind your provider, from mapping to partner testing. See integrations, ERP development and e-commerce development.
- Retailer → 850 purchase order creates a sales order (860 changes update it) NetSuite
- NetSuite → 855 acknowledgment from the sales order: accepted, changed or rejected lines Retailer
- NetSuite → 856 ASN from the item fulfillment: cartons, SSCC labels, items per carton Retailer
- NetSuite → 810 invoice from the NetSuite invoice Retailer
- NetSuite → 846 inventory advice: available quantity by item Retailer
- Retailer ⇄ 997 acknowledgments and 824 rejections: often not surfaced to anyone NetSuite
● Works natively● Partial or one-way● Needs custom work
X12 transaction sets. The flow figure shows the most common retail cycle; your retailers' guides decide the exact set.
- Retailer maps maintained for you
- NetSuite SuiteApp or built-for-NetSuite integration
- Per-partner or quote-based fees
- Fits standard sales order flows
- Good if you already license one
- EDI steps plus NetSuite steps
- You still own maps and tests
- Platform fees on top
- Your rules for splits, kits, pricing
- Fits unusual NetSuite setups
- About 304 to 710 hours for the first partner
- You own monitoring and changes
Pricing and capabilities as published by each vendor in November 2026.
- 01 Collect partner guides
Each retailer's specs, labels and routing rules.
- 02 Map to NetSuite
Fields, items, ship-to codes, units.
- 03 Set up transport
VAN, AS2 or the provider's network.
- 04 Test with the partner
Test 850s through to 810, label checks.
- 05 Go live in production
First real orders watched end to end.
- 06 Add partners
Reuse the core, map and test each one.
Estimate your NetSuite EDI integration
Pick the documents and features you need for your first trading partner. 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:
- X12: Transaction sets
- SPS Commerce: Fulfillment for NetSuite
- TrueCommerce: NetSuite EDI integration
- Orderful: EDI integration with NetSuite guide
- Orderful: Pricing
- Oracle NetSuite Help: NetSuite Concurrency Limits




