EDIFACT IFTMIN — Instruction to Despatch / Transport
IFTMIN carries pickup and delivery locations, commodity, weights, service level, and references the commercial shipment.
✦ What It Does
NAD identifies shipper, consignee, and carrier; TDT and EQD describe mode and equipment needs.
Used in European road freight and multimodal where EDIFACT is the carrier integration standard.
May pair with IFTSTA milestones until proof of delivery.
⚡ When It's Used
- Shipper tenders load to primary carrier after ORDERS release.
- 3PL tenders linehaul on behalf of shipper.
- Inbound import container drayage instructions.
- Emergency reroute after disruption.
- Seasonal peak supplemental capacity buys.
Who Uses EDIFACT IFTMIN
European retail & brands
Common in EDIFACT-first programs where instruction to despatch / transport 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
Instruction type and shipment ID.
NAD
Shipper, consignee, notify, and carrier parties.
GID / GDS
Goods description and totals.
TDT / DTM
Mode, means, pickup and delivery windows.
Related Messages
Need Help with EDIFACT IFTMIN?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert