X12
Outbound

Blume Global X12 214 Transportation Carrier Shipment Status Message

Blume Global
The EDI 214 provides real-time shipment status updates to Blume Global. Carriers transmit pickup confirmations, in-transit milestones, and delivery confirmations as freight moves through the network.
15segments
3loops
5mandatory

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 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
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
B1002 Shipment Identification Number
O AN 1-30
B1003 Standard Carrier Alpha Code
M ID 2-4
L11 Business Instructions and Reference Number
Optional Max: 300
L1101 Reference Identification
C AN 1-30
L1102 Reference Identification Qualifier
C ID 2-3
K1 Remarks
Optional Max: 10
K101 Free-Form Message
M AN 1-30
K102 Free-Form Message
O AN 1-30
N1 Loop Repeat: 10
N1 Name
Optional Max: 1
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
N4 Geographic Location
Optional Max: 1
N405 Location Qualifier
C ID 1-2
N406 Location Identifier
O AN 1-30
G61 Contact
Optional Max: 1
G6101 Contact Function Code
M ID 2-2
G6102 Name
M AN 1-60
G6103 Communication Number Qualifier
C ID 2-2
G6104 Communication Number
C AN 1-80
G6105 Contact Inquiry Reference
O AN 1-20
G62 Date/Time
Optional Max: 1
G6201 Date Qualifier
C ID 2-2
G6202 Date
C DT 8-8
G6203 Time Qualifier
C ID 1-2
G6204 Time
C TM 4-8
G6205 Time Code
O ID 2-2
L11 Business Instructions and Reference Number
Optional Max: 300
L1101 Reference Identification
C AN 1-30
L1102 Reference Identification Qualifier
C ID 2-3
LX Loop Repeat: 999,999
LX Assigned Number
Optional Max: 1
LX01 Assigned Number
M N0 1-6
AT7 Loop Repeat: 10
AT7 Shipment Status Details
Optional Max: 1
AT701 Shipment Status Code
C ID 2-2
AT703 Shipment Appointment Status Code
C ID 2-2
AT705 Date
C DT 8-8
AT706 Time
C TM 4-8
MS2 Equipment or Container Owner and Type
Optional Max: 1
MS201 Standard Carrier Alpha Code
C ID 2-4
MS202 Equipment Number
C AN 1-10
MS204 Equipment Number Check Digit
O N0 1-1
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 Blume Global 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 Blume Global — providing real-time freight visibility without manual status calls or portal updates.

Blume Global EDI 214 FAQ

Common questions about 214 Transportation Carrier Shipment Status Message transactions with Blume Global.

How long does it take to set up Blume Global EDI with Stacksync?

Most suppliers are fully connected and processing live Blume Global EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Blume Global?

No. Stacksync handles the entire EDI transport layer. We connect directly to Blume Global's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Blume Global compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Blume Global?

Stacksync supports all EDI document types required by Blume Global — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Blume Global EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Blume Global's EDI network and your system in real time.

What happens when Blume Global updates their EDI specifications?

Stacksync monitors Blume Global's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.