TL;DR: EDI in shipping and logistics is the standardized, computer-to-computer exchange of business documents (purchase orders, advance ship notices, invoices, warehouse instructions, and freight messages) between trading partners. Retailers mandate it, and getting it wrong triggers chargebacks that can cost 3% or more per order. This guide covers the three document families you’ll encounter, how ASNs and GS1-128 labels must match, the real costs and timelines practitioners report, and what to watch for when choosing a transport method or EDI provider.
EDI in Shipping and Logistics
Electronic Data Interchange (EDI) in shipping and logistics is the standardized, computer-to-computer exchange of business documents, like purchase orders, advance ship notices, invoices, and warehouse or transportation messages, using structured formats such as ANSI X12 in North America. No phone calls, no PDF attachments, no manual re-keying. Just machine-readable data flowing between systems.
If you’re an operations manager at an ecommerce brand or a 3PL warehouse, EDI isn’t optional. It’s the language your retail partners speak, and they’ll fine you for speaking it poorly.
Why EDI Still Matters (and Isn’t Going Anywhere)
There’s a persistent myth that APIs and modern integrations have replaced EDI. The data says otherwise. Forrester projects that EDI’s share of US B2B electronic transactions will actually edge up to 21% by 2027, not down. In the EU, nearly half of manufacturing firms with electronic sales still receive orders through EDI-type channels.
The reason is simple: big retailers built their supply chains on EDI decades ago, and those systems work. Walmart, Target, Costco, Home Depot, and hundreds of other retailers require EDI compliance from every supplier. When they say “send us an 856 ASN before the truck arrives,” they don’t mean email a spreadsheet.
The stakes are financial. Walmart’s OTIF (On Time, In Full) program is widely cited at 3% of item value for missed delivery windows or incomplete shipments, and ASN errors can trigger separate penalties on top of that. Other retailers run similar programs with their own fee structures. These chargebacks add up fast, especially for brands scaling into wholesale for the first time.
For brands navigating B2B and wholesale fulfillment, understanding EDI is the difference between a profitable retail channel and a margin-destroying one.
The Three EDI Document Families You’ll Touch
EDI in shipping and logistics breaks into three tracks. You might use one, two, or all three depending on whether you sell to retailers, use a 3PL, or manage freight directly.
Retail and B2B Commerce (Supplier to Retailer)
These are the documents that flow between a brand (supplier) and a retailer (buyer):
- 850, Purchase Order: The retailer tells you what they want, how many, and when to deliver. This kicks off the entire flow.
- 855, PO Acknowledgment: You confirm you can fill the order (or flag changes). Many retailers like Walmart publish specific 855 specs that suppliers must follow exactly.
- 856, Advance Ship Notice (ASN): You tell the retailer what’s shipping, how it’s packed, and the tracking details, before the truck arrives. This is the single most chargeback-prone document. More on that below.
- 810, Invoice: Your bill to the retailer, aligned to the PO and ASN.
- 846, Inventory Advice: Stock availability synced to prevent overselling across channels.
Less common but still relevant: the 860 (PO Change) and 832 (Catalog) appear when retailers need lifecycle updates on existing orders or product data.
Real-world example: A national retailer sends an 850 to your Shopify-connected ERP. Your system generates a pick list, your warehouse ships, and your 856 goes back with carton-level detail and SSCC codes. The retailer’s receiving dock scans the labels, matches them to the ASN, and either processes the shipment cleanly or flags exceptions.
Warehouse and 3PL Documents (Brand to Warehouse)
When a 3PL handles your fulfillment, a second set of documents manages the brand-to-warehouse relationship:
- 940, Warehouse Shipping Order: The brand (depositor) instructs the 3PL to pick, pack, and ship specific items.
- 945, Warehouse Shipping Advice: The 3PL confirms what actually shipped, including carrier info, tracking numbers, and quantities.
- 943/944: Used for stock transfers and receiving confirmations; less common but relevant for multi-warehouse networks.
A critical distinction: 940/945 documents flow between you and your warehouse. 850/856 documents flow between you and your retail buyer. In a 3PL scenario, you often need both sets running in parallel.
Transportation Documents (Shipper to Carrier)
Freight movements have their own EDI track:
- 204, Motor Carrier Load Tender: A shipper or broker offers a load to a carrier with pickup/delivery details.
- 990, Response to Load Tender: The carrier accepts or declines.
- 214, Shipment Status: In-transit checkpoints, delivery confirmation, and proof-of-delivery updates.
- 210, Motor Carrier Freight Invoice: The carrier’s bill for hauling the load.
Real-world example: Your freight broker sends a 204 to a carrier. The carrier responds with a 990 acceptance, then sends 214 status updates at pickup, each terminal, and final delivery. After the load delivers, the 210 freight invoice follows.
ASN, Labels, and SSCC: Why Receiving Loves or Hates Your Data
The 856 ASN is where most EDI pain concentrates. It’s not just a “heads up, something is shipping” message. It’s a structured hierarchy describing exactly how goods are packed:
- Shipment level (the whole delivery)
- Order level (which PO lines are included)
- Tare level (pallets)
- Pack level (cartons)
- Item level (individual SKUs and quantities)
Each carton and pallet gets a Serial Shipping Container Code (SSCC), a unique 18-digit identifier. The SSCC is encoded into a GS1-128 barcode (formerly called UCC-128) printed on the physical label stuck to each carton.
Here’s where things break: the ASN references those SSCCs electronically, and the physical labels carry them as scannable barcodes. If they don’t match, the retailer’s receiving system flags exceptions. That means chargebacks, short-pays, or refused deliveries.
GS1-128 is the only barcode symbology approved to encode SSCCs in logistics. Getting the label format wrong, printing at the wrong time in the workflow, or generating SSCCs out of sequence with the ASN are all common failure modes.
For brands shipping healthcare or regulated products, the ASN hierarchy also needs to carry lot numbers, expiration dates, and potentially FEFO (First Expired, First Out) data. If you’re in that space, healthcare-specific fulfillment workflows add another layer of compliance.
How EDI Messages Actually Move: AS2, VANs, and the 997 Receipt
EDI defines what’s in the message. The transport protocol defines how the message gets from point A to point B. These are different things, and confusing them is common.
AS2
AS2 (Applicability Statement 2) is a secure protocol that sends EDI documents over HTTPS with encryption and digital signing. Many large retailers require AS2. Drummond Group certification ensures interoperability between different AS2 software products. AS2 is point-to-point, you connect directly to your trading partner.
Value Added Networks (VANs)
VANs act as middlemen. You send your EDI documents to the VAN, and the VAN routes them to the right partner. VANs handle format translation, message tracking, and sometimes validation. The trade-off is cost: VAN pricing typically involves per-kilocharacter fees plus monthly minimums. Practitioners on Reddit report seeing everything from sub-$0.01/KC to $110+ monthly base plans, with extra charges for mailbox fees, testing, and “interconnect” fees when your partner uses a different VAN.
SFTP
Some smaller partners accept EDI files via SFTP. It works, but it lacks the built-in acknowledgment and routing features of AS2 or VAN.
The 997 Functional Acknowledgment
Every critical EDI exchange should produce a 997 Functional Acknowledgment. This is a receipt confirming your partner received and syntactically validated your document. It does not mean they accepted the order or agree with the contents. It just means the file arrived and parsed correctly. Track your 997s. A missing 997 is an early warning that something failed silently.
EDI vs API in Logistics: Use Both
The “EDI vs API” debate misses the point. In logistics, you’ll almost certainly use both.
Keep EDI for: High-volume, standardized documents that must conform to strict trading-partner rules. Purchase orders, ASNs, invoices, warehouse instructions (940/945), and freight documents (204/214/210) all fit here. Retailers won’t rewrite their receiving systems to accept your custom API payload.
Use APIs for: Real-time visibility, self-service status lookups, webhook alerts for exceptions, and fast integrations with modern platforms. Tracking updates, inventory sync to Shopify or Amazon, and exception notifications all work better through APIs.
As OpenText’s analysis puts it, most modern logistics organizations run a hybrid strategy. EDI handles the structured, compliance-driven documents. APIs handle the real-time, event-driven data.
If you’re evaluating how a 3PL connects to your systems, look at both their EDI capabilities and their direct integrations with platforms like Shopify, Amazon, and Walmart.
The Full Flow: How EDI Works Through a 3PL
Here’s the complete document flow when a retailer orders from a brand that uses a 3PL:
- Retailer sends 850 (Purchase Order) to the brand.
- Brand sends 855 (PO Acknowledgment) back to the retailer.
- Brand sends 940 (Warehouse Shipping Order) to the 3PL.
- 3PL picks, packs, and applies GS1-128 labels with SSCCs to each carton.
- 3PL sends 945 (Warehouse Shipping Advice) back to the brand, confirming what shipped.
- Brand generates 856 (ASN) using 945 data and sends it to the retailer.
- Brand sends 810 (Invoice) to the retailer.
- 997 acknowledgments are exchanged at each step.
The critical handoff is step 5 to step 6. The 3PL’s 945 must feed the brand’s 856 with matching carton IDs and SSCCs. If the 945 reports different carton contents than what the 856 tells the retailer, the retailer’s receiving dock will flag mismatches.
Practitioners on Reddit specifically call out this 945-to-856 mapping gap as a frequent source of chargebacks. The fix is validation logic that confirms the 3PL’s outbound data matches the ASN data one-to-one before transmission.
Chargebacks You Can Prevent with Correct EDI
Retailers don’t fine suppliers for fun. They fine them because bad data creates real costs at receiving docks and distribution centers. Here are three failure patterns and the EDI fixes:
1. MABD Miss (Must Arrive By Date)
The shipment arrives late, or the appointment wasn’t scheduled properly. The EDI fix: use 214 appointment status updates to confirm carrier pickup and delivery timing, and align your ASN transmission time with actual carrier pickup. If the ASN says “shipped Tuesday” but the carrier didn’t pick up until Thursday, you’re setting yourself up for an OTIF miss.
Walmart’s OTIF program penalizes late deliveries at roughly 3% of item cost. Other retailers run similar programs. Always check your retailer’s current routing guide, because penalty rates and dispute windows change.
2. ASN/Label Mismatch
The 856 says the carton contains 24 units of SKU A. The label on the physical carton encodes a different SSCC. The retailer scans the label, looks up the SSCC in the ASN, and gets a mismatch. The fix: generate SSCCs in your WMS at the moment of packing (not before), print the GS1-128 label immediately, and validate the 856 pack loop against the actual label data before transmitting.
3. 945/856 Misalignment
Your 3PL’s 945 reports 10 cartons shipped. Your 856 to the retailer references 12 cartons because someone manually adjusted a quantity. The retailer receives 10 cartons, expects 12, and deducts accordingly. The fix: automate the 856 generation directly from 945 data with no manual override, or build validation rules that block transmission when counts don’t match.
Quick Chargeback Check
- Getting fined for late delivery? Confirm your 214 status codes reflect actual carrier events, not estimated ones.
- Getting fined for receiving errors? Verify your SSCC generation timing in the WMS matches your 856 pack hierarchy.
- Getting fined for quantity discrepancies? Audit whether 945 contents feed 856 carton IDs one-to-one.
Always confirm penalty details against your specific retailer’s current compliance guide, as programs and rates update regularly.
Real-World Timelines, Costs, and Pitfalls
The vendor pitch for EDI sounds clean: connect, map, test, go live. Reality is messier.
Timelines
Practitioners on Reddit consistently report that getting a single trading partner live takes 2 to 3 months. 3PL setups take two to three times longer than straightforward buyer-seller flows because of the extra 940/945 mapping layer and the coordination between three parties (brand, 3PL, retailer). Budget calendar time for mapping, testing, user acceptance testing, and certification with the retailer.
Costs
VAN pricing is notoriously opaque. Common structures include per-kilocharacter fees with monthly minimums, but practitioners warn to watch for hidden charges: mailbox fees, test environment fees, and “interconnect” fees when your trading partner uses a different VAN. Get itemized quotes from multiple providers and compare total cost at your actual transaction volume.
Mapping Pitfalls
The most common mapping issues reported by practitioners:
- 945s missing PO references or placing data in the wrong loop, causing the brand’s system to fail when generating the 856.
- 856 hierarchy errors, particularly wrong nesting of pack and tare levels.
- 214 status codes that deviate from standard X12, especially when working with large marketplaces that use custom code sets.
One recurring theme from practitioner discussions: the real complexity isn’t the EDI technology itself. It’s the orchestration, keeping context in one place across your EDI provider, 3PL WMS, retailer portal, and carrier TMS. Teams repeatedly identify project management discipline as the biggest success factor in EDI implementations.
Implementation Checklist
Before you start an EDI project, work through this list:
- Map required documents by channel. DTC orders typically need no EDI. B2B retail needs 850/855/856/810/846. 3PL flows add 940/945. Freight adds 204/214/210.
- Pull every retailer’s routing guide. Each one specifies ASN hierarchy rules, label formats, SSCC requirements, and transmission deadlines.
- Choose your transport method. AS2 for direct connections to major retailers. VAN if you have many trading partners. SFTP only if the partner accepts it.
- Model your costs. Get VAN quotes at your projected volume. Factor in monthly minimums, per-KC fees, interconnect charges, and test environment costs.
- Instrument compliance metrics. Track OTIF rates, ASN timeliness and accuracy, label scan pass rates, 997 response times, and chargebacks by type.
- Build exception playbooks. Define what happens when an 855 is late, an ASN gets rejected, or a 214 code doesn’t match expectations. Align with each retailer’s dispute windows.
Understanding how onboarding works with your 3PL is just as important as the EDI setup itself, because both need to happen in parallel.
Where 4fillment Fits in Your EDI Picture
For brands that need a 3PL capable of handling B2B retail compliance, 4fillment supports the routing guide and EDI complexity that wholesale channels demand. That includes barcode-based receiving, ASN generation, and GS1-128 label compliance. Direct integrations with Shopify, Amazon, Walmart, eBay, and Etsy, plus API and ERP connectivity, mean order data flows automatically without manual re-keying.
Slack alerts and real-time WMS visibility help operations teams catch exceptions before they become chargebacks. With a multi-node network across California, Texas, Georgia, and New Jersey, 4fillment offers 1 to 2 day ground coverage nationwide, which matters when retailers impose tight Must Arrive By Date windows. Onboarding takes 7 to 10 days, fast enough to get EDI testing underway quickly.
For brands also running programs with strict ship-time requirements, like Seller Fulfilled Prime, the same-day handling and 99%+ on-time ship rate targets align with the EDI-driven discipline that retail compliance demands.
FAQ
What does EDI mean in shipping and logistics?
EDI (Electronic Data Interchange) in shipping and logistics is the automated, computer-to-computer exchange of standardized business documents between trading partners. In North America, it uses the ANSI X12 format for documents like purchase orders (850), advance ship notices (856), invoices (810), warehouse instructions (940/945), and freight messages (204/214/210).
What is the difference between an ASN and a shipping label?
The ASN (EDI 856) is an electronic document describing what’s being shipped, how it’s packed, and the tracking details. The GS1-128 shipping label is a physical barcode on the carton that encodes the SSCC (Serial Shipping Container Code). The ASN references the SSCCs on the labels. If they don’t match, the retailer’s receiving system flags errors.
How long does it take to set up EDI with a retail partner?
Practitioners consistently report 2 to 3 months per trading partner for mapping, testing, and certification. 3PL setups tend to take two to three times longer because of the additional 940/945 layer and three-party coordination between brand, warehouse, and retailer.
What is the difference between 940/945 and 850/856?
The 940 and 945 are warehouse documents. The 940 instructs a 3PL to ship, and the 945 confirms what actually shipped. The 850 and 856 are commerce documents. The 850 is a retailer’s purchase order, and the 856 is the supplier’s advance ship notice. In a 3PL scenario, you typically need both pairs running in parallel.
How much does EDI cost?
Costs vary widely. VAN pricing commonly uses per-kilocharacter fees with monthly minimums. Practitioners report base plans ranging from under $0.01 per kilocharacter to $110+ per month, with additional charges for mailboxes, testing, and interconnects. AS2 connections reduce per-message costs but require upfront setup and certificate management.
What is a 997 Functional Acknowledgment?
The 997 is an automated receipt confirming that your trading partner received your EDI document and that it passed basic syntax validation. It does not mean the partner accepted the business content (like agreeing to fill an order). Track 997s for every critical document, a missing one signals a silent failure.
Can EDI and APIs work together in logistics?
Yes, and most modern logistics operations use both. EDI handles high-volume, standardized documents required by trading partners (POs, ASNs, invoices, 940/945, freight docs). APIs handle real-time visibility, webhook alerts, platform integrations, and exception notifications. It’s a hybrid strategy, not an either-or choice.
How do EDI errors cause chargebacks?
Retailers penalize suppliers for data that creates problems at their receiving docks. Common causes include ASN/label SSCC mismatches (the electronic record doesn’t match the physical barcode), late ASN transmission (the ASN arrives after the truck), and quantity discrepancies between the 3PL’s 945 and the supplier’s 856. Walmart’s OTIF program, for example, assesses roughly 3% of item cost for late or incomplete shipments.