NetSuite EDI integration: trading with retailers without retyping
Large retailers and distributors send purchase orders and expect advance ship notices and invoices back as EDI documents, on their schedule and in their format. A NetSuite EDI integration turns those documents into sales orders and sends the replies from NetSuite’s fulfillments and invoices.
- Updated
- October 5, 2026
- Written by
- Nitya Hoyos
- Covers
- Approach, cost, mapping
- Questions
- 6 answered below
(01)The situation
The core cycle for a supplier is short: the retailer sends an 850 purchase order, you may reply with an 855 acknowledgment, you ship and send an 856 advance ship notice, and you bill with an 810 invoice. Every document gets a 997 functional acknowledgment. Many retailers also want 846 inventory updates. In NetSuite terms, the 850 becomes a sales order, the 856 is built from the item fulfillment, and the 810 from the invoice.
The hard part is that every trading partner has its own implementation guide. Two retailers both sending an 850 will use different segments, different item identifiers (UPC, their own item number, your SKU) and different rules about what the ASN must contain. The 856 is the strictest: it often has to describe every carton and its contents, with GS1-128 carton labels that match. Late or wrong ASNs lead to chargebacks, which can cost more than the integration.
For that reason most NetSuite users work with a full-service EDI provider that keeps the partner maps, runs the connection to each retailer and handles certification testing. The integration work on the NetSuite side is mapping the provider’s documents to sales orders, fulfillments and invoices, and making sure the data the ASN needs, such as carton contents, exists in NetSuite before shipping.
(02)What it costs
Cost and timeline by approach
Connector
$3,500–$9,500
35–77 hours · 2–3 weeks
Middleware
$7,000–$20,000
75–159 hours · 3–6 weeks
Custom code
$15,500–$43,500
165–347 hours · 6–12 weeks
For a two-way NetSuite–EDI trading partners integration moving items & catalog, sales orders, fulfillments & tracking, invoices & payments, at medium volume with hourly sync and some existing NetSuite customization. Hours are priced at $95–$125 an hour and include discovery and 15% for testing and cutover. Connector and middleware figures leave out license fees, which are paid to the vendor. These are estimates from the published method, not a quote.
(03)The options
Which approach fits
| Approach | Best for | Trade-off |
|---|---|---|
| Full-service EDI provider with a NetSuite integration (e.g. SPS Commerce, TrueCommerce) | Most suppliers: the provider maintains each retailer’s map and certification. | Per-partner and per-document fees for as long as you trade. |
| EDI translator or VAN + your own mapping | Teams with EDI knowledge and many partners. | You maintain every partner map and run certification yourselves. |
| Custom NetSuite side on top of a provider | Carton-level ASNs, kits, or rules the provider’s NetSuite app does not cover. | Two systems to monitor: the provider and your code. |
(04)Field mapping
Mapping decisions that matter
| Source | NetSuite | Note |
|---|---|---|
| 850 purchase order | Sales order | Retailer PO number as external ID; reject duplicates. |
| 850 item identifier (UPC / buyer part no.) | Item: UPC or cross-reference | Keep a per-partner cross-reference for buyer item numbers. |
| 856 advance ship notice | Item fulfillment + package/carton data | Carton contents must be recorded before the ASN is sent. |
| 810 invoice | Invoice | Prices must match the PO, or the retailer short-pays. |
| 997 functional acknowledgment | (provider log) | Alert on missing 997s; a silent failure means a missed chargeback window. |
(05)Where it goes wrong
The mistakes that cost the most
- 01Each retailer certifies your documents before going live, and testing often takes weeks on their schedule, not yours. Plan the timeline around it.
- 02ASNs built from what was ordered instead of what was packed cause receiving errors at the retailer and chargebacks.
- 03Price differences between the PO and your NetSuite price levels must be resolved before invoicing; invoicing your price instead of theirs leads to deductions.
- 04Item cross-references kept in a spreadsheet instead of NetSuite break the first time someone adds a new product for one retailer.
- 05Carton labels (GS1-128) printed from a different system than the one that builds the ASN end up with numbers that don’t match, and the retailer’s receiving dock rejects or fines the shipment.
(06)Before you build
When not to do this
If you have one EDI partner and low volume, a web EDI portal from a provider, where someone keys documents by hand, can be cheaper than integrating. Integrate when the order count or the chargebacks make manual entry the larger cost.
(07)Questions
Does NetSuite support EDI?
NetSuite does not include an EDI translator, so most companies use an EDI provider with a NetSuite integration, which turns EDI documents into NetSuite transactions and back.
Which EDI documents do suppliers need?
Most retailers require the 850 purchase order, 856 advance ship notice and 810 invoice, plus 997 acknowledgments. Some also require the 855 order acknowledgment, 846 inventory and 860 PO changes.
How much does NetSuite EDI cost?
Two parts: the EDI provider’s fees, usually a setup fee per trading partner plus a monthly or per-document charge, and the work to connect the provider to NetSuite, sized in the cost table above. Chargebacks avoided often pay for the integration; a late or wrong ASN can cost more than the document fees.
What is an ASN, and why do retailers charge back for it?
An ASN (EDI 856, advance ship notice) tells the retailer exactly what is in each carton before the truck arrives, so their dock can receive it by scanning labels. If the ASN is late, missing or doesn’t match the cartons, receiving slows down, and most large retailers pass that cost back to the supplier as a chargeback.
Can you connect NetSuite to the EDI provider we already use?
Usually, yes. Most EDI providers exchange documents through an API, SFTP or their own NetSuite app. The audit starts by mapping what your provider already sends and receives, and where NetSuite data is missing or retyped.
How long does a NetSuite EDI integration take?
The NetSuite mapping is often a few weeks. The total depends on each trading partner’s certification testing, which runs on the retailer’s schedule and is usually the longest step.
Free checklist