EDI 940 - Warehouse Shipping Order

What Is the EDI 940?

EDI 940 is used to electronically instruct a warehouse or third-party logistics provider (3PL) to release, pick, pack, and ship inventory. The transaction standardizes warehouse fulfillment instructions including items, quantities, ship-to locations, carrier routing, and requested shipment dates to improve fulfillment accuracy and operational visibility. 

What Is EDI 940 Used For? 

EDI 940 is used to electronically authorize a warehouse or third-party logistics provider (3PL) to release, pick, pack, and ship inventory. The transaction standardizes fulfillment instructions including products, quantities, carrier routing, destinations, and requested shipment dates to improve warehouse execution and shipment accuracy. 
 

Transaction Identity Block 

EDI 940 Quick Facts 

What Is the EDI 940? 

The EDI 940 Warehouse Shipping Order is a structured electronic instruction used by a seller or depositor to authorize a warehouse or third-party logistics provider (3PL) to release and ship inventory. It replaces manual instructions with a standardized digital command that defines items, quantities, destinations, and shipping requirements.  

What Does the EDI 940 Do? 

The EDI 940 directs warehouse operations to ship inventory accurately and on time while maintaining alignment with customer commitments and fulfillment controls. The transaction communicates: 

• What products to ship
• The quantity of each item
• Where products should ship
• Carrier and routing instructions
• Special handling requirements
• Shipment timing and fulfillment instructions

The transaction supports original, change, replacement, and cancellation scenarios, enabling dynamic order control within fulfillment operations. 

Who Uses the EDI 940? 

• Retailers and wholesalers
• Manufacturers
• E-commerce fulfillment providers
• 3PL and warehouse operators
• Grocery and cold-chain distributors  

What Industries Use the EDI 940? 

The EDI 940 is widely used across retail, grocery, manufacturing, healthcare, automotive, e-commerce, and third-party logistics environments. Organizations use the transaction to coordinate warehouse fulfillment, inventory release, and shipment execution across multi-enterprise supply chain operations. 

When Is the EDI 940 Required? 

The EDI 940 is required whenever: 

• A warehouse must ship inventory on behalf of a seller
• A fulfillment instruction must be communicated electronically 

• Multi-warehouse or outsourced logistics models are in use  

   

Is the EDI 940 Mandated Under Regulation? 

The EDI 940 is not mandated by regulation but is contractually required in most warehouse and 3PL relationships. Compliance is driven by trading partner agreements and operational SLAs. 

Why Is the EDI 940 Important?

The EDI 940 acts as the operational bridge between order management systems and warehouse execution environments. The transaction improves fulfillment coordination, reduces manual warehouse communication, supports inventory synchronization, and establishes a structured workflow for downstream shipment visibility and transportation tracking. 

#ExplorePartnerLinQ 

• Phantom Inventory Is Stealing Your Margins
• Warehouse & Fulfillment Integration
• Transactional Visibility
• Multi-Enterprise Orchestration 

How Does the EDI 940 Work in the Business Workflow? 

The EDI 940 Warehouse Shipping Order is used by a seller or depositor to authorize a warehouse or third-party logistics provider (3PL) to release and ship inventory on the seller’s behalf. The transaction replaces paper instructions, emails, and phone calls with a structured electronic instruction that specifies products, quantities, shipping dates, locations, carrier information, and special handling requirements. 

Upstream Transactions 

Warehouse Execution Trigger 

Downstream Transactions

The workflow begins when a customer order is received and validated. The supplier or seller then transmits the EDI 940 to the warehouse or 3PL. The warehouse uses the transaction to initiate: 

• Picking
• Packing
• Carrier preparation
• Shipment release
• Carton and pallet processing
• Shipment documentation  

Once fulfillment execution is complete, the warehouse responds with the EDI 945 Warehouse Shipping Advice to confirm shipped items and quantities. Additional visibility transactions such as the EDI 856 ASN and EDI 214 shipment status updates may then follow 

End-to-End Workflow Example 

1. Customer places an order through ERP or OMS
2. Supplier validates inventory and acknowledges the order
3. Supplier sends the EDI 940 to the warehouse or 3PL
4. Warehouse executes pick, pack, and ship activities
5. Warehouse returns the EDI 945 confirming shipment execution
6. Shipment visibility is provided through EDI 856 and EDI 214 transactions 

7. ERP and visibility systems reconcile fulfillment activity  

    

Industry-Specific Workflow Variations 

The EDI 940 supports multiple warehouse fulfillment models including:

• Retail store replenishment
• Direct-to-consumer fulfillment
• Grocery and cold-chain logistics
• Export palletized shipments
• Multi-warehouse distribution
• Carton-level fulfillment with serialized traceability  

The transaction supports both: 

• Item Warehouse Shipping Order workflows
• Carton Warehouse Shipping Order workflows  

The carton-based model enables specific cartons and palletized logistics units to be identified using GS1 SSCC container serial numbers. 

How Does the EDI 940 Improve Warehouse Execution? 

The EDI 940 improves warehouse execution by reducing manual data entry, reducing paper flow, improving fulfillment accuracy, and accelerating warehouse processing. Structured electronic shipment instructions improve operational efficiency across warehouses, suppliers, retailers, and logistics providers. 

Operational Value of the EDI 940 

The EDI 940 improves warehouse execution by: 

• Reducing manual data entry
• Reducing paper flow
• Improving fulfillment accuracy
• Supporting traceable shipping authorization
• Accelerating warehouse processing
• Standardizing communication between trading partners  

The transaction establishes an electronic and auditable fulfillment instruction process while improving operational efficiency across multi-enterprise supply chain environments.  

Why Is EDI 940 Important in Warehouse Operations? 

EDI 940 enables warehouses and 3PL providers to automate shipment execution using standardized digital instructions. The transaction improves fulfillment speed, reduces manual processing errors, supports inventory synchronization, and provides a structured foundation for downstream shipment visibility through EDI 945 and EDI 856 transactions. 
 

Cross-Standard Canonical Mapping 

How does PartnerLinQ use the 940? 

PartnerLinQ transforms ERP and OMS shipment instructions into the EDI 940 transaction, validates mandatory data elements before transmission, and sends the transaction to warehouses and 3PL providers. The platform then monitors inbound EDI 945 Warehouse Shipping Advice transactions to reconcile shipped versus requested quantities and update visibility systems 

Where Is the EDI 940 Used? 

• Warehouse management systems (WMS)
• Transportation and logistics platforms
• ERP-integrated fulfillment environments
• Multi-enterprise supply chain networks  

Are there Industry-Specific Responses? 

Yes, there are Industry-Specific Responses that vary by partner relationship. 

• 945 → Warehouse confirmation
• 997 / 999 → Acknowledgments
• 856 → Shipment visibility  

What Is the Purpose of the EDI 940 Warehouse Shipping Order? 

The EDI 940 Warehouse Shipping Order is used to authorize a warehouse or third-party logistics provider (3PL) to release and ship inventory on behalf of a seller. The transaction replaces paper instructions with a structured electronic instruction that specifies products, quantities, shipping dates, locations, and fulfillment requirements. 

What Are the Key Features of the EDI 940?

The EDI 940 supports digital shipment authorization, structured warehouse execution, carrier routing guidance, carton and pallet traceability, and warehouse lifecycle management. The transaction supports item-level and carton-level fulfillment models while enabling standardized communication between sellers, warehouses, and 3PL providers. 

What Business Use Cases Does the EDI 940 Support? 

The EDI 940 supports: 

• 3PL fulfillment operations
• Retail replenishment
• Direct-to-consumer fulfillment
• Grocery and cold-chain logistics
• Export and palletized shipments
• Multi-warehouse distribution models
• Serialized carton and pallet tracking  

The transaction is widely used in retail, grocery, manufacturing, healthcare, distribution, and logistics environments. 

Common Industries Using the 940 - Industry Application 

What Fulfillment Models Does the EDI 940 Support? 

The EDI 940 supports two warehouse fulfillment models: 

• Item Warehouse Shipping Order
• Carton Warehouse Shipping Order  

The item-based model supports shipping the same products to multiple locations, while the carton-based model supports serialized carton fulfillment to a single destination using container serial numbers and SSCC identifiers.  

How Does the EDI 940 Support Traceability? 

The EDI 940 supports GS1 identifiers including GTIN and SSCC as well as EPC/RFID data carriers and serialized product identification. This enables pallet, carton, and logistics unit traceability across warehouse and transportation workflows.  

What Information Does an EDI 940 Contain? 

An EDI 940 contains warehouse shipping instructions including order identifiers, ship-to locations, requested shipment dates, carrier routing information, item quantities, and fulfillment details. Common segments include W05 for shipping order control, N1 for party identification, G62 for scheduling, and W01 for item-level shipment detail. 

What Information Is Included in an EDI 940?

An EDI 940 includes: 

• Seller order number
• Buyer purchase order number
• Ship-to and ship-from locations
• Requested shipment dates
• Item quantities and identifiers
• Carrier and transportation details
• Special handling instructions
• Weight, volume, and shipment totals  

The transaction may also support GTIN, SSCC, EPC/RFID, lot numbers, and serialized traceability identifiers. 

What Data Is Required in an EDI 940? 

An EDI 940 typically includes order identifiers, warehouse locations, requested shipment dates, item quantities, carrier routing instructions, and fulfillment detail necessary for a warehouse or 3PL to accurately release and ship inventory on behalf of a seller. 

What Information Is Required in the EDI 940? 

The EDI 940 Warehouse Shipping Order requires the information necessary for a warehouse or third-party logistics provider (3PL) to accurately release, pick, pack, and ship inventory on behalf of a seller. At a minimum, the transaction includes the seller’s order number, buyer purchase order number, shipping dates, ship-to location, item quantities, and warehouse fulfillment instructions. 

What Core Data Is Included in an EDI 940? 

The EDI 940 commonly includes: 

• Seller order number
• Buyer purchase order number
• Ship-from and ship-to locations
• Warehouse identification
• Item identifiers and quantities
• Unit of measure
• Requested shipping dates
• Carrier and routing instructions
• Special handling instructions
• Shipment totals including weight and volume  

The transaction may also support GTIN, SSCC, EPC/RFID identifiers, lot numbers, and serialized carton or pallet information.  

Quick Segment Reference 

What Required Segments Are Used in the EDI 940? 

The EDI 940 uses structured ANSI X12 segments to communicate warehouse shipping instructions. Common required segments include: 

• ST — Transaction Set Header
• W05 — Shipping Order Identification
• N1/N3/N4 — Party and location identification
• G62 — Date and time information
• LX — Transaction line numbering
• W01 — Line-item warehouse detail
• SE — Transaction Set Trailer 

What Does the W05 Segment Contain? 

The W05 Shipping Order Identification segment provides key order control information including: 

• Order status code
• Depositor order number
• Buyer purchase order number  

The segment identifies whether the transaction is: 

• Original
• Change
• Cancellation
• Replacement order  

PartnerLinQ uses the W0501 element to identify transaction purpose codes such as: 

• N = Original
• R = Change
• F = Cancel 

What Location Information Is Required in the EDI 940? 

The EDI 940 uses the N1, N3, and N4 segments to identify: 

• Ship-from locations
• Ship-to locations
• Warehouses
• Carriers
• Consignees
• Billing parties  

Location identifiers may include: 

• GLN (Global Location Number)
• DUNS numbers
• SCAC codes
• Seller-assigned location identifiers 

What Product and Quantity Information Is Required? 

The W01 Line Item Detail segment communicates: 

• Product identifiers
• Item quantities
• Unit of measure
• Packaging detail
• GTINs
• Seller item numbers
• Serialized carton or pallet identifiers  

The transaction supports both item-based and carton-based fulfillment models.  

What Carrier and Transportation Information Is Included?

The W66 Warehouse Carrier Information segment supports: 

• Carrier identification
• Transportation method
• SCAC codes
• FOB instructions
• Routing guidance  

Additional shipment handling requirements may be communicated using: 

• W6 Special Handling Information
• NTE Note/Special Instruction
• N9 Extended Reference Information 

What Dates Are Required in the EDI 940? 

The G62 Date/Time segment communicates important scheduling information including: 

• Requested ship date
• Pickup date
• Delivery requested date
• Must respond by date  

These dates help warehouses coordinate fulfillment execution and transportation scheduling. 

What Totals and Validation Information Are Included? 

The W76 Total Shipping Order segment supports shipment validation by communicating: 

• Total quantities
• Shipment weight
• Shipment volume
• TL/LTL transportation estimation support  

These totals help validate fulfillment accuracy and transportation planning 

Optional Segments 

N9, PER, NTE, W6 

Required Identifiers 

• Order number (W0502)
• Purchase Order (W0503)
• Location codes (GLN/DUNS)  
   

Required Dates 

• Ship date
• Requested delivery  
   

Common Segments 

What Status and Reason Codes Are Used? 

The EDI 940 Warehouse Shipping Order primarily uses status and action indicators within the W05 Shipping Order Identification segment, specifically element W0501 (Order Status Code). These codes identify the purpose of the transaction such as creating a new order, changing an existing order, or canceling a shipment instruction. 

Common EDI 940 Status Codes (W05-01) 

What Reason Codes Are Used in the EDI 940? 

The EDI 940 does not contain a dedicated structured “Reason Code” segment for explaining changes, cancellations, or adjustments. Instead, implementations commonly use: 

• N9 Extended Reference Information
• NTE Note/Special Instruction
• Custom mutually defined qualifiers such as “ZZ”  

These segments provide supplemental explanation or reference detail related to warehouse fulfillment 

What are the Benefits of the 940? 

The EDI 940 Warehouse Shipping Order improves warehouse execution by replacing paper instructions, emails, and manual communication with a structured electronic transaction that standardizes shipment authorization, fulfillment instructions, and warehouse coordination. The transaction helps organizations improve operational efficiency, fulfillment accuracy, traceability, and warehouse execution control. 

How Does the EDI 940 Improve Warehouse Operations?

The EDI 940 improves warehouse operations by electronically communicating: 

• What products to ship
• Quantities to fulfill
• Ship-to destinations
• Requested shipment dates
• Carrier routing instructions
• Special handling requirements  

Structured electronic fulfillment instructions reduce manual data entry, improve warehouse coordination, and accelerate shipment processing across warehouses and 3PL providers. 

What Operational Benefits Does the EDI 940 Provide? 

The EDI 940 provides several operational benefits including: 

• Faster warehouse execution
• Reduced manual processing
• Improved fulfillment accuracy
• Reduced paper flow
• Standardized shipment communication
• Improved coordination between sellers and warehouses
• Better execution visibility across fulfillment workflows  

Trading partners using the EDI 940 improve operating efficiencies through reduced data entry and substantially reduced paper flow. 

How Does EDI 940 Improve Fulfillment Accuracy? 

EDI 940 improves fulfillment accuracy by replacing manual warehouse instructions with standardized electronic shipment requests. Automated validation of item quantities, locations, routing instructions, and shipping dates helps reduce picking errors, shipment delays, inventory discrepancies, and downstream fulfillment exceptions. 

What Financial Benefits Does the EDI 940 Provide?  

The EDI 940 helps reduce operational costs by:  

• Reducing manual labor
• Reducing shipping errors
• Reducing paper-based processing
• Improving warehouse productivity
• Supporting automated fulfillment workflows  

The transaction also improves shipment coordination between ERP systems, warehouses, transportation providers, and 3PL operations. 

What Compliance and Standardization Benefits Does the EDI 940 Provide? 

The EDI 940 standardizes communication between sellers, warehouses, carriers, and 3PL providers using ANSI X12 structures and GS1 identifiers. The transaction establishes a traceable electronic authorization trail that improves consistency, interoperability, and fulfillment governance across multi-enterprise supply chain environments.  

• Traceable shipping authorization
• Standardized communication  

Why Automate the EDI 940? 

Automating the EDI 940 reduces manual warehouse coordination and accelerates fulfillment execution through structured electronic workflows. Automation improves shipment accuracy, reduces fulfillment delays, supports exception monitoring, and enhances visibility across warehouse, transportation, and inventory management operations. 

What Are the Benefits of Automating the EDI 940? 

Automating the EDI 940 Warehouse Shipping Order improves warehouse execution by replacing manual shipment coordination with structured electronic workflows that accelerate fulfillment processing, improve shipment accuracy, and standardize communication between ERP systems, warehouses, carriers, and third-party logistics providers (3PLs).  

• Real-time order release
• Automated validation
• Exception monitoring
• Full lifecycle visibility  

Before vs After EDI 940 Automation Table 

How Does EDI 940 Automation Improve Warehouse Execution? 

EDI 940 automation enables warehouses and 3PL providers to receive shipment instructions electronically rather than through paper documents, emails, or phone calls. Automated warehouse instructions improve fulfillment speed, reduce manual processing delays, and support more accurate shipment execution. 

What Operational Benefits Does EDI 940 Automation Provide? 

Automating the EDI 940 provides operational benefits including: 

• Real-time order release
• Automated validation
• Exception monitoring
• Full lifecycle visibility
• Faster warehouse execution
• Reduced manual errors
• Reduced paper flow  

These capabilities improve warehouse efficiency and help standardize fulfillment execution across multi-enterprise supply chain environments.  

How Does EDI 940 Automation Reduce Errors? 

EDI 940 automation validates shipment instructions before transmission by verifying: 

• Order numbers
• Item quantities
• Ship-to locations
• Shipment dates
• Carrier information
• Product identifiers  

Automated validation reduces fulfillment errors caused by manual data entry, incomplete shipment instructions, and inconsistent warehouse communication.  

How Does EDI 940 Automation Support Traceability? 

Automated EDI 940 workflows support serialized and standards-based traceability using: 

• GTIN product identifiers
• GS1 SSCC pallet and carton identifiers
• EPC/RFID data carriers
• Product serial number identification
• Contractual compliance with trading partners  

These capabilities improve visibility and control across warehouse, pallet, carton, and transportation workflows.  

How Does EDI 940 Automation Improve Multi-Warehouse Operations? 

The EDI 940 supports multi-warehouse and outsourced fulfillment models by electronically coordinating shipment instructions across warehouse management systems, transportation providers, and 3PL environments. Automated fulfillment workflows improve consistency, execution speed, and coordination across distributed logistics operations. 

EDI 940 Technical Structure, Format, and Versions 

The EDI 940 Warehouse Shipping Order follows a structured ANSI X12 format designed to communicate warehouse shipment instructions with precision, traceability, and validation control, an architecture comprised of header, detail, and trailer sections, with a strong emphasis on item-level granularity (W01) and transaction-level control (ST/SE). 

Hierarchical Loop Structure 

• Heading: ST, W05, N1 loop
• Detail: LX loop → W01
• Summary: W76, SE  

File Format and Delimiters 

Using the following Production Delimiters on all EDI transmissions sent to Vendors, Carriers, Trading and Solution partners will enable consistent EDI parsing across trading partners: 

• Segment Separator – hex 15 (NAK) or hex 7E (~)
• Element separator – hex 7C (|) or hex 2A (*)
• Sub-element Separator – hex 3E (>) 

Version Differences 

The EDI 940 is defined by ANSI X12 standards, with multiple versions in use despite newer versions. 

Is the EDI 940 Real-Time? 

The EDI 940 is traditionally a batch-oriented transaction and is not inherently real-time. Modern integration platforms improve responsiveness by automating transmission, validation, orchestration, and downstream warehouse execution workflows to support near real-time fulfillment visibility. 

What Are the Limitations of the EDI 940? 

The EDI 940 Warehouse Shipping Order provides structured warehouse shipment instructions, but like many ANSI X12 transactions, the standard has limitations related to real-time processing, flexibility, and structured exception handling. These limitations are often addressed through integration platforms, implementation guidelines, and supplemental business processes.  

Is the EDI 940 Real-Time?

The EDI 940 is not inherently a real-time transaction. Traditional EDI environments typically process warehouse shipping orders in scheduled or batch-oriented transmission cycles rather than through event-driven real-time messaging. Organizations often rely on integration platforms and automated orchestration workflows to improve fulfillment responsiveness and shipment visibility.  

What Flexibility Limitations Exist in the EDI 940? 

The EDI 940 follows a structured ANSI X12 format designed around standardized warehouse shipping instructions. While this structure improves consistency and interoperability, legacy transaction formats can limit flexibility when highly customized fulfillment scenarios or dynamic operational workflows are required.  

Does the EDI 940 Have Structured Reason Codes? 

The EDI 940 does not contain a dedicated structured “Reason Code” segment for cancellations, adjustments, or fulfillment exceptions. Implementations commonly rely on: 

• N9 Extended Reference Information
• NTE Note/Special Instruction
• Custom mutually defined qualifiers  

Because these approaches are not fully standardized, organizations may experience inconsistencies between trading partner implementations.  

What Data Limitations Exist in the EDI 940? 

Some EDI 940 implementations rely on free-form notes and unstructured text within the NTE segment for communicating special instructions, explanations, or operational exceptions. While functional, unstructured notes reduce standardization and may require manual interpretation by warehouse or logistics personnel.  

Can EDI 940 Change Management Be Complex? 

Complex order changes can create operational challenges in warehouse fulfillment environments. PartnerLinQ notes that significant shipment modifications may require a “change by refresh” process where: 

• The original order is canceled
• A replacement order is generated
• A new “Original” transaction is transmitted  

This approach improves fulfillment accuracy but may add operational complexity when orders change after warehouse execution has already begun.  

What Warehouse Challenges Does the EDI 940 Solve?  

The EDI 940 helps organizations address: 

• Manual warehouse communication
• Shipment coordination delays
• Inventory synchronization issues
• Fulfillment visibility gaps
• Picking and shipping errors
• Multi-warehouse coordination complexity
• Paper-based shipment authorization workflows  

The transaction standardizes warehouse execution and improves coordination between ERP systems, warehouses, carriers, and third-party logistics providers. 

Does the EDI 940 Require Trading Partner Coordination? 

Successful EDI 940 implementations depend heavily on trading partner agreements, implementation guides, and warehouse operational alignment. Trading partners frequently define: 

• Required segments
• Identifier standards
• Routing requirements
• Shipment timing expectations
• Validation rules  

Differences between implementation guides can increase onboarding and integration complexity across multi-enterprise environments.  

Can the EDI 940 Create Visibility Gaps Without Integration? 

The EDI 940 primarily communicates warehouse shipment instructions. Additional transactions such as: 

• EDI 945 Warehouse Shipping Advice
• EDI 856 Advance Ship Notice
• EDI 214 Transportation Status  

are typically required to achieve end-to-end shipment visibility, transportation tracking, and fulfillment reconciliation. Without integrated downstream workflows, visibility gaps may exist between shipment release and shipment confirmation.  

Are Implementation Guidelines and Sample Files Available for the X12 EDI 940  

Yes. PartnerLinQ provides sample transactions and implementation guides. EDI 940 implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding.  

Companion Guides 

Trading partners frequently publish X12 EDI 940 implementation guidelines defining segment usage and validation rules. Customized specification documents for use in on boarding and technical development are available through PartnerLinQ Support and Guideline Management. 

Trading Partner Requirements 

Trading partners define: 

• Required segments
• Frequency expectations
• Identifier standards  

EDI 940 Example File (X12 Sample) 

ST*940*0001~

W05*N*ORD100245*PO5609755~

N1*SF*Seller Warehouse*91*1311~

N1*ST*Smith Pharmacy Chain*91*0000100027~

N3*50 INDUSTRY DRIVE WEST~

N4*SPRINGFIELD*MA*06270~

G62*10*20250625~

G62*64*20250627~

W66*PP*M********UNKN~

LX*1~

W01*20*EA**VN*ITEM-82873510102~

N9*LT*LOT150707~

SE*12*0001~
  

Annotated Sample

Common Errors and Rejection Scenarios

What are the Basic Questions for EDI Integration? 

1. Are there Samples and Specs available?
2. What is the general direction of the transaction?
3. Are inbound or outbound orders required?
4. Are AS2, VAN, or SFTP connections used?
5. Are more than one trading partner exchanging the [Transaction ID]?
6. Are there other interested parties?
7. What trading partner requirements apply?
8. What version is required?
9. What versions are supported?
10. What other transactions might these interested parties be a party to?
11. What response to the [Transaction ID] is expected or sent?
12. Is a response to [Transaction ID] a timed event?  Are notifications involved/needed?
13. What system generates the response?
14. What response time is contractually required?
15. Are there samples and specs of the response transaction available?
16. Are change orders supported?
17. What validation rules apply?
18. How are changes to the [Transaction ID] business message managed today?
19. Is there automation? (an internal system trigger) or are [Transaction ID] business message transactions triggered manually?
20. How is automation managed (manual vs. system-triggered)?
21. Are responses and changes automatically triggered? (an internal system trigger)
22. Are alerting systems configured for missed response deadlines?
23. Do transactions require human intervention?
24. What systems generate or consume the transaction?
25. How are changes to the business message managed today?
26. How are one-time addresses handled in ERP?
27. What identifiers are used (SSCC, GTIN)?
28. Are SKU or UPC identifiers used?
29. What identifiers are required (SKU, UPC, GTIN)?
30. What testing process is required?
31. What validation rules must be applied?  

What are the Best Practices for using the EDI 940? 

Best Practices for organizations using the EDI 940 Warehouse Shipping Order include: 

What Transactions are associated with the 940? 

EDI 940 vs EDI 945  

How the EDI 940 Fits into the Warehouse Fulfillment Lifecycle 

FAQs 

What is EDI 940? 

EDI 940 is a warehouse shipping order used to instruct a warehouse or 3PL to release and ship goods. It defines items, quantities, destinations, and shipping instructions in a standardized electronic format.  
 

How does EDI 940 work? 

EDI 940 flows from a supplier or retailer to a warehouse, triggering fulfillment. The warehouse executes shipment and responds with EDI 945 to confirm completion. 
 

Who sends EDI 940? 

Suppliers, manufacturers, or retailers send EDI 940 to warehouses or 3PL providers to initiate shipment. 
 

What comes after EDI 940? 

The warehouse responds with EDI 945 and may trigger EDI 856 (ASN) and 214 (status updates). 

Footnotes 

1. PartnerLinQ EDI 940 Functional Overview
2. PartnerLinQ 940 Specification (v4010)
3. Sample EDI 940 Files
4. Integration Questions Framework