EDIFACT message guide · Transport

IFTSTQ International multimodal status request

The UN/EDIFACT message used to request a transport status report (IFTSTA) for a consignment.

Sent by
Shipper, consignee or forwarder
Received by
Carrier or forwarder
Standard
UN/EDIFACT · Batch message
X12 equivalent
313 Shipment Status Inquiry (Ocean)

What is the EDIFACT IFTSTQ message?

IFTSTQ is the UN/EDIFACT international multimodal status request message. The directory defines it as a message to request an international multimodal status report (IFTSTA) giving details of the transport status, or a change in transport status, between agreed parties.

It identifies the consignments or equipment to report on, by references such as booking, bill of lading or container numbers. Many parties subscribe to status events instead, but a request is useful when an expected event is missing. The carrier answers with one or more status reports.

How the EDIFACT IFTSTQ message worksDiagram of the UN/EDIFACT IFTSTQ International multimodal status request message. Shipper, consignee or forwarder sends it to carrier or forwarder. It usually starts the exchange. It is usually followed by IFTSTA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTSTQ message worksInternational multimodal status request: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeIFTSTQSENDERShipper, consignee orforwarderRECEIVERCarrier or forwarderCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTSTAInternationalmultimodal statusreport2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage IFTSTQUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFNADCNIBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for IFTSTQ. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT IFTSTQ message worksDiagram of the UN/EDIFACT IFTSTQ International multimodal status request message. Shipper, consignee or forwarder sends it to carrier or forwarder. It usually starts the exchange. It is usually followed by IFTSTA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 3 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTSTQmessage worksInternational multimodal status request: whosends it, where it fits and what the directorymarks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeIFTSTQSENDERShipper,consignee orforwarderRECEIVERCarrier orforwarderCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTSTAInternational multimodal statusreport2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message IFTSTQ (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 3 conditional groups, starting with:RFFNADCNIBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for IFTSTQ.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends IFTSTQ, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around IFTSTQ and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Asking for the current status of a consignment
  • Checking shipments with missing events
  • Requesting status for specific containers

Where it fits in the message flow

This message IFTSTQ International multimodal status request

Structure

Mandatory segments in IFTSTQ (directory D.21A)

In UN/EDIFACT directory D.21A, the IFTSTQ message has 25 segment positions arranged in 8 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • UNT

Practical example

IFTSTQ in practice

A consignee notices that no discharge event has arrived for a container whose vessel arrived two days ago. Its visibility platform sends the carrier an IFTSTQ for the container number. The carrier answers with an IFTSTA showing the container is discharged and held for inspection, and the consignee alerts its broker.

Implementation

Implementation considerations for IFTSTQ

  • Use the references the carrier indexes, such as container or bill of lading numbers.
  • Use requests for exceptions rather than polling every shipment.
  • Match each IFTSTA response to the request.
  • Check which parties the carrier authorizes to request status.

Need help with IFTSTQ?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.