To start and identify an interchange of zero or more functional groups and interchange-related control segments
UPS X12 214 Transportation Carrier Shipment Status Message
X12 214 (Transportation Carrier Shipment Status Message) is the EDI transaction exchanged between UPS (UPS Plus) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 17
- Loops
- 4
- X12 214
- All partners ↗
Transaction context
Where 214 Transportation Carrier Shipment Status Message fits on UPS Plus
- UPS channels
- 1 of 1
- Trading partners
- 170
- Channels
- 242
1 of UPS's 1 channel carries 214
partners across the Stacksync network trade 214
channels network-wide carry 214
Most common alongside 214
The 214 reports shipment milestones and exceptions: arrival at pickup, departure with the shipment, en route updates, delays with reason codes, and completed delivery, each stamped with dates, times, and locations. Shippers and consignees require it for track and trace, dock and labor scheduling, and carrier performance measurement, and they reconcile it against the 204 tender and the 210 freight bill before authorizing payment. 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 fires: 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.
Common 214 rejection causes
- Reference mismatches with the 204: partner specs require the 214 shipment ID to echo the tender's value exactly (Ryder maps B10-02 to the 204 B2-04, with no blanks or special characters), or the status fails application processing.
- Invalid status and reason code pairs: AT7 requires both a shipment status code and a reason code from the partner's published lists, and messages the receiver cannot apply are returned to the carrier on an 824 Application Advice.
- Missing mandatory identifiers: the Standard Carrier Alpha Code (B10-03) is mandatory and the carrier PRO number is required, and their absence keeps the receiver from tying the status to a shipment.
- Unmonitored acknowledgments: partners return 997s (Ryder sends one within 24 hours) and expect carriers to reconcile them; unchased missing 997s or 824 rejects leave silent gaps in the status feed.
Specification summary
X12 214 Transportation Carrier Shipment Status Message at the element level
The X12 214 specification defines 68 segments carrying 316 data elements, 63 of which are mandatory.
- Segments
- 68
- Data elements
- 316
- Mandatory elements
- 63
| 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
Full segment guideline — 17 segments 4 loops · X12 214 Transportation Carrier Shipment Status Message
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit identifying numbers and other basic data relating to the transaction set
To specify instructions in this business relationship or a reference number
To indicate identifying marks and numbers for shipping containers
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify additional names or those longer than 35 characters in length
To specify the location of the named party
To specify the geographic place of the named party
To identify a person or office to whom communications should be directed
LX Loop Repeat: 999,999
To reference a line number in a transaction set
AT7 Loop Repeat: 10
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.
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify pertinent dates and times
SPO Loop Repeat: 999,999
To specify the purchase order details for a shipment
To specify destination and quantity detail
Trading partners
4+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
UPS UPS Plus EDI 214 FAQ
Common questions about 214 Transportation Carrier Shipment Status Message on the UPS Plus channel.
What is X12 214 Transportation Carrier Shipment Status Message?
X12 214 (Transportation Carrier Shipment Status Message) is the EDI transaction set used to exchange transportation carrier shipment status message data. UPS's UPS Plus channel requires it from trading partners.
Does UPS UPS Plus require 214 for trading partners?
Yes, UPS (UPS Plus) supports X12 214 Transportation Carrier Shipment Status Message. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate UPS 214 with Stacksync?
Most companies go live with UPS 214 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 214 on UPS Plus?
On UPS Plus, X12 214 is typically exchanged alongside 856 Ship Notice Manifest. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your UPS EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
