Key Takeaways
- EDI (Electronic Data Interchange) is how retailers send POs, receive shipment notifications, and process invoices electronically — it's required by every major national retailer.
- Setup costs $150–$500/month for small brands, with implementation fees of $500–$2,000.
- The four critical EDI documents are: 850 (Purchase Order), 856 (Advance Ship Notice), 810 (Invoice), and 997 (Acknowledgment).
- Setup takes 4–8 weeks including trading partner configuration and testing — start before the PO, not after.
- The #1 EDI mistake is manual ASN creation instead of automated transmission, which leads to late-ASN chargebacks of $200–$500 per incident.
EDI setup for a small brand typically costs $150–$500/month, takes 4–8 weeks, and involves connecting your business to a standardized electronic document system that retailers require for purchase orders, shipment notifications, and invoices.
We've set up EDI for dozens of brands at Logic Agency, and the pattern is always the same: founders assume it's a massive technical project, delay it until the last minute, and then scramble to get it done in two weeks when the retailer asks for it. This guide gives you the full picture so you can plan it properly.
What EDI Actually Is (and Why Retailers Require It)
EDI stands for Electronic Data Interchange. In plain terms, it's a standardized system for sending business documents — purchase orders, shipping notices, invoices — electronically between trading partners. Instead of emailing a PDF purchase order, the retailer's system sends a structured electronic document that your system can read, process, and respond to automatically.
Retailers require EDI for one reason: scale. A retailer managing 5,000+ vendors can't process purchase orders by email. They can't manually track shipment notifications. They can't reconcile invoices from 5,000 different formats. EDI standardizes these transactions so the retailer's system can process them without human intervention.
For you as a small brand, EDI means:
- You receive purchase orders electronically (not via email or portal)
- You transmit shipment notifications electronically when orders ship
- You submit invoices electronically for payment processing
- Each document follows a standard format that both systems understand
The standard used by most U.S. retailers is ANSI X12. You don't need to understand the technical specification. Your EDI provider handles the translation. You need to understand which documents are required and what they do.
The 4 EDI Documents Every Small Brand Needs
EDI 850: Purchase Order
The 850 is the retailer's purchase order — the electronic equivalent of “we want to buy this from you.” It contains the SKUs, quantities, prices, ship dates, and delivery instructions. When a retailer places an order, it arrives as an 850.
Your system (or your EDI provider's portal) receives the 850 and presents it in a readable format. You review it, confirm you can fulfill it, and acknowledge receipt.
EDI 855: Purchase Order Acknowledgment
The 855 confirms that you received the PO and can fulfill it as specified. Not every retailer requires an 855, but many do — and sending one is good practice. It confirms the order details, flags any issues (backordered SKUs, quantity adjustments), and sets expectations.
EDI 856: Advance Ship Notice (ASN)
The 856 is the most important EDI document for compliance — and the one that causes the most chargebacks when it's late or wrong.
The ASN tells the retailer: “This shipment is on its way. Here's exactly what's in it — which SKUs, how many units, how many cartons, the carrier, the tracking number, and the expected delivery date.”
Most retailers require the 856 to be transmitted within 2 hours of carrier pickup. Some require 30 minutes. A late or missing ASN triggers an automatic chargeback — typically $200–$500 per occurrence. It's the single most common retail penalty for small brands.
The 856 must match the physical shipment exactly. If the ASN says 500 units and the shipment contains 480, that mismatch triggers a separate chargeback.
EDI 810: Invoice
The 810 is your electronic invoice — sent after shipment to trigger payment processing. The 810 must reference the original PO number and match the ASN. Discrepancies between the 810 and the 850/856 delay payment and can generate deductions.
EDI 997: Functional Acknowledgment
The 997 is a system-level receipt that confirms a document was received and processed. It's automated — your EDI system sends and receives 997s without your involvement. Think of it as a digital read receipt.
EDI Setup Options for Small Brands
You don't need to build EDI infrastructure from scratch. Three options cover 95% of small brand needs:
Option 1: Full EDI Provider (Most Common)
A third-party EDI service that manages your connections with retail trading partners. They translate documents between your systems and the retailer's, handle compliance requirements, and provide a web portal for managing transactions.
Top providers for small brands:
- SPS Commerce — the largest retail EDI network. Strong onboarding support, extensive retailer pre-connections.
- TrueCommerce — good mid-market option with ERP integrations.
- Covalent (formerly 1 EDI Source) — smaller provider with competitive pricing for low-volume brands.
Typical cost: $150–$400/month plus $500–$2,000 implementation fee. Monthly cost depends on transaction volume and number of trading partners.
Best for: Brands managing their own fulfillment or using a 3PL that doesn't offer EDI.
Option 2: Web-EDI (Portal-Based)
A browser-based portal where you manually key in EDI documents. The retailer sends a PO, you log into the portal, review it, and manually create the ASN and invoice.
Typical cost: $0–$100/month (some retailers offer free web-EDI portals).
Best for: Very low volume (1–3 POs per month) where the manual data entry time is manageable.
Caution: Manual ASN creation is risky. One missed session, one data entry error, and you're eating a chargeback. We see brands start on web-EDI and switch to a full provider within 6 months because the manual process doesn't scale and the error rate is too high.
Option 3: 3PL-Provided EDI (Simplest Path)
Your third-party logistics provider includes EDI as part of their fulfillment service. The 3PL receives the PO, manages inventory, ships the order, and transmits the ASN — all within their system.
Typical cost: Included in 3PL fulfillment fees (or $100–$300/month add-on).
Best for: Brands using a retail-experienced 3PL. This is the fastest path to EDI compliance because the 3PL already has trading partner connections with major retailers.
Caution: Verify your 3PL actually has EDI capability and existing connections with your specific retailer. “We can do EDI” and “We have an active trading partner connection with Target” are different statements. Ask for proof.
EDI Setup Timeline: What 4–8 Weeks Actually Looks Like
Weeks 1–2: Provider Selection and Account Setup
- Select your EDI provider or confirm 3PL EDI capability
- Create your account and provide business information
- Identify the specific retailer(s) you need to connect with
- Begin trading partner setup (your provider initiates the connection with the retailer's EDI system)
Weeks 2–4: Trading Partner Configuration
- Your EDI provider configures the document maps for your specific retailer
- Each retailer has slightly different data requirements within the standard EDI format
- Your provider maps these requirements to your system
- If integrating with an ERP or OMS, that integration work happens here
Weeks 4–6: Testing
- Transmit test transactions (test 850, 856, 810) with the retailer's system
- Verify document accuracy — do the fields populate correctly? Does the ASN format match requirements?
- Fix mapping errors identified during testing
- The retailer's EDI team validates your test documents
Weeks 6–8: Go-Live and First Real Transaction
- Switch from test mode to production
- Process your first real PO through the EDI system
- Monitor the first 2–3 transactions closely for errors
- Confirm ASN timing meets the retailer's compliance window
Don't compress this timeline below 4 weeks. Rushed EDI setups generate errors in the first month that cost more in chargebacks than the time saved.
What EDI Setup Actually Costs for Small Brands
Here's a realistic cost breakdown for a small brand setting up EDI for one retail trading partner:
| Cost Category | Low Estimate | High Estimate |
|---|---|---|
| Implementation / setup fee | $500 | $2,000 |
| Monthly subscription | $150/month | $500/month |
| Per-transaction fees (if applicable) | $0.10–$0.50/transaction | $1–$3/transaction |
| Integration with OMS/ERP (if needed) | $1,000 | $5,000 |
| Year 1 total cost | $2,800 | $12,000 |
Compare that to the cost of not having EDI: $200–$500 per late ASN chargeback, $100–$300 per documentation error, and the relationship cost of being flagged as a non-compliant vendor. Two months of ASN-related chargebacks typically exceed the full first-year cost of EDI setup.
The 5 Most Common EDI Setup Mistakes
Mistake 1: Starting After the PO Is Signed
The retailer says yes. The PO is coming. You start your EDI setup on Day 1 post-PO. But the PO ships in 6 weeks and EDI takes 4–8 weeks to configure. You're behind before you start.
Start EDI setup when you begin pursuing the retail account — not when the deal closes. If the account doesn't materialize, you've lost $500 in implementation fees. If it does and your EDI isn't ready, you've lost $5,000+ in first-shipment chargebacks.
Mistake 2: Manual ASN Creation
Web-EDI portals are fine for receiving POs. They're dangerous for ASN creation. The 856 must be transmitted within hours of shipment — sometimes within 30 minutes. A manual process requires someone available, accurate, and timely every single shipment. People get sick. People make typos. People forget.
Automated ASN generation — where the 856 is triggered by the shipping event in your WMS or 3PL system — eliminates the most common and most expensive EDI-related chargeback.
Mistake 3: Not Testing With the Specific Retailer
Your EDI provider may have a generic connection template for “major retailers.” But Target's 856 requirements aren't identical to Walmart's. A test transaction that passes validation on a generic template can fail at the retailer's DC because a specific field is formatted differently.
Test with the actual retailer. Send test transactions through their system. Get confirmation from their EDI team that your documents pass.
Mistake 4: Ignoring the 810 Invoice
Most brands focus on the 850 and 856 — PO and ASN — and treat the 810 invoice as an afterthought. But invoice discrepancies cause payment delays and deductions. If your 810 references the wrong PO number, shows a different quantity than the ASN, or uses a different unit price than the PO, payment gets held until the discrepancy is resolved.
Mistake 5: No Backup Process
EDI systems go down. Servers fail. Your provider has an outage. If you have no backup process for transmitting an ASN during downtime, every shipment during the outage generates chargebacks.
Document a backup process — even if it's “log into the retailer's web portal and manually submit the ASN.” Know the process before you need it.
FAQ
Do all retailers require EDI?
No. Smaller regional retailers, independent stores, specialty chains, and some natural grocers accept manual purchase orders and invoices by email or through their own ordering portal. But every major national retailer — Target, Walmart, Whole Foods, Sephora, Ulta, CVS, Kroger, Costco — requires EDI. If your retail strategy includes national chains, EDI is a prerequisite.
How long does EDI setup take for a small brand?
Plan for 4–8 weeks from provider selection to first live transaction. The fastest setups happen when your EDI provider has an existing connection with the retailer and you don't need ERP integration. The longest setups involve new trading partner connections, complex integrations, or retailers with slow EDI onboarding teams.
What is the cheapest way to set up EDI?
If your 3PL offers EDI as part of their fulfillment service, that's typically the lowest-cost path — often included in your fulfillment fees or available as a $100–$300/month add-on. If you need a standalone EDI provider, expect $150–$400/month plus a one-time setup fee. Web-EDI portals are the cheapest option ($0–$100/month) but carry higher chargeback risk due to manual data entry.
Can I use the same EDI setup for multiple retailers?
Your EDI provider account supports multiple trading partners, but each retailer requires separate configuration. The document formats vary — Target's ASN requirements differ from Walmart's. Your provider handles the mapping, but expect 2–4 weeks of additional setup time per new retailer. The monthly cost typically increases $50–$150 per additional trading partner.
What happens if my EDI system goes down?
You need a documented backup process. Most retailers have web-EDI portals that you can use as an emergency fallback for ASN and invoice submission. Know the portal login, know the process, and test it before you need it. An EDI outage without a backup process means every shipment during the downtime generates chargebacks.
Is EDI the same as an ERP?
No. EDI is a communication standard — it governs how documents are exchanged between trading partners. An ERP system manages your internal business operations: inventory, orders, accounting, production. EDI connects your systems to the retailer's systems. An ERP manages what happens inside your business. Many small brands run EDI without an ERP, using their EDI provider's portal or their 3PL's system to manage transactions.