Skip to content
X12 EDI

E2open, LLC X12 214 Transportation Carrier Shipment Status Message

Plan X12 214 Transportation Carrier Shipment Status Message for E2open, LLC / Truco (UTZ Brands) (via E2open). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
14
Loops
3
X12 214
Partner references ↗
Book an EDI demo ← All Truco (UTZ Brands) (via E2open) transactions

Implementation guide

E2open, LLC / Truco (UTZ Brands) (via E2open): 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.

This document is listed for E2open, LLC / Truco (UTZ Brands) (via E2open). Confirm the version, required fields and responses that apply to your account.

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.

The document reference includes 14 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

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 E2open, LLC 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.

Transaction context

Where 214 Transportation Carrier Shipment Status Message fits on Truco (UTZ Brands) (via E2open)

On Truco (UTZ Brands) (via E2open), the X12 214 Transportation Carrier Shipment Status Message can follow the 204 Motor Carrier Load Tender and 990 Response To A Load Tender and can precede the 210 Motor Carrier Freight Details And Invoice in an example Logistics cycle. Confirm the required sequence for your trading agreement.

E2open, LLC channels
37 of 37

37 of E2open, LLC's 37 channels list 214

Trading partners
170

partner references list 214

Channels
242

channel entries list 214

Frequently listed alongside 214

The directory associates E2open and 214 with 41 channels.

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
Segment reference — 14 segments 3 loops · X12 214 Transportation Carrier Shipment Status Message
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

B10 Beginning Segment for Transportation Carrier Shipment Status Message 3 elements

To transmit identifying numbers and other basic data relating to the transaction set

L11 Business Instructions and Reference Number 2 elements

To specify instructions in this business relationship or a reference number

N1 Loop Repeat: 10
N1 Name 4 elements

To identify a party by type of organization, name, and code

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 4 elements

To specify the geographic place of the named party

LX Loop Repeat: 999,999
LX Assigned Number 1 element

To reference a line number in a transaction set

AT7 Loop Repeat: 10
AT7 Shipment Status Details 7 elements

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.

MS1 Equipment, Shipment, or Real Property Location 5 elements

To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude

MS2 Equipment or Container Owner and Type 2 elements

To specify the owner, the identification number assigned by that owner, and the type of equipment

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

K1 Remarks 1 element

To transmit information in a free-form format for comment or special instruction

Related references

214 Transportation Carrier Shipment Status Message on other E2open, LLC channels

Compare the listed channel references and confirm their current implementation guides.

Nouryon (via E2open) X12 214 Ruiz Foods (via E2open) X12 214 Ball Corporation (via E2open) X12 214 America's Logistics (Amer Serv Lines) (via E2open) X12 214 JBS Swift (via E2open) X12 214 Rise Baking via E2Open X12 214 Blujay Solutions TM Shippers X12 214 Chiquita (via E2open) (1425470) X12 214 Schwan's (via E2open) X12 214 Arkema (via E2open) X12 214 AWG (via E2open) X12 214 Butterball Lean (via E2open) X12 214 Winona Foods LLG (via E2open) X12 214 HB Fuller (via E2open) X12 214 Bar-S Foods (via E2open) X12 214 Reyes Holdings (via E2open) X12 214 CHEP (via E2open) X12 214 Barilla (via E2open) X12 214 Lakeview Farms (via E2open) X12 214 Sargento (via E2open) X12 214 Malt (via E2open) X12 214

Showing 21 of 36 references

Browse the full directory

Related references

Other transactions in Truco (UTZ Brands) (via E2open)

Other EDI documents listed on this channel.

Response To A Load Tender X12 990 Motor Carrier Freight Details And Invoice X12 210 Motor Carrier Load Tender X12 204

Showing 3 of 3 references

Browse the full directory

E2open, LLC / Truco (UTZ Brands) (via E2open) EDI 214 questions

Common questions about 214 Transportation Carrier Shipment Status Message on the Truco (UTZ Brands) (via E2open) channel.

What is X12 214 Transportation Carrier Shipment Status Message used for?

214 is used when the carrier reports a transport milestone or exception. It carries information for the shipment status event. Match it to your business system using shipment reference, event code, event time and location.

Is 214 required for E2open, LLC / Truco (UTZ Brands) (via E2open)?

214 is listed for E2open, LLC / Truco (UTZ Brands) (via E2open). Confirm the required version and direction for your business unit and account with the partner.

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.

How does 214 relate to other EDI messages?

X12 204 Motor Carrier Load Tender; X12 990 Response To A Load Tender; X12 210 Motor Carrier Freight Details And Invoice are related documents also listed on Truco (UTZ Brands) (via E2open). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 214 and 204?

214 is used when the carrier reports a transport milestone or exception. 204 is used when a shipper offers a load to a carrier. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect E2open, LLC 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