EDI in NetSuite for Retail Ecommerce: SPS Commerce Setup Guide

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.

If you've ever received a purchase order from a major retailer — Target, Walmart, Nordstrom, Costco, or any national chain — you've encountered EDI. Electronic Data Interchange is the decades-old standard for business-to-business document exchange that still dominates retail supply chains. And if you're an ecommerce brand that's landed a wholesale account with a major retailer, implementing EDI in NetSuite isn't optional — it's a requirement for doing business.

In our work with ecommerce brands expanding into retail wholesale, EDI is consistently the most intimidating integration on the project list. The terminology is arcane (what's an 856 ASN?), the compliance requirements are strict (Target will fine you for late ASNs), and the setup involves a surprising number of moving parts. But once it's running, EDI automates the entire order-to-invoice cycle with your retail partners.

This guide demystifies EDI for ecommerce brands new to retail, explains the key document types, walks through SPS Commerce setup in NetSuite, and covers the compliance requirements and penalties that make getting it right so important.

Key Takeaways

• EDI is required by virtually every major retailer — it's not a nice-to-have, it's a condition of doing business
• SPS Commerce is the most popular EDI provider for mid-market brands using NetSuite, with a native SuiteApp connector
• Three core documents handle 90% of retail EDI: 850 (Purchase Order), 856 (ASN), and 810 (Invoice)
• Compliance penalties are real — late or inaccurate ASNs can result in chargebacks of 1–5% of the order value
• Budget $15K–$35K for initial EDI setup plus $5K–$15K/year for SPS Commerce fees

What Is EDI and Why Do Retailers Require It?

EDI in Plain Language

EDI is a standardized format for exchanging business documents electronically between trading partners. Instead of emailing purchase orders, faxing invoices, or using a web portal, EDI documents are transmitted computer-to-computer in a structured format that both systems can process automatically.

Think of it as an API that was invented in the 1970s and standardized in the 1980s. It predates the web, REST APIs, and JSON by decades. It uses document types identified by numbers (850, 856, 810, etc.), data formatted in fixed-width or delimited segments, and transmission protocols that range from AS2 to SFTP to VAN (Value Added Network).

Why Retailers Still Use EDI

You might wonder why retailers don't just use modern APIs. Several reasons:

1. Installed base: Retailers have invested billions in EDI infrastructure over 40+ years. Switching isn't economically justified.
2. Standardization: EDI provides a common language across thousands of trading partners. Every supplier sends documents in the same format.
3. Automation: Large retailers process millions of POs and invoices. EDI enables full automation without human intervention.
4. Compliance and audit trail: EDI provides a documented, traceable record of every business transaction.
5. Reliability: VAN-based EDI is extremely reliable — messages are guaranteed to be delivered, with acknowledgments and retries built in.

What Happens Without EDI

If a retailer requires EDI and you can't provide it, you have two options:

1. Web portal: Some retailers offer a web-based portal where you can manually view POs, enter ASNs, and submit invoices. This works for low-volume accounts but doesn't scale — if you're processing 50+ POs per week, manual portal entry is unsustainable.
2. Lose the account: Some retailers won't work with suppliers who can't do EDI. Period.

Which EDI Document Types Do You Need?

EDI has hundreds of document types, but retail ecommerce brands typically need only a handful:

850 — Purchase Order

The retailer sends you an 850 when they want to buy your products. It contains:

• Retailer's PO number
• Ship-to location (which store or distribution center)
• Line items with UPC/EAN, description, quantity, and agreed price
• Requested ship date and cancel date
• Shipping instructions (carrier, routing)
• Special handling requirements (labels, packaging, pallet configuration)

In NetSuite: An incoming 850 creates a Sales Order. The EDI connector maps the retailer's item numbers (UPCs) to your NetSuite item records, sets the customer (retailer), populates the ship-to address, and creates line items with quantities and prices.

855 — Purchase Order Acknowledgment

You send an 855 back to the retailer confirming receipt of the PO. It indicates whether you can fulfill the order as requested, partially, or not at all.

• Accept: You'll fulfill the PO as requested
• Accept with changes: You can fulfill but with modifications (different quantities, different ship date)
• Reject: You can't fulfill the PO

In NetSuite: When you review and approve the sales order created from the 850, the EDI connector generates and sends an 855 back to the retailer.

856 — Advance Ship Notice (ASN)

The 856 is the most compliance-critical document. You send it to the retailer when you ship the order, before the goods arrive. It tells the retailer exactly what's in each box, on each pallet, with the carrier and tracking information.

Contents:

• Shipment-level: Carrier, tracking/PRO number, ship date, estimated delivery date
• Order-level: PO number, ship-to location
• Pack-level: Carton IDs (SSCC-18 barcodes), contents of each carton
• Item-level: UPC, quantity, lot number (if applicable)

In NetSuite: When you create an item fulfillment against the sales order (marking the order as shipped), the EDI connector generates an 856 with the shipment details and transmits it to the retailer.

Why it matters: Retailers use the ASN to prepare for receiving. Their warehouse scans the SSCC-18 barcode on each carton and automatically checks it against the ASN. If the ASN is missing, late, or inaccurate, the receiving process breaks down — and you get chargebacks.

810 — Invoice

You send an 810 to the retailer to request payment. It contains the PO number, line items shipped, quantities, prices, and total amount due.

In NetSuite: When you create an invoice against the fulfilled sales order, the EDI connector generates an 810 and transmits it to the retailer. The invoice amount should match the ASN quantities — if you shipped 95 units instead of 100, the invoice should be for 95 units.

Other Common Documents

Document	Name	Direction	When Used
820	Payment Order/Remittance Advice	Retailer → You	Retailer payment details
846	Inventory Inquiry/Advice	You → Retailer	Inventory availability updates
860	Purchase Order Change	Retailer → You	Retailer modifies a PO
865	PO Change Acknowledgment	You → Retailer	You confirm PO changes
997	Functional Acknowledgment	Both	Confirms document receipt

How Do You Set Up SPS Commerce in NetSuite?

SPS Commerce is the dominant EDI provider for mid-market brands on NetSuite. They offer a cloud-based EDI platform with a native NetSuite SuiteApp that handles document translation, transmission, and mapping.

Step 1: SPS Commerce Account Setup

1. Contact SPS Commerce and provide your retailer list. SPS will pull the EDI specifications (called "trading partner maps") for each retailer.
2. SPS maps your documents — they configure the translation between the retailer's EDI format and the data format SPS sends to/from NetSuite.
3. You receive SPS credentials — FTP/SFTP credentials for document exchange, plus access to the SPS Commerce portal for monitoring.

Step 2: Install the SPS Commerce SuiteApp

1. Install the SPS Commerce EDI SuiteApp from the NetSuite SuiteApp Marketplace.
2. Configure the connection to SPS Commerce (FTP/SFTP credentials).
3. Set up the document processing queues — inbound (850s coming from retailers) and outbound (856s, 810s going to retailers).

Step 3: Configure Trading Partner Settings

For each retailer:

1. Create a customer record in NetSuite for the retailer (if not already existing).
2. Map the retailer's item numbers to your NetSuite item records. Retailers use their own item codes (often UPCs) — you need a cross-reference table that maps their codes to your internal SKUs.
3. Configure ship-to locations — retailers have multiple stores and distribution centers, each with a specific GLN (Global Location Number) or store number. Map these to NetSuite ship-to addresses.
4. Set up pricing — ensure your NetSuite price levels match the agreed wholesale pricing with each retailer.

Step 4: Configure Document Processing

Inbound 850 processing:

• SPS receives the 850 from the retailer
• SPS translates it to a format the SuiteApp understands
• The SuiteApp creates a sales order in NetSuite with mapped items, quantities, prices, and ship-to
• Your team reviews and approves the sales order

Outbound 856 processing:

• You create an item fulfillment in NetSuite
• The SuiteApp generates SSCC-18 carton labels (or you generate them externally)
• The SuiteApp creates the 856 document with shipment and carton details
• SPS translates the 856 to the retailer's format and transmits it

Outbound 810 processing:

• You create an invoice in NetSuite against the fulfilled sales order
• The SuiteApp generates the 810 document
• SPS transmits the 810 to the retailer

Step 5: Testing

Every new trading partner relationship requires testing before going live. This involves:

1. SPS sends test 850s — verify they create correct sales orders in NetSuite
2. You send test 856s and 810s — SPS and the retailer verify they're formatted correctly
3. End-to-end test — process a complete PO cycle (850 → 855 → 856 → 810) with test data
4. Retailer approval — the retailer's EDI team confirms your documents are compliant

Testing typically takes 2–4 weeks per retailer. Don't rush this — a failed test is much better than a compliance chargeback on a real order.

What Are the Compliance Requirements and Penalties?

ASN Compliance

The 856 ASN is where most compliance issues arise. Retailers enforce strict requirements:

• Timing: The ASN must be transmitted before the shipment arrives. Many retailers require it within 24 hours of ship date. Late ASNs result in chargebacks.
• Accuracy: The ASN must match what's physically in the shipment — correct items, correct quantities, correct carton IDs. Discrepancies result in chargebacks.
• SSCC-18 labels: Each carton must have a unique SSCC-18 barcode label that matches the ASN. Missing or incorrect labels prevent automated receiving.
• Carton-level detail: Many retailers require carton-level packing information — which items are in which carton. This is called "pack-level" ASN and is more complex than shipment-level ASN.

Common Penalties

Violation	Typical Penalty
Late ASN	1–3% of PO value
Missing ASN	3–5% of PO value
ASN accuracy errors	1–2% of PO value
Missing SSCC-18 labels	$0.50–$2.00 per carton
Late shipment	1–3% of PO value
Over/under shipment (outside tolerance)	Cost of discrepancy + penalty
Incorrect routing (wrong carrier)	Freight cost + penalty

These add up fast. A brand shipping $500K/year to a major retailer can easily lose $15K–$25K in chargebacks if their EDI compliance is poor. We've seen brands lose 5–8% of their wholesale revenue to chargebacks in the first year of a retail relationship — entirely preventable with proper EDI setup and operational discipline.

Retailer-Specific Requirements

Each retailer has unique requirements documented in their "routing guide" or "vendor compliance manual." These documents are typically 50–200 pages long and cover everything from label placement to pallet configuration to ASN data requirements.

Key retailers and their reputations for compliance enforcement:

• Walmart: Extremely strict. Their OTIF (On-Time In-Full) scorecard directly impacts your business relationship. Consistent failures can result in deduction of future POs.
• Target: Strict on ASN compliance and shipping windows. They use a vendor scorecard system with financial penalties.
• Amazon (Vendor Central): Moderate strictness, but their chargeback process is opaque and difficult to dispute.
• Nordstrom: Moderate. They enforce routing compliance and ASN requirements but are generally more collaborative with vendor partners.
• Costco: Strict on product and packaging specifications, less strict on EDI compliance compared to other retailers.

What Does EDI Implementation Cost?

SPS Commerce Pricing

SPS Commerce pricing is based on document volume and number of trading partners:

Component	Annual Cost
SPS Commerce platform fee	$3,000–$8,000
Per-document fees (850, 856, 810)	$0.10–$0.50 per document
Trading partner setup (per retailer)	$500–$2,000 one-time
Typical annual total	$5,000–$15,000

NetSuite Implementation

Component	Cost
SuiteApp configuration	$5,000–$10,000
Trading partner mapping (per retailer)	$2,000–$5,000
SSCC-18 label setup	$1,000–$3,000
Testing and go-live	$2,000–$5,000
Total implementation	$10,000–$23,000

Total First Year

For a brand setting up EDI with 2–3 retail partners:

• SPS Commerce annual: $8K–$12K
• Implementation: $15K–$25K
• Year 1 Total: $23K–$37K
• Year 2+ Annual: $5K–$15K

The ROI is clear: if EDI compliance prevents $15K–$25K in chargebacks and enables $500K+ in wholesale revenue, the investment pays for itself immediately.

Frequently Asked Questions

Do I need EDI for every retailer?

Not necessarily. Smaller retailers and specialty boutiques may accept orders via email, phone, or a B2B portal. EDI is typically required by national chains with more than 50 stores. Ask each retailer during onboarding whether EDI is required or optional.

Can I use SPS Commerce if the retailer wants to use a different EDI provider?

Yes. SPS Commerce connects to a VAN (Value Added Network) that can communicate with any other VAN or direct EDI connection. It doesn't matter which EDI provider the retailer uses — SPS handles the translation and transmission.

How do I handle EDI for drop-ship orders?

Some retailers send drop-ship 850s where you ship directly to the end customer, not to the retailer's warehouse. These orders may have different ship methods, labeling requirements, and packing slip formats. Configure your NetSuite setup to distinguish drop-ship POs from warehouse POs and apply the appropriate fulfillment rules.

What if a retailer changes their EDI requirements?

It happens regularly. Retailers update their routing guides, add required fields, change label formats, or modify compliance rules. SPS Commerce typically notifies you of changes and updates the trading partner maps. Budget for 4–8 hours of configuration work per retailer per year for specification updates.

Can I do EDI without SPS Commerce?

Yes. Other EDI providers include TrueCommerce, DiCentral (now part of DigiCert), and Cleo. You can also build a direct connection using AS2 protocol, though this requires more technical expertise. SPS Commerce is popular because of their extensive retailer network and NetSuite SuiteApp, but it's not the only option.

What Should You Do Next?

EDI is the price of admission to retail wholesale, and for ecommerce brands expanding beyond DTC, it's a critical capability. The setup is complex, but once it's running, it automates the entire order-to-invoice cycle and positions your brand as a professional, compliant vendor that retailers want to work with.

Start by identifying which retailers you're targeting, requesting their EDI requirements, and evaluating whether SPS Commerce or another EDI provider fits your needs and budget.

Take our free integration assessment to get a customized EDI + NetSuite implementation plan, including retailer-specific requirements analysis, SPS Commerce configuration guidance, and compliance checklist for your target retail partners.