What is EDI in apparel? A practical guide for fashion brands.

What EDI actually is

EDI stands for electronic data interchange. It’s the standardised electronic exchange of business documents - purchase orders, shipping notices, invoices, inventory updates - between trading partners in a format both sides can process automatically without anyone re-keying data.

The core idea is 50 years old. Before EDI, a large retailer wanting to buy 10,000 items from 500 vendors would have someone type each purchase order, mail or fax it, receive a paper acknowledgment, wait for a paper shipping notice, count what arrived, and match it against a paper invoice. At scale this was impossible. EDI standardised the format of each document so retailers and vendors could exchange them directly between computer systems - no paper, no re-keying, no manual matching.

What makes EDI feel modern is its stubbornness. The document formats are older than most people in the industry; the technology behind them (X12 in the US, EDIFACT internationally) predates the web. But the standards work. A purchase order from Walmart to a hosiery brand in North Carolina uses essentially the same X12 850 format it did in 1995. Retailers have iterated on operational rules around EDI, not on EDI itself.

For an apparel brand, EDI is not optional at wholesale scale. It’s the ticket to selling into department stores, mass retailers and most large chain stores. Without EDI, those channels are effectively closed.

Why retailers require EDI

Major retailers process millions of orders across thousands of vendors. Manual order handling at that scale is impossible, so retailers standardised on EDI decades ago and made it a condition of doing business.

The specific problem EDI solves for a retailer:

• Order placement. Buyers issue POs weekly. Each one has to reach the right vendor in a format that vendor’s system can process automatically. Fax and email don’t scale.
• Inbound planning. The retailer’s warehouse needs to know what’s arriving, when, in what cartons, with what labelling - before it arrives. EDI provides this via the advance ship notice (ASN, or 856).
• Reconciliation. Every invoice has to match a PO, a receipt, and pricing rules. Manual reconciliation on millions of invoices is impossible. EDI enables three-way match automation.
• Vendor compliance. If a retailer’s systems can enforce format rules on incoming data, non-compliant vendors reveal themselves immediately. This is why chargebacks exist.

The consequence for apparel brands: EDI compliance is not a technical convenience. It’s a commercial requirement, enforced through chargebacks. A brand that runs EDI cleanly gets paid in full; a brand that runs EDI poorly gets paid net of deductions that can wipe out the margin on the order.

The EDI documents that matter for apparel

The X12 standard defines hundreds of document types. In apparel, eight of them do the real work.

Practical rule: 850, 856 and 810 are effectively universal - if you sell wholesale to any major retailer, you handle these three. 855, 846 and 820 are common. 852 and 860 are worth having when the retailer supports them but not always required.

Chargebacks and how they compound

A chargeback is a deduction a retailer applies to a vendor’s invoice for non-compliance with the retailer’s operational requirements. In apparel wholesale, chargebacks are the mechanism through which EDI failures become financial losses.

The common trigger categories:

• Late or missing ASN. Goods arrive at the retailer’s warehouse without an ASN, or with an ASN sent after the goods. Common range: $250-500 per shipment plus a percentage of the invoice.
• Incorrect case labelling. UCC-128 labels don’t match the ASN or don’t scan properly. $50-100 per case plus rework charges.
• Quantity discrepancy. ASN says 500 units, receipt counts 480. Retailer deducts the difference plus a handling fee.
• Delivery window violation. Goods arrive outside the specified window - early or late. Percentage of invoice, sometimes 5-10%.
• Incorrect routing. Ship to wrong DC, use wrong carrier. Freight cost differential plus a penalty.

Individually, chargebacks look manageable. In aggregate, they compound quickly. A small brand doing $500k with a major retailer, running EDI poorly, can easily see 3-5% of gross invoiced revenue disappear to chargebacks - which for many apparel brands is the entire net margin on that account.

The financial trap: chargebacks show up in the payment remittance (820), not on the invoice, so a brand’s accounting system sees full invoiced revenue and reduced cash. Reconciling the two - and understanding which chargebacks are avoidable vs. structural - is a real operational discipline that many brands don’t build until after a bad quarter.

Middleware EDI vs. native ERP EDI

Historically, apparel brands used a separate EDI service provider - SPS Commerce, TrueCommerce, DiCentral, EDI Gateway - that sat between the brand and its retailers. The service provider translated the retailer’s EDI format into something the brand could handle, and translated the brand’s responses back. This model still dominates the market and works fine, but has costs.

Third-party EDI middleware

Pros: Vendor-agnostic - works with any ERP or accounting system. Retailer maps already exist for most common trading partners, so onboarding is faster. The service provider is a specialist in EDI and stays current with retailer spec changes.

Cons: Per-document fees add up - $0.10-1.00 per document, plus base monthly cost. At scale this becomes tens of thousands per year. Data flows through an external system before reaching your ERP, so orders can be delayed, ASN timing depends on middleware sync, and every troubleshooting issue involves a third party. Adds a second contract and a second point of failure.

Native ERP EDI

Pros: No middleware, no per-document fees. Orders arrive directly in the ERP, are picked and shipped in the ERP, and ASNs and invoices flow out of the ERP - single system, no external sync. Usually cheaper at scale, faster in production, easier to troubleshoot. Data structure inside the ERP is the same as EDI expects, so mapping is simpler.

Cons: ERP vendor has to maintain the retailer maps and stay current with retailer spec changes. Not every ERP does this well; some apparel ERPs claim native EDI but effectively re-sell an underlying middleware. Worth checking whether the retailer maps are maintained by the ERP vendor or a partner.

Which is right

For brands under $5M in wholesale revenue, or with fewer than five EDI retailers, either model works and cost differences are marginal. For brands over $10M in wholesale, or with 10+ EDI retailers, native ERP EDI usually wins on both cost and reliability - if the ERP genuinely supports it. For brands in between, the deciding factor is often the existing stack: replacing SPS Commerce mid-scale for a per-document savings is rarely worth it if EDI is running cleanly; migrating away from a middleware that’s a source of chargebacks is often the highest-ROI operational change a brand makes in a year.

What EDI actually costs

The visible costs, using rough public ranges as of 2026:

• Third-party EDI middleware: $200-1,000/month base subscription plus $0.10-1.00 per document per retailer. At mid-market wholesale scale (10-20 retailers, 3-8k documents/month) this typically runs $15-40k/year.
• Native ERP EDI: usually included in the ERP subscription without per-document fees, but each retailer map is a one-time implementation cost - typically $1-5k per retailer.
• Setup per retailer: $500-3k for middleware EDI (mostly certification testing time). $1-5k for native ERP EDI (both mapping and testing). Similar ballpark; the model choice matters more for ongoing than for setup.

The invisible costs, which usually dwarf the subscription:

• Chargebacks from EDI errors. Discussed above - 3-5% of invoiced revenue is a realistic range for brands with EDI hygiene problems.
• Internal EDI operations time. Someone monitors the transactions, catches problems, retransmits failed documents, coordinates with retailers on spec updates. Anywhere from a few hours a week to a full FTE, depending on retailer count and hygiene.
• Missed shipments from EDI-driven timing issues. When ASN generation is late, ship dates slip. When ship dates slip, chargebacks and future PO reductions follow.

A useful diagnostic: total the last 12 months of chargebacks by trigger category. If EDI-related triggers account for more than 1% of gross wholesale revenue, the EDI setup is costing more than any subscription decision could save. Fix EDI hygiene first; optimise cost second.

Which retailers require EDI

Practically all major wholesale accounts in apparel require EDI. A working list, not exhaustive:

• US mass retail: Walmart, Target, Costco, Sam’s Club, BJ’s Wholesale
• US department stores: Macy’s, Nordstrom, Dillard’s, JCPenney, Kohl’s, Belk
• US off-price: TJ Maxx, Marshalls, HomeGoods, Ross, Burlington, Nordstrom Rack, Saks Off 5th
• US sporting goods: Dick’s Sporting Goods, Academy Sports, REI
• US e-commerce: Amazon (Vendor Central), Wayfair, Zappos
• US specialty: Dillard’s, Neiman Marcus, Bloomingdale’s, Saks Fifth Avenue
• Europe: Zalando, El Corte Inglés, John Lewis, Selfridges, House of Fraser, Harrods
• Australia: David Jones, Myer, The Iconic
• Canada: Hudson’s Bay, Winners, Sport Chek

What’s not usually EDI: boutiques, single-store independents, direct-to-consumer channels, most trade shows. The line is roughly around retailer size - if the retailer has more than ~50 stores or a real e-commerce warehouse operation, EDI is likely required. Below that, purchase orders arrive by email or via a wholesale portal.

Getting started with EDI

A brand that’s about to onboard its first major retailer usually finds out about EDI as part of the retailer’s vendor setup packet. The retailer specifies which documents are required, which format version, what the case labelling requirements are, and points at their EDI compliance guidelines. Reading that packet in full is worth an hour.

From there, the practical steps:

1. Decide the model. Middleware or native. If you have an apparel ERP with genuine native EDI, native is usually the right choice. If not, middleware is fine.
2. Implement the core three documents first. 850, 856, 810. Get these working cleanly before adding others.
3. Complete the retailer’s certification testing. Every retailer runs test transactions before going live. Skipping or rushing this stage causes the worst chargebacks.
4. Build the internal EDI ops discipline. Someone monitors daily. Failed documents get resent. Retailer spec updates get read and implemented. This is a real operational role, not an IT afterthought.
5. Track chargebacks by trigger. Monthly categorisation of chargebacks reveals which are avoidable (fix the process) and which are structural (renegotiate the trading terms). Both are worth doing; you can’t address either without the data.

The single most valuable habit for a growing wholesale apparel brand: chargeback trend reporting reviewed monthly by whoever owns wholesale profitability. The brand that watches this compulsively is the brand whose wholesale margin holds up.

Frequently asked questions