Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP

X12 transaction code

EDI 214 Transportation Carrier Shipment Status Message (X12 214)

EDI 214 is the shipment status update, the X12 Transportation Carrier Shipment Status Message transaction set, used when the carrier reports a transport milestone or exception. The motor carrier or its agent sends the 214 to the shipper, and often to the consignee or a 3PL managing the freight.

Standard
X12
Code
214
Partner references
170
Book an EDI demo ← All trading partners

At a glance

EDI 214 at a glance

What the 214 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.

X12 214 Transportation Carrier Shipment Status Message summary
Document X12 214 Transportation Carrier Shipment Status Message
Business record Shipment status event
Who sends it to whom The motor carrier or its agent sends the 214 to the shipper, and often to the consignee or a 3PL managing the freight.
When it is sent A shipment milestone or exception occurs, such as the driver departing the pickup location, an en route delay, or completed delivery, and the carrier's system emits the corresponding status update.
Match on Shipment reference, event code, event time and location
Partner references 170 trading partners in this directory
Related documents X12 204 Motor Carrier Load Tender, X12 990 Response to a Load Tender, X12 210 Motor Carrier Freight Details and Invoice

Key segments in an EDI 214

The business segments that appear in at least half of the 241 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.

Segment Name Purpose Partner references
B10 Beginning Segment for Transportation Carrier Shipment Status Message To transmit identifying numbers and other basic data relating to the transaction set. 241 of 241
LX Assigned Number To reference a line number in a transaction set. 241 of 241
AT7 Shipment Status Details To specify the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled. 240 of 241
L11 Business Instructions and Reference Number To specify instructions in this business relationship or a reference number. 232 of 241
MS1 Equipment, Shipment, or Real Property Location To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude. 221 of 241
MS2 Equipment or Container Owner and Type To specify the owner, the identification number assigned by that owner, and the type of equipment. 201 of 241
N1 Name To identify a party by type of organization, name, and code. 190 of 241
N4 Geographic Location To specify the geographic place of the named party. 173 of 241
N3 Address Information To specify the location of the named party. 168 of 241

Stacksync connects EDI documents such as the X12 214 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.

Implementation guide

X12 214 mapping and validation

X12 214 Transportation Carrier Shipment Status Message is used when the carrier reports a transport milestone or exception. Preserve shipment reference, event code, event time and location so the shipment status event in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record shipment status event

shipment reference, event code, event time and location
  • Define which combination of shipment reference, event code, event time and location identifies one business record, its lines and any later revision.
Update the receiving system Processing the shipment status event

ID assigned by the receiving system and processing result
  • Deliver an older status after a newer one and retain event history without moving the current status backward.
  • Send one milestone twice and avoid duplicate customer notifications.
Check the processing result Processing status for the shipment status event

Original document reference and matching response
  • Reconcile the shipment status event with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when the carrier reports a transport milestone or exception. Name the operational owner of the shipment status event and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map shipment reference, event code, event time and location. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic shipment status event data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful shipment status event processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 214 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic shipment status event data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out shipment status event without processing it twice.

Document structure

X12 214 Transportation Carrier Shipment Status Message at the element level

The X12 214 reference contains 68 segment entries and 316 data elements; 63 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
68
Data elements
316
Mandatory elements
63
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
B10 7 1
MAN 6 2
K1 2 1
N1 6 1
N2 2 1
N3 2 1
G61 5 2
MS3 5 2
LX 1 1
Q7 3 1
Key identifiers in 214
  • Standard Carrier Alpha Code
  • Marks and Numbers Qualifier
  • Marks and Numbers
  • Free-Form Message
  • Entity Identifier Code
  • Name
  • Address Information
  • Contact Function Code

Find your trading partner for X12 214

170 partners, 242 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 214 Transportation Carrier Shipment Status Message appears in this catalog

The largest groups of classified 214 catalog entries are in logistics & transport, grocery & food and retail.

By industry

  • logistics & transport 124 channels
  • grocery & food 46 channels
  • retail 17 channels
  • consumer goods 12 channels
  • building & hardware 10 channels
  • manufacturing & industrial 7 channels

By network

  • E2open 41 channels
  • MercuryGate 35 channels
  • Manhattan Associates 17 channels
  • Ryder 16 channels
  • Blue Yonder 12 channels
  • BluJay 5 channels
Partner entries with the most listed channels

FAQ

EDI 214 questions

What is an EDI 214?

EDI 214 is the shipment status update, the X12 Transportation Carrier Shipment Status Message transaction set. Trading partners use it when the carrier reports a transport milestone or exception. It carries the data for the shipment status event, and your system matches it on shipment reference, event code, event time and location.

Who sends an EDI 214 and who receives it?

The motor carrier or its agent sends the 214 to the shipper, and often to the consignee or a 3PL managing the freight. Your trading partner agreement confirms the direction and version for your account.

When is an EDI 214 sent?

A shipment milestone or exception occurs, such as the driver departing the pickup location, an en route delay, or completed delivery, and the carrier's system emits the corresponding status update. Your partner guide sets any deadline or schedule for the document.

What are the key segments in an EDI 214?

Across 241 partner document references listed here, the business segments that appear most often include B10 (Beginning Segment for Transportation Carrier Shipment Status Message), LX (Assigned Number), AT7 (Shipment Status Details), L11 (Business Instructions and Reference Number), MS1 (Equipment, Shipment, or Real Property Location), MS2 (Equipment or Container Owner and Type). Each partner guide sets which segments and elements your account must send.

What is the difference between EDI 214 and EDI 204?

The 204 tenders the load to the carrier. The 214 comes after the carrier takes it and reports status: pickup, in transit, delays and delivery.

What should I map for X12 214?

Start with shipment reference, event code, event time and location and the target shipment status event. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 214 error handling?

Deliver an older status after a newer one and retain event history without moving the current status backward. Send one milestone twice and avoid duplicate customer notifications. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

Which partners list X12 214?

The directory on this page links 170 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform