Introduction
Electronic Data Interchange (EDI) is the backbone of modern commerce. Help automate warehouse operations.
Every time a pallet moves, a truck is dispatched, or an invoice is generated, there’s a structured conversation happening behind the scenes, one written in EDI.
In a world where supply chains span continents, warehouses handle thousands of SKUs, and customers expect same-day visibility, EDI is what allows disparate systems to speak a common language, instantly, accurately, and without human intervention.
EDI isn’t a single, monolithic protocol. It’s a collection of standardized transaction sets, each purpose-built for a specific business event.
For warehouse operations specifically, eight transaction codes form the critical infrastructure that keeps inventory moving, carriers on schedule, and billing accurate.
Key Takeaways
EDI is the operational backbone of modern warehouse and logistics workflows because it enables systems like WMS, TMS, ERP, and partner platforms to exchange structured data automatically.
The most effective warehouse EDI setup is a full transaction loop, especially the paired flows of 940/945 and 943/944, because they create visibility from shipment authorization through receipt confirmation.
Freight-related transactions such as 204, 990, 214, and 210 are just as important as warehouse transactions because they connect tendering, carrier acceptance, tracking, and billing into one process.
EDI reduces manual work, improves accuracy, and shortens cycle times, but those gains only happen when documents are integrated directly into core systems and not handled as standalone files.
Successful EDI implementation is an ongoing program, not a one-time project, and requires partner-specific mapping, monitoring, exception handling, and continuous optimization.
What Is EDI and Why Does It Matter for Warehouses?
EDI is the computer-to-computer exchange of business documents in a standard electronic format between trading partners.
Instead of emailing a PDF purchase order or faxing a shipping manifest, EDI enables systems, ERPs, WMS platforms, and TMS to exchange structured data automatically, in real time, with zero manual re-keying.
In the warehouse context, the implications are profound. A modern 3PL (third-party logistics) facility might handle shipments for dozens of retail clients simultaneously.
Without EDI, each incoming order, each outbound shipment confirmation, and each freight invoice would require manual processing.
With EDI, a single data handshake triggers a cascade of automated actions across every connected system in the supply chain.
The ANSI ASC X12 standard, the dominant EDI framework in North America, defines each transaction set by a three-digit code.
These codes are what we’ll be exploring in depth.
Each one represents a specific business event, with a rigidly defined data structure that ensures every trading partner interprets the document identically.
The Complete Supply Chain Flow: How All 8 EDI Documents Connect
Before diving into each transaction individually, it’s critical to understand how these eight codes operate as a unified ecosystem. The end-to-end data flow links retailer, warehouse, and carrier through a complete information loop.
FROM | TRANSACTION | TO | PURPOSE |
Retailer / Owner | EDI 940 → | 3PL Warehouse | Outbound ship authorization |
Retailer / Owner | EDI 943 → | 3PL Warehouse | Inbound stock transfer notification |
3PL Warehouse | EDI 944 → | Retailer / Owner | Receipt confirmation |
Retailer / Owner | EDI 204 → | Carrier / Broker | Load tender offer |
Carrier / Broker | EDI 990 → | Retailer / Owner | Accept / Reject / Counter |
3PL Warehouse | EDI 945 → | Retailer / Owner | Shipment confirmation |
Carrier | EDI 214 → | Shipper / Retailer | In-transit status updates |
Carrier | EDI 210 → | Shipper / Retailer | Freight invoice |
This flow represents the complete operational lifecycle, from the initial authorization to ship, through inventory transfers and carrier assignments, all the way to delivery confirmation and billing.
Every handshake in this chain is critical. The system only performs at its best when all eight codes are implemented correctly.
The 8 EDI Transaction Codes Used in Warehouse Operations Explained
1. EDI 940 - Warehouse Shipping Order
The EDI 940 is the starting point of the entire outbound warehouse process.
It is the electronic equivalent of a pick-and-ship authorization, sent by a retailer, brand, or inventory owner to instruct a third-party warehouse to prepare and dispatch a specific shipment.
Think of it as the “green light.” Without a received and processed EDI 940, a 3PL has no formal authorization to release inventory.
This transaction set replaces phone calls, faxes, and emailed spreadsheets, each of which introduced delays, transcription errors, and compliance risks.
The document carries the full set of instructions a warehouse needs to execute an outbound shipment: ship-to address, required ship date, item descriptions with quantities, lot numbers, special handling instructions, carrier preferences, and routing requirements.
Advanced implementations also include retail compliance requirements (e.g., Walmart or Target routing guide mandates).
Example:
A fashion retailer running a flash sale may trigger thousands of EDI 940s within hours as orders pour in.
Every 940 lands in the WMS automatically, spawning pick orders, generating packing slips, and queuing carrier labels, all without a single human touchpoint.
2. EDI 945 - Warehouse Shipping Advice
If the EDI 940 is the order to ship, the EDI 945 is the confirmation that it happened.
This transaction set is sent by the warehouse back to the inventory owner after a shipment has physically departed, providing a full audit trail of what was actually shipped versus what was requested.
In real-world warehouse operations, what ships is not always what was ordered.
A pallet may have fallen short by two units due to a picking discrepancy.
A product may have been damaged during staging. The EDI 945 captures these variances explicitly, communicating actual quantities, lot numbers, carrier SCAC codes, PRO numbers, and departure timestamps.
The 945 is the critical trigger for the retailer’s downstream processes.
Upon receipt, the ERP system updates open order status, generates an advance shipment notification (ASN) for the destination, reconciles inventory levels, and initiates accounts receivable.
Retailers that mandate EDI compliance often treat a missing or delayed 945 as a vendor compliance violation subject to chargebacks.
3. EDI 943 - Warehouse Stock Transfer Shipment Advice
While the 940 governs outbound shipments to end customers, the EDI 943 is designed for inter-warehouse or stock transfer movements.
When inventory is being moved from a manufacturer or Distribution Center to a 3PL fulfillment warehouse, the EDI 943 is the inbound advance notification that tells the receiving facility what is coming.
A warehouse that knows exactly what’s arriving, quantities, product IDs, pallet configurations, expected arrival windows, and lot/expiration data, can pre-allocate dock doors, stage receiving equipment, assign labor, pre-build putaway plans, and configure quality inspection workflows. Without an EDI 943, receiving becomes reactive and chaotic.
Common use cases include seasonal inventory replenishment from a manufacturer’s DC, cross-docking operations, multi-node distribution network transfers, and e-commerce returns processing. In cold-chain logistics, the EDI 943 is especially critical, enabling refrigerated dock preparation before temperature-sensitive goods arrive.
4. EDI 944 Warehouse Stock Transfer Receipt Advice
The EDI 944 is the natural partner of the EDI 943, the receipt confirmation that closes the loop on inbound stock transfers.
After the 3PL warehouse has physically received, counted, inspected, and put away the incoming inventory, it sends a 944 back to the inventory owner to confirm exactly what was received.
Just as the 945 captures outbound variances, the 944 captures inbound discrepancies: damaged goods, short shipments, quantity overages, expired product, wrong items, or items failing quality inspection.
This data is invaluable for supplier performance management, claims processing, and inventory accuracy.
From a financial perspective, the EDI 944 is often the trigger for accounts payable processes.
Once inventory ownership is confirmed as transferred, payment terms begin.
For brands and manufacturers, the 944 also updates perpetual inventory records, removing units from ‘in-transit’ and adding them to ‘on-hand’ at the receiving facility.
The 940/945 pair governs outbound movement. The 943/944 pair governs inbound stock transfers. Together, these four codes give warehouse operators complete, real-time visibility into every unit of product, wherever it is in the facility lifecycle.
5. EDI 204 - Motor Carrier Load Tender
Once the warehouse is ready to ship, someone has to move the freight.
The EDI 204 is how shippers and freight brokers formally offer a load to a motor carrier, replacing the phone call or load board posting with a structured, system-to-system tender that carriers can accept, reject, or conditionally respond to automatically.
The EDI 204 is a rich document that includes origin and destination stop details, pickup and delivery windows, commodity descriptions, weight and cube measurements, special handling requirements (hazmat, temperature control, team driving), accessorial service requirements, and applicable rates.
Leading carriers have built TMS systems that auto-evaluate incoming 204s against available driver and equipment pools.
A load tender can be evaluated and responded to in seconds, dramatically compressing the freight booking cycle.
For shippers managing hundreds of outbound loads per day, this automation is the difference between a manageable operation and logistical chaos.
6. EDI 990 - Response to Load Tender
The EDI 990 is the carrier’s reply to the EDI 204 load tender, a structured acceptance, rejection, or conditional response that completes the two-way freight contracting handshake. Three key response types exist within the 990 framework:
ACCEPT (A): The carrier confirms they will execute the load as tendered. This triggers the shipper’s TMS to finalize the booking, assign a PRO number, and begin tracking the shipment. It also updates the warehouse outbound schedule with a confirmed carrier pickup window.
REJECT (R): The carrier declines, typically due to no available capacity, driver availability, or equipment mismatch. An automated TMS can instantly re-tender to the next carrier in the routing guide hierarchy, maintaining continuity without dispatcher involvement.
CONDITIONAL (C): The carrier offers a counter-proposal, a different pickup window, rate, or equipment type. The 204/990 exchange is where freight management becomes data-driven. Carrier acceptance rates, response times, and conditional counter-rates feed carrier scorecards and routing guide optimization.
7. EDI 214 - Transportation Carrier Shipment Status Message
In the age of same-day delivery expectations, real-time shipment visibility isn’t a luxury; it’s a baseline requirement.
The EDI 214 is the mechanism by which motor carriers deliver structured, event-driven status updates throughout a shipment’s journey from pickup to final delivery.
Each EDI 214 transmission corresponds to a specific shipment milestone: driver arrived at shipper, freight picked up, in transit, freight arrived at terminal, out for delivery, delivered.
Each event includes a precise timestamp, geographic location, appointment adherence data, and exception codes when something goes wrong (appointment missed, refused delivery, weather delay, mechanical failure).
When retailers receive continuous 214 updates, they can dynamically manage receiving schedules, reallocate dock appointments, and proactively communicate delivery ETA changes to end customers.
For e-commerce businesses, 214 data feeds directly into customer-facing tracking portals and notification systems.
Aggregated across carriers and lanes, EDI 214 data enables on-time delivery benchmarking, carrier performance comparison, root cause analysis of delay patterns, and network design insights that can reshape freight routing strategies.
8. EDI 210 - Motor Carrier Freight Details and Invoice
The EDI 210 brings the entire freight transaction full circle by delivering the carrier’s electronic freight invoice. This replaces paper bills of lading, manual invoice submissions, and the freight audit process that historically consumed enormous amounts of time and generated significant billing disputes.
The document contains a complete breakdown of all charges: base freight charges calculated against the contracted rate or tariff, fuel surcharges, accessorial fees (liftgate, residential delivery, inside delivery, detention, layover), and applicable discounts or allowances. It references the original PRO number, BOL number, pickup date, delivery date, and commodity details.
When EDI 210 data feeds directly into an automated freight audit and payment (FAP) platform, invoices can be validated against the original rate confirmations, contract rates, and actual service delivery data captured in the EDI 214 stream. Discrepancies are flagged automatically, reducing the invoice exception rate from an industry average of 15-25% to near zero.
For 3PLs billing clients for carrier charges, the 210 also forms the data foundation for client freight invoices — enabling pass-through billing with full transparency and eliminating manual re-keying between carrier bills and client invoices.
EDI Transaction Code Summary Table
| Code | Transaction Name | Direction | Primary Function | Triggered By |
| EDI 940 | Warehouse Shipping Order | → TO WH | Authorizes 3PL to pick, pack & ship outbound order | Customer order confirmed in ERP |
| EDI 945 | Warehouse Shipping Advice | ← FROM WH | Confirms what was shipped & departure data | Physical shipment departure from warehouse |
| EDI 943 | Stock Transfer Shipment Advice | → TO WH | Advance notice of inbound inventory transfer | Outbound shipment from origin facility |
| EDI 944 | Stock Transfer Receipt Advice | ← FROM WH | Confirms inbound receipt quantities & discrepancies | Inventory putaway completed at warehouse |
| EDI 990 | Response to Load Tender | ← FROM CARRIER | Carrier accepts, rejects, or counters load tender | Receipt of EDI 204 from shipper |
| EDI 204 | Motor Carrier Load Tender | → TO CARRIER | Formally offers freight load to motor carrier | Outbound shipment ready to book carrier |
| EDI 210 | Motor Carrier Freight Invoice | ← FROM CARRIER | Electronic freight invoice for payment processing | Delivery completion confirmed by carrier |
| EDI 214 | Transportation Carrier Shipment Status | ← FROM CARRIER | Real-time milestone events & exception updates | Shipment lifecycle events (pickup → delivery) |
Why Implementing All These 8 EDI Transaction Codes Helps Automate Your Warehouse Operations
Order Cycle Speed EDI-enabled warehouses process outbound orders 60-70% faster, with automated 940 intake reducing processing time from hours to minutes. | Inventory Accuracy The 943/944 loop creates a perfect closed-book reconciliation for every stock transfer, achieving 99.9%+ inventory accuracy rates. |
Carrier Efficiency The 204/990 exchange compresses load booking from hours to seconds, enabling dynamic freight optimization at scale. | End-to-End Visibility EDI 214 status events create a continuous tracking feed that feeds customer portals, control towers, and exception management. |
Freight Cost Control Automated EDI 210 invoice auditing eliminates overbilling, reduces invoice disputes by up to 80%, unlocking millions in freight savings. | Trading Partner Compliance Full EDI compliance protects against retailer chargebacks, maintains preferred vendor status, and opens doors to new relationships. |
Data-Driven Decisions Aggregate data across all 8 EDI streams creates an unmatched operational intelligence layer — from dock performance to carrier scorecards. | Scalable Automation A fully EDI-enabled warehouse can handle 10x volume growth with minimal headcount increases — the automation scales with the business. |
How to Successfully Implement EDI for Warehouse Operations
Rolling out a complete EDI program is a structured project, not a plug-and-play installation. Here’s the proven roadmap for a successful implementation across all eight transaction codes:
EDI Implementation Roadmap
- Conduct a Trading Partner Audit — Map all current trading relationships: which retailers, suppliers, and carriers you exchange documents with, and which EDI codes they require. This shapes your implementation priority list.
- Choose Your EDI Platform — Decide between a fully managed EDI-as-a-service provider like Commport Communications, a direct VAN (Value Added Network), and an API-based modern EDI platform. Your volume, IT capacity, and trading partner requirements drive this decision.
- Integrate with Your WMS and TMS — EDI only delivers value when it flows directly into your core systems. Map EDI 940 intake to your WMS order management module. Map EDI 943/944 to your receiving workflows. Map 204/990/214/210 to your TMS transportation lifecycle.
- Build and Test Transaction Maps — Each trading partner may have unique segment requirements within the standard. Work with your EDI provider to build custom maps for each partner and execute comprehensive ISA testing before going live.
- Pilot with Low-Risk Partners First — Start with a single retailer and one or two carriers. Validate that the full loop — 940 → 945 and 204 → 990 → 214 → 210 — completes cleanly before scaling.
- Monitor, Alert, and Optimize — Implement EDI monitoring dashboards that flag failed transmissions, duplicate documents, and SLA breaches. Set up automated alerts for unacknowledged 940s, overdue 945s, or missing 990 responses.
- Expand and Onboard New Partners — With a tested framework in place, new trading partner onboarding becomes a templated process. The investment in your first implementation pays compounding dividends with every new partner added.
Common Pitfalls to Avoid
- Implementing EDI codes in isolation without connecting them to your WMS/TMS workflows — EDI data that isn’t actioned is just noise
- Ignoring trading partner-specific segment requirements — a technically valid X12 document can still fail a partner’s validation rules
- Failing to build exception handling workflows for rejected or unacknowledged transactions
- Underestimating the importance of acknowledgment codes (EDI 997/999) in confirming successful receipt
- Not establishing EDI SLA monitoring — a delayed EDI 945 can result in retailer chargebacks worth far more than your EDI platform costs
- Treating EDI as a one-time project rather than an ongoing program requiring monitoring, maintenance, and continuous improvement
Conclusion
EDI 940 through 214 aren’t just technical standards — they are the operational DNA of a modern, efficient warehouse.
When deployed as a complete ecosystem, they eliminate manual touchpoints, compress cycle times, achieve inventory accuracy at scale, and build the data foundation for continuous improvement.
The warehouses winning in today’s competitive landscape aren’t the ones with the biggest footprints — they’re the ones with the most intelligent, automated information flows. EDI is where that intelligence starts.
Commport EDI Solutions - #1 EDI Solutions in North America
Need Help? Download: Commport's EDI Buyers Guide
Unlock the full potential of your supply chain with our comprehensive EDI Buyer's Guide — your first step towards seamless, efficient, and error-free transactions
Frequently Asked Questions
EDI automates the exchange of shipping, receiving, freight, and billing information so warehouses can operate faster with fewer manual touchpoints.
EDI 940, 943, 944, 945, 204, 990, 214, and 210 as the key transaction sets that support outbound shipping, stock transfers, carrier tendering, status updates, and freight invoicing.
EDI 943 sends advance notice that inbound stock is coming to a warehouse, and EDI 944 confirms what was actually received after the goods arrive.
EDI 940 authorizes the warehouse to pick and ship outbound inventory, and EDI 945 confirms what was physically shipped after departure.
Because EDI creates real value only when incoming documents automatically trigger warehouse and transportation actions inside core systems, rather than requiring manual re-entry
EDI 990 lets a carrier accept, reject, or counter a load tender, making it the formal response that confirms whether the shipment will be moved.
