IFTSTA Tracking

Edifact IFTSTA supported versions

Following IFTSTA versions are supported:

D01A
D01B
D01C
D94B
D96A
D99B

Multiple events can be included in 1 message. The IFTSTA can contain many details, the relevant details for our shippers are:

Event types & reason: what event happened
Event reference: link the event to the shippers shipment
Event date: when it happened
Event location: where it happened

Event types & reason

This is mandatory to provide!

Although officially not all versions use the same list of tracking codes, in practice we noticed that many carriers provide their own interpretation of the codes.

Therefore the carrier can provide Viya with the codes he/she will forward in the STS section inside the CNI loop.

Fields used:

Event Type: 010 - 9015: Status Category, coded
Event Reason: 030 - 9013: Status reason description code

Example below shows:

Event Type = 167
Event Reason = 310

UNA:+.? '
UNB+UNOA:4+542059315:22+VIYA+250313:1836+736894'
UNH+73689400001+IFTSTA:D:01B'
BGM+77+2992029823883873689400001+9'
DTM+137:20250313:102'
NAD+MS+54205031500028::9'
NAD+MR+3011343064007::9'
CNI+1+131637258'
LOC+89+:::G GENNEVILLIERS'
STS+1+167+310:::CONFORME'
RFF+CU:131637258'
RFF+AAS:131637258'
DTM+137:202503131822:203'
UNT+12+73689400001'
UNZ+1+736894'

References

The mandatory reference is the one that ties the event to the shipper’s shipment.

Any other references are allowed as additional context.

Following options exist to provide the link to the shipment, it should be one option for all flows supported by the carrier for a specific shipper.

Option 1: RFF+AWB in header

Example reference: 614560156 in below snippet:

UNA:+.? '
UNB+UNOA:4+542059315:22+VIYA+250313:1836+736894'
UNH+73689400001+IFTSTA:D:01B'
BGM+77+2992029823883873689400001+9'
DTM+137:20250313:102'
NAD+MS+54205031500028::9'
NAD+MR+3011343064007::9'
RFF+AWB+614560156'
CNI+1+131637258'
....

Option 2: RFF in CNI.STS loop

Use one of the following qualifiers: ACL, CN, CR, CU, ON, SRN, UCN.

Note: For all flows for the shipper, the same qualifier should be used

Example reference: 614560156 in below snippet using the CU qualifier:

UNA:+.? '
UNB+UNOA:4+542059315:22+VIYA+250313:1836+736894'
UNH+73689400001+IFTSTA:D:01B'
BGM+77+2992029823883873689400001+9'
DTM+137:20250313:102'
NAD+MS+54205031500028::9'
NAD+MR+3011343064007::9'
CNI+1+131637258'
LOC+89+:::G GENNEVILLIERS'
STS+1+167+310:::CONFORME'
RFF+CU:614560156'
RFF+AAS:131637258'
DTM+137:202503131822:203'
UNT+12+73689400001'
UNZ+1+736894'

Option 3: CNI document message number

Example reference: 614560156:

UNA:+.? '
UNB+UNOA:4+542059315:22+VIYA+250313:1836+736894'
UNH+73689400001+IFTSTA:D:01B'
BGM+77+2992029823883873689400001+9'
DTM+137:20250313:102'
NAD+MS+54205031500028::9'
NAD+MR+3011343064007::9'
CNI+1+614560156'
LOC+89+:::G GENNEVILLIERS'
STS+1+167+310:::CONFORME'
RFF+CU:ABCDE'
RFF+AAS:131637258'
DTM+137:202503131822:203'
UNT+12+73689400001'
UNZ+1+736894'

Event date

The event date is expected in the DTM segment inside the CNI.STS loop.

The actual event date

Mandatory for each event, use qualifier:

137: Date/time of event

Expected delivery date

If a delivery appointment is made for a specific delivery date or an ETA is available, use one of the following appointment qualifiers:

63: Delivery date/time, latest
64: Delivery date/time, earliest
67: Delivery date/time, current schedule
69: Delivery date/time, promised for
71: Delivery date/time, requested for (after and including)
72: Delivery date/time, promised for (after and including)
73: Guarantee period
74: Delivery date/time, requested for (prior to and including)
75: Delivery date/time, promised for (prior to and including)
76: Delivery date/time, scheduled for
79: Shipment date/time, promised for
231: Arrival date/time, earliest
232: Arrival date/time, scheduled
234: Collection date/time, earliest
265: Due date
806: Shipment date/time, expected

Example event

Event happened on 15-oct-2025 17:15, an appointment was made for delivery on 17-oct-2025 14:25.

UNA:+.? '
UNB+UNOA:4+542059315:22+VIYA+250313:1836+736894'
UNH+73689400001+IFTSTA:D:01B'
BGM+77+2992029823883873689400001+9'
DTM+137:20250313:102'
NAD+MS+54205031500028::9'
NAD+MR+3011343064007::9'
CNI+1+614560156'
LOC+89+:::G GENNEVILLIERS'
STS+1+167+310:::CONFORME'
RFF+CU:ABCDE'
RFF+AAS:131637258'
DTM+137:202510151715:203'
DTM+76:202510171425:203'
UNT+12+73689400001'
UNZ+1+736894'

Event location

Optionally the event location can be provided in the NAD segment inside the CNI.STS loop, use Party qualifier CS

Example: where the event location is:

Name of location: CARRIER HUB NAME
Streetname + number: STREETNAME 6
City: CITYNAME
Postcode: POSTALCODE
Countrycode: NL

UNA:+.? '
UNB+UNOA:1+SENDER:ZZ+VIYA+250313:0734+3205++IFTSTA'
UNH+320500001+IFTSTA:D:01A:UN'
BGM+23+201001985861387743OS'
NAD+MS+54205031500028::9'
NAD+MR+3011343064007::9'
RFF+POR:61387743'
RFF+AWB:61387743'
RFF+ADE:2010019858'
CNI+1'
STS+1+301+000'
NAD+CS+++CARRIER HUB NAME+STREETNAME 6+CITYNAME++POSTALCODE+NL'
LOC+175+BQH::3:DARTFORD+GB'
TDT+30+1+++CARRIERCODE'
DTM+137:202503131139:203'
EQD+AA'
MEA+ABR+AAD+KGM:6'
GID+1+1:CTN'
UNT+16+320500001'
UNZ+1+3205'

Any extra text relevant for user

If there are specific instructions/exception messages that could be usefull for the shipper, provide them in the FTX segment in CNT.STS loop. The qualifier used within FTX is irrelevant.

Example Consol closed in FTX segment:

UNA:+.? '
UNB+UNOC:3+SENDERX+VIYA+250313:1249+105771'
UNH+10577100001+IFTSTA:D:01B:UN'
BGM+77+8IK9016+9'
DTM+137:202503131142:203'
NAD+CZ+CH3ME003'
CNI+1+10371973'
STS++15:::Consolidated'
RFF+CU:56000736715339400'
RFF+BH:8IK9016'
RFF+AF:N08506'
RFF+BM:506-12009314'
DTM+137:202503090512:203'
DTM+133:202503101600:203'
DTM+132:202503161500:203'
FTX+ACB+++Consol closed'
NAD+AP+++SHIPPER COMPANY'
LOC+172+USDFW:::DALLAS-FORT WORTH INT APT'
GID+1+2:CBX'
UNT+18+10577100001'
UNZ+1+105771'