Instruction Message
UN/EDIFACT IFTMIN conveys transport instructions from a shipper or forwarder to a carrier, specifying what needs to be moved, how, and by when.
In this guide
EDIFACT IFTMIN moves from Shipper / Freight Forwarder to Carrier (Shipper → Carrier) via AS2, SFTP, VAN. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How EDIFACT IFTMIN Works
Sender
Shipper / Freight Forwarder
Receiver
Carrier
Direction
Shipper → Carrier
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Logistics & Fulfillment
Sender — Shipper / Freight Forwarder
EDI Transmission
IFTMIN
Instruction Message
UN/EDIFACT D.96A / D.01B
Receiver — Carrier
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT IFTMIN workflow. Steps: Finalize Booking, Build IFTMIN, Send to Carrier, Carrier Receives Instruction, Plan Capacity & Routing, Report Status. Transmitted from Shipper / Freight Forwarder to Carrier via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
Overview
Formalizes freight booking and transport instructions between shippers, freight forwarders, and carriers in international logistics.
Sender
Shipper / Freight Forwarder
Receiver
Carrier
Direction
Shipper → Carrier
Standard / Version
UN/EDIFACT D.96A / D.01B
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| BGM | Beginning of Message | Instruction document number and type. |
| TDT | Details of Transport | Mode of transport and carrier identification. |
| LOC | Place/Location Identification | Origin and destination locations. |
| GID | Goods Item Details | Cargo description and packaging. |
Interactive example
Click any segment below to see its business meaning.
UNH
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
UNH+1+IFTMIN:D:96A:UN'
BGM+610+INS-4471+9'
TDT+20+++30+FEDX'
LOC+9+COLUMBUS:139:6'
LOC+11+CLEVELAND:139:6'
GID+1+4:CT'
UNS+S'
UNT+7+1'Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| TMS Load Record | load.origin_city | LOC+9 (Place/Location) |
| TMS Load Record | load.carrier_code | TDT/8212 (Carrier Identification) |
Validation rules
- LOC segments must include both an origin (qualifier 9) and destination (qualifier 11).
- TDT transport mode code must be consistent with the equipment described in GID.
Common errors & troubleshooting
Carrier system can't plan the route
Cause: Origin/destination LOC codes used free text instead of standardized UN/LOCODEs.
Fix: Map internal location names to UN/LOCODE identifiers before transmission.
Frequently asked questions
Yes — the transport mode code in TDT changes (e.g., 1 = Maritime) but the same message structure applies across road, rail, air, and ocean instructions.
Still have questions about IFTMIN?
Ask EDI AI →