IFTSTA, Explained: The EDIFACT Status Message
What the EDIFACT IFTSTA message is, how carriers use it for shipment status updates, and how it differs from IFTMIN and tracking webhooks.
What Is IFTSTA?
IFTSTA is the UN/EDIFACT message carriers use to report the status of a shipment back to the shipper or forwarder over EDI: booked, collected, in transit, held at customs, delivered. The official name is the International multimodal status report message, and it's the EDIFACT message used to report the status of a transport operation, providing tracking events and milestone updates throughout the shipment lifecycle, communicating the current status of a shipment as it moves through the transport chain. If your carrier still runs EDI for tracking rather than a REST API, IFTSTA is almost certainly the message sitting behind those updates.
It's not tied to one transport mode either. The message supports all transport modes and can track consignments, containers, transport equipment, and individual goods items. That's why you'll see it used by deep-sea carriers, rail/intermodal operators and European road freight networks alike, even though the segment content looks slightly different depending on who's sending it.
IFTSTA vs IFTMIN: Two Messages, Opposite Directions
People mix these up because they're part of the same conversation, just running in opposite directions. IFTMIN is the instruction message you send to the carrier, telling them to move a consignment. IFTSTA is what comes back, telling you what actually happened to it.
| Message | Direction | Purpose | Typical trigger |
|---|---|---|---|
| IFTMIN | Shipper/forwarder → carrier | Booking instruction / transport order | New shipment created in TMS/ERP |
| IFTSTA | Carrier → shipper/forwarder | Status report / tracking milestone | Scan event, hub handover, delivery, exception |
If you've read our earlier piece on migrating DPD's IFTMIN flows to REST, think of IFTSTA as its mirror image. One tells the carrier what to do. The other tells you what they did with it, and when, and where.
IFTSTA vs a Tracking Webhook
Both do the same job: tell your system that something happened to a shipment. The difference is plumbing. A webhook fires an HTTPS POST with a JSON payload the moment a scan event is recorded. IFTSTA is a file, typically delivered over AS2, a VAN, or SFTP, and it often carries several status events batched into one message rather than one event per message.
This isn't a legacy-vs-modern split that cleanly maps to "small carriers vs big carriers." Parcel networks like DHL, UPS and FedEx have largely moved their tracking to pure API/webhook delivery. But a lot of European LTL and FTL networks, plus deep-sea and rail/intermodal forwarders, still run IFTSTA as their primary or only tracking channel, partly because their underlying transport order process is still EDIFACT-based end to end. Ripping out IFTSTA without replacing the IFTMIN side first just breaks the loop.
This is exactly the kind of plumbing that TMS platforms try to abstract away from you. Cargoson normalizes both legacy IFTSTA feeds and modern webhook tracking into one status stream, and you'll see the same ambition from nShift, Shipmondo and ShippyPro. The pitch is the same across all of them: you shouldn't have to know or care whether a given carrier's tracking event arrived as a batched EDIFACT segment or a JSON webhook.
How an IFTSTA Message Is Actually Structured
Strip away the EDIFACT syntax and an IFTSTA message is built from a handful of segments doing specific jobs:
- BGM (Beginning of Message): status report number and type, and identifies which consignment the report covers.
- NAD: identifies the parties involved, carrier, shipper, consignee, so the receiving system knows who the status applies to.
- STS (Status): the actual event, status event code (e.g., collected, in transit, delivered, held at customs), plus a reason code when something's gone wrong.
- DTM: the date/time the event occurred, which is not the same as when the message was transmitted. Don't assume otherwise or your SLAs will look wrong.
- LOC: location where the status event occurred.
That sounds tidy until you remember EDIFACT has multiple sub-releases in active use. Carriers run different versions, D96B, D00B, D09A, D21A among them, and the segment groups and qualifiers shift slightly between releases. A status code that means "booking confirmed" under one carrier's D96B implementation can carry a different reason code structure under another carrier's D09A setup. If you're mapping more than two or three EDI tracking partners, you will hit this, and it's the single biggest source of silent bugs in IFTSTA parsing. Nobody throws an error, the data just means something subtly different than you assumed.
Worked Example: A Pallet Shipment Through a European LTL Network
Picture a full pallet load moving through a network with one pickup, one hub transfer, and a final delivery. Over EDI, your TMS would typically receive a chain of IFTSTA messages, not one. A realistic sequence looks like this:
- Booking confirmed: BGM identifies the consignment, STS reports the carrier has accepted it.
- Collected: STS with a collection code, DTM for the pickup timestamp, LOC for the origin depot.
- In transit / hub scan: a second IFTSTA, or a second STS segment group within the same message, showing the consignment arriving at an intermediate hub.
- Exception: if customs or a damage check holds the shipment, you get a status update carrying an exception reason code. When a shipment is delayed, damaged, or held, the IFTSTA with an exception status code triggers alerts in the shipper's system for proactive management.
- Delivered: the closing message. The final IFTSTA with "delivered" status includes the delivery date/time, signatory name, and POD reference, serving as electronic confirmation of delivery.
This pattern of a status stream, rather than one tidy status update, is exactly why TMS platforms like Transporeon, MercuryGate and Descartes build dedicated parsing layers for IFTSTA, and why Cargoson's approach of normalizing the stream into one consistent event feed matters in practice: your downstream order-tracking screen shouldn't have to know whether it's reading five EDIFACT messages or five webhook calls.
Common Problems When You Implement IFTSTA
Three things catch IT teams out repeatedly:
- Status-code drift between carriers. The same STS code can mean different things depending on the carrier's EDIFACT sub-release. You need a per-carrier mapping table, not a single global lookup, or your "delivered" dashboard will quietly lie to you.
- Volume and ordering. One shipment can generate many IFTSTA events across its lifecycle, arriving out of order if network latency or batching timing varies. You need dedupe and sequencing logic, something a single webhook call rarely requires.
- Connectivity setup before the first message ever lands. Carriers typically require AS2 certificate exchange, VAN mailbox setup, or SFTP credentialing before any IFTSTA will flow, and this partner-specific setup work has to happen before testing can even start.
FAQ
What does IFTSTA stand for?
International Forwarding and Transport Status (report). The formal UN/EDIFACT name is the International multimodal status report message.
Is IFTSTA still used, or has it been replaced by APIs?
Both exist in parallel today. Parcel carriers have largely moved to webhook/API tracking, but many European LTL/FTL networks, rail and ocean forwarders still run IFTSTA as their primary status feed.
What's the difference between IFTSTA and IFTMIN?
IFTMIN is the outbound booking instruction you send to the carrier. IFTSTA is the inbound status report the carrier sends back. Same transport chain, opposite direction.
Do I need a VAN to receive IFTSTA messages?
Not necessarily. You can receive it directly over AS2 or SFTP if the carrier supports it, though many shippers running multiple EDI carriers still use a VAN to avoid managing separate connections with each one.
Can IFTSTA and webhook tracking run side by side in one TMS?
Yes, and for most mid-to-large shippers with a mixed carrier base, this is the normal setup rather than the exception. The TMS or connectivity layer just needs to normalize both into one internal event model.