EDIFACT IFTSTA — Transport Status
IFTSTA reports events: accepted, pickup, in-transit, exception, proof of delivery, with timestamps and location where required.
✦ What It Does
STS segments carry status codes; LOC and DTM anchor place and time for each event.
Omnichannel and retail inbound teams track IFTSTA against appointment scheduling systems.
High-volume feeds require idempotent processing and deduplication by control reference.
⚡ When It's Used
- Carrier TMS emits status as trailer departs geofence.
- Exception codes for delay, refusal, or rework.
- POD capture closes the transportation service.
- Multileg status for air-sea combinations.
- Visibility platform aggregates IFTSTA to customer portal.
Who Uses EDIFACT IFTSTA
European retail & brands
Common in EDIFACT-first programs where transport status flows between HQ, DCs, and suppliers across the EU and APAC.
Global manufacturers
Automotive, industrial, and CPG companies standardize on EDIFACT for plants and suppliers outside North America.
3PLs & carriers
Logistics service providers consume or produce the message when the contract mandates UN/EDIFACT syntax and directories.
Key Segments & Constructs
EDIFACT uses a hierarchical structure: UNH (message header) opens the transaction; BGM (beginning of message) carries the document name and reference; party data uses NAD; lines often use LIN with QTY, PRI, and MOA. Exact segment requirements depend on the message directory (D.96A, etc.) and your trading partner's implementation guide.
BGM
Status message function and document chain.
RFF
Shipment, order, and equipment references.
STS / DTM / LOC
Status code with time and place.
EQD
Equipment ID such as trailer or container number.
Related Messages
Need Help with EDIFACT IFTSTA?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert