X12

Inbound

Expeditors X12 940 Warehouse Shipping Order

Expeditors

The EDI 940 (Warehouse Shipping Order) document is used by Expeditors for electronic data interchange. It enables automated processing and compliance with Expeditors's trading partner requirements.

18segments

3loops

5mandatory

Book a demo

← All Expeditors transactions

Schema Reference

18 segments · X12 940 Warehouse Shipping Order

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

W0501 Order Status Code

M ID 1-1

W0502 Depositor Order Number

M AN 1-22

W0503 Purchase Order Number

O AN 1-22

W0504 Link Sequence Number

C N0 6-6

W0505 Master Reference (Link) Number

C AN 1-22

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

PER01 Contact Function Code

M ID 2-2

PER02 Name

O AN 1-60

PER03 Communication Number Qualifier

C ID 2-2

PER04 Communication Number

C AN 1-80

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

N903 Free-form Description

C AN 1-45

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

NTE01 Note Reference Code

O ID 3-3

NTE02 Description

M AN 1-80

W6601 Shipment Method of Payment

M ID 2-2

W6602 Transportation Method/Type Code

M ID 1-2

W6605 Routing

O AN 1-35

W6610 Standard Carrier Alpha Code

O ID 2-4

LX Loop

LX01 Assigned Number

M N0 1-6

W01 Loop

W0101 Quantity Ordered

M R 1-15

W0102 Unit or Basis for Measurement Code

M ID 2-2

W0103 U.P.C. Case Code

C AN 12-12

W0104 Product/Service ID Qualifier

C ID 2-2

W0105 Product/Service ID

C AN 1-48

W0106 Product/Service ID Qualifier

C ID 2-2

W0107 Product/Service ID

C AN 1-48

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

N903 Free-form Description

C AN 1-45

NTE01 Note Reference Code

O ID 3-3

NTE02 Description

M AN 1-80

W7601 Quantity Ordered

M R 1-15

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating Expeditors EDI 940

Stacksync validates, transforms, and delivers your 940 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync processes Expeditors EDI 940 (Warehouse Shipping Order) documents automatically — syncing data to your system in real time with no manual intervention required.

Expeditors EDI 940 FAQ

Common questions about 940 Warehouse Shipping Order transactions with Expeditors.

What is a Expeditors EDI 940 Warehouse Shipping Order?

The Expeditors EDI 940 Warehouse Shipping Order is an X12 transaction set used to exchange Warehouse Shipping Order data electronically between trading partners. As a inbound document, it standardizes the communication of Warehouse Shipping Order information between Expeditors and their suppliers, carriers, or partners. Stacksync processes Expeditors 940 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Expeditors's requirements in real time.

How does Stacksync automate Expeditors EDI 940 Warehouse Shipping Order transactions?

Stacksync handles Expeditors EDI 940 Warehouse Shipping Order transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 940 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Expeditors 940 document meets their specific formatting requirements before transmission or after receipt.

What are common Expeditors EDI 940 errors and how do I fix them?

Common errors in Expeditors EDI 940 Warehouse Shipping Order transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Expeditors 940 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Expeditors EDI 940 with Stacksync?

Most Expeditors EDI 940 Warehouse Shipping Order integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Expeditors's 940 format and your system, running test transactions, and completing Expeditors's certification process if required. Stacksync includes pre-built mappings for Expeditors's most common 940 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Expeditors EDI 940 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Expeditors EDI 940 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Expeditors updates their 940 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Expeditors EDI?