X12
Outbound

Sazerac Company (via Blue Yonder) X12 214 Transportation Carrier Shipment Status Message

Sazerac Company (via Blue Yonder)
The EDI 214 provides real-time shipment status updates to Sazerac Company (via Blue Yonder). Carriers transmit pickup confirmations, in-transit milestones, and delivery confirmations as freight moves through the network.
15segments
3loops
7mandatory

Schema Reference

15 segments · X12 214 Transportation Carrier Shipment Status Message

ISA ISA Interchange Control Header
Mandatory Max: 1
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 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator 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 Interchange Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 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
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
B10 Beginning Segment for Transportation Carrier Shipment Status Message
Mandatory Max: 1
B1001 Reference Identification
C AN 1-50
B1002 Shipment Identification Number
O AN 1-30
B1003 Standard Carrier Alpha Code
M ID 2-4
MS3 Interline Information
Optional Max: 12
MS301 Standard Carrier Alpha Code
M ID 2-4
MS302 Routing Sequence Code
M ID 1-2
LX Loop Repeat: 999,999
LX Transaction Set Line Number
Mandatory Max: 1
LX01 Assigned Number
M N0 1-6
L11 Business Instructions and Reference Number
Optional Max: 999
L1101 Reference Identification
C AN 1-50
L1102 Reference Identification Qualifier
C ID 2-3
AT8 Shipment Weight, Packaging and Quantity Data
Optional Max: 10
AT801 Weight Qualifier
C ID 1-2
AT802 Weight Unit Code
C ID 1-1
AT803 Weight
C R 1-10
AT7 Loop Repeat: 10
AT7 Shipment Status Details
Mandatory Max: 1
AT701 Shipment Status Indicator
C ID 2-2
AT702 Shipment Status or Appointment Reason Code
O ID 2-2
AT703 Shipment Appointment Status Code
C ID 2-2
AT704 Shipment Status or Appointment Reason Code
O ID 2-2
AT705 Date
C DT 8-8
AT706 Time
C TM 4-8
AT707 Time Code
O ID 2-2
MS1 Equipment, Shipment, or Real Property Location
Optional Max: 1
MS101 City Name
C AN 2-30
MS102 State or Province Code
C ID 2-2
MS103 Country Code
C ID 2-3
MS2 Equipment or Container Owner and Type
Optional Max: 2
MS201 Standard Carrier Alpha Code
C ID 2-4
MS202 Equipment Number
C AN 1-15
MS203 Equipment Description Code
O ID 2-2
N1 Loop Repeat: 5
N1 Party Identification
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N3 Party Location
Optional Max: 2
N301 Address Information
M AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
C ID 2-3
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Sazerac Company (via Blue Yonder) EDI 214

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

Validate
Transform
Route
Monitor
Stacksync transmits 214 Shipment Status updates from your TMS to Sazerac Company (via Blue Yonder) — providing real-time freight visibility without manual status calls or portal updates.

Sazerac Company (via Blue Yonder) EDI 214 FAQ

Common questions about 214 Transportation Carrier Shipment Status Message transactions with Sazerac Company (via Blue Yonder).

What status updates does Sazerac Company (via Blue Yonder) expect in an EDI 214?

Sazerac Company (via Blue Yonder) expects EDI 214 Shipment Status Messages at key milestones: pickup (status code X3), in-transit checkpoints (X1), delivery appointment scheduled (X6), arrived at delivery (X1), and delivered (D1). Some Sazerac Company (via Blue Yonder) programs also require departure from origin, border crossing for international loads, and out-for-delivery notifications. Each 214 includes a timestamp, location, and the shipment reference number linking it to the original 204 tender. Stacksync generates 214 updates automatically from your GPS tracking or TMS milestone events, keeping Sazerac Company (via Blue Yonder)'s visibility platform current without manual status entry.

How frequently should EDI 214 updates be sent to Sazerac Company (via Blue Yonder)?

Most Sazerac Company (via Blue Yonder) programs expect EDI 214 updates at every significant milestone — typically pickup, each major transit point, and delivery. Some high-priority Sazerac Company (via Blue Yonder) lanes require periodic in-transit updates every 4 to 8 hours, regardless of milestone events. The key is that Sazerac Company (via Blue Yonder) should never need to call your dispatch for a status check. Stacksync integrates with your ELD or GPS provider and sends 214 updates automatically based on geofence triggers or scheduled intervals, ensuring Sazerac Company (via Blue Yonder) has continuous visibility without your dispatch team manually generating status messages.

What happens if Sazerac Company (via Blue Yonder) doesn't receive an EDI 214 on time?

Missing or late EDI 214 updates can result in Sazerac Company (via Blue Yonder) chargebacks, reduced carrier scorecard ratings, and loss of preferred carrier status. Sazerac Company (via Blue Yonder) uses 214 data for dock scheduling, inventory planning, and customer notifications — when status updates are missing, it creates operational blind spots. In some Sazerac Company (via Blue Yonder) programs, consecutive 214 failures trigger automatic load retendering to backup carriers. Stacksync monitors 214 delivery and alerts your team if a status update fails to transmit, allowing you to resend before Sazerac Company (via Blue Yonder) escalates the issue.

How does Stacksync automate Sazerac Company (via Blue Yonder) EDI 214 status messages?

Stacksync connects to your TMS, ELD, or GPS tracking system and automatically generates Sazerac Company (via Blue Yonder) 214 messages when shipment events occur. When a driver checks in at pickup, crosses a geofence, or completes delivery, Stacksync captures the event, formats the 214 with the correct status code, location, and timestamp, and transmits it to Sazerac Company (via Blue Yonder)'s EDI network. The platform handles appointment codes, exception reporting (delays, refused deliveries), and proof-of-delivery confirmation. Your drivers continue using their existing tools while Stacksync handles the EDI compliance layer automatically.

Can Sazerac Company (via Blue Yonder) EDI 214 data be used to verify freight invoices?

Yes. The EDI 214 provides an independent record of when pickup and delivery actually occurred, which is essential for auditing freight invoices (EDI 210). If a carrier's 210 invoice claims accessorial charges for detention, the 214 timestamps prove how long the driver waited. If a delivery date on the invoice doesn't match the 214 delivery confirmation, it signals a billing discrepancy. Stacksync cross-references 214 data with 210 invoices automatically, flagging mismatches in dates, locations, and service events for your freight audit review.

Ready to automate Sazerac Company (via Blue Yonder) EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding