# EDIFACT IFTMIN: Transport Instruction

> EDIFACT IFTMIN explained: the shipper's instruction to a carrier or forwarder, BGM 610, NAD parties, GID goods items, a D.96A example and the 204 and 304 map.

<QuickAnswer>
EDIFACT IFTMIN is the UN/EDIFACT instruction message for transport. A shipper sends it to a carrier or freight forwarder to book the movement of one consignment: the parties, pickup and delivery dates, transport mode, goods items, packages and weights. It does the job of the X12 204 load tender for road freight and of the 304 shipping instructions for ocean.
</QuickAnswer>

**IFTMIN is the work order for a shipment.** When a European shipper hands freight to a forwarder or road carrier by EDI, this is usually the message: who is sending, who is receiving, what is moving, how heavy it is, and when it must be collected and delivered. If it is wrong, the driver turns up on the wrong day, with the wrong vehicle, or the consignment is billed to the wrong party.

This guide covers what IFTMIN carries, who sends it and to whom, the directories you will meet, a full example, the segments you will map, and how it compares with the X12 [204 load tender](/guides/edi/204-motor-carrier-load-tender) and [304 shipping instructions](/guides/edi/304-shipping-instructions).

<EDIGuideCTA
  badge="For EDIFACT IFTMIN"
  transactionType="IFTMIN"
  headline="Check a transport instruction before it reaches the carrier"
  body="Paste an IFTMIN into the free EDIFACT inspector to see the parties, goods items and weights, with UNT and UNZ counts checked. Every shipment starts as an order: OrderSync reads orders in any format, from EDI 850s to PDFs and emails, matches customers, items and units, and sends clean data to your ERP."
  secondaryHref="/edifact-inspector"
  secondaryLabel="Try the free EDIFACT inspector"
/>

## What Is an EDIFACT IFTMIN?

**IFTMIN is the UN/EDIFACT Instruction message: "a message from the party issuing an instruction regarding forwarding/transport services for a consignment under conditions agreed, to the party arranging the forwarding and/or transport services."** It belongs to the IFTM family of transport and forwarding messages, alongside IFTMBF (firm booking), IFTMBC (booking confirmation) and [IFTSTA](/guides/edi/edifact-iftsta) (status report).

GS1's EANCOM manual sets out the principles: the instruction results in a transport contract for one consignment, it is "the message from shipper to carrier or forwarder containing the final details of the consignment", and one instruction message should always equal one consignment. GS1 also says it should not be used to instruct the despatch of products; that is the job of INSDES.

Authoritative references for IFTMIN work:

- The [UN/EDIFACT D.96A IFTMIN message](https://service.unece.org/trade/untdid/d96a/trmd/iftmin_c.htm) from UNECE, also laid out group by group on [EDIFACTORY](https://www.edifactory.de/edifact/directory/D96A/message/IFTMIN)
- The [GS1 EANCOM 2002 IFTMIN specification](https://www.gs1.org/sites/default/files/docs/eancom/s3/iftmin.pdf), directory D.01B, with its principles, code lists and a worked example using GLNs and SSCCs
- Each carrier, forwarder and transport platform publishes its own IFTMIN guide, which sets the references, codes and services it accepts

**Who sends it?** The party that orders the transport: a manufacturer or retailer shipping goods, or a forwarder passing an instruction on to a subcontracted carrier.

**Who receives it?** The party arranging the move: a freight forwarder, a road carrier, a parcel or groupage network, or an ocean carrier.

**When is it sent?** Once the consignment is ready to be booked: packed, weighed and with a collection date. Changes and cancellations follow as further IFTMINs with a different message function in `BGM`.

**Why does it matter?** The carrier plans collection, vehicle type and delivery from it, and invoices from it later. Data missing from the IFTMIN becomes a phone call, a failed collection or a freight invoice query.

## Who Uses IFTMIN

| Sector | Sender | Receiver | Typical use |
|---|---|---|---|
| Road and groupage | Shipper | Forwarder or road carrier | Book a collection of pallets or parcels to a consignee |
| Forwarding | Forwarder | Subcontracted haulier | Pass the move on, with the forwarder's own references |
| Retail and consumer goods | Supplier or retailer | Carrier or 3PL | EANCOM IFTMIN with GLNs for parties and SSCCs for pallets |
| Ocean | Shipper, forwarder or NVOCC | Ocean carrier or booking portal | Shipping instructions for the bill of lading, after the booking |
| Automotive | Supplier or OEM logistics | Carrier or logistics provider | Collection instructions against a JIT call-off |

In ocean freight the IFTM messages divide the work the way the X12 300 series does: IFTMBF requests the booking (the [300](/guides/edi/300-reservation-booking-request-ocean)), IFTMBC confirms it (the [301](/guides/edi/301-confirmation-ocean)), and IFTMIN carries the shipping instructions (the [304](/guides/edi/304-shipping-instructions)). Road freight usually skips the booking pair and sends IFTMIN on its own.

## Directories

There is no single directory every transport partner uses:

| Directory | Where you meet it |
|---|---|
| D.96A | Many forwarder and road carrier guides; the example below uses it |
| D.01B | GS1 EANCOM 2002 IFTMIN (subset version EAN004) for retail and consumer goods |
| Later directories (D.99B, D.00B and beyond) | Ocean carriers and booking portals, which publish their own guides |

The segment groups are similar across these directories, but positions, code lists and mandatory segments vary. Build to the guide of the carrier or forwarder you are sending to, and read the version in `UNH` on anything you receive.

## Example: Road Instruction to a Forwarder

The fictional foundry Kestrel Castings books two pallets of brake carriers with the fictional forwarder Alder Freight Forwarding, for collection in the UK on 12 November and delivery to its customer's plant in Germany on 13 November.

<EdifactSample
  title="Road instruction for two pallets"
  description="Forwarding instructions (BGM 610) with collection and delivery dates, control totals, consignor and order references, road main carriage, the three parties and one goods item of two pallets."
  label="UN/EDIFACT D.96A"
  raw="UNA:+.? '
UNB+UNOC:3+KESTRELCAST:ZZZ+ALDERFWD:ZZZ+261111:1530+KCT0000771++IFTMIN'
UNH+1+IFTMIN:D:96A:UN'
BGM+610+KC-TI-26-04412+9'
DTM+137:202611111530:203'
DTM+200:202611121000:203'
DTM+2:202611130800:203'
FTX+DEL+++Deliver to goods-in dock D07. Tail-lift vehicle required'
CNT+7:812:KGM'
CNT+11:2'
RFF+CU:KC-SHP-30991'
RFF+ON:4500087731'
TDT+20++3'
NAD+CZ+++Kestrel Castings Ltd+Unit 4 Foundry Way+Walsall++WS2 9ZZ+GB'
NAD+CN+++Northbrook Axle GmbH+Werkstrasse 12+Hannover++30659+DE'
NAD+FW+++Alder Freight Forwarding Ltd'
GID+1+2:PX'
FTX+AAA+++Machined brake carriers, cast iron'
MEA+AAE+G+KGM:812'
UNT+18+1'
UNZ+1+KCT0000771'"
/>

| Segment | What it says |
|---|---|
| `BGM+610+KC-TI-26-04412+9'` | Forwarding instructions (`610`), instruction number KC-TI-26-04412, original (`9`) |
| `DTM+137` | Message date: 11 November at 15:30 |
| `DTM+200` | Pick-up/collection date and time of cargo: 12 November at 10:00 |
| `DTM+2` | Delivery date and time requested: 13 November at 08:00 |
| `FTX+DEL` | Delivery information in free text |
| `CNT+7:812:KGM'` / `CNT+11:2'` | Total gross weight 812 kg; total number of packages 2 |
| `RFF+CU` / `RFF+ON` | The consignor's shipment reference and the customer's order number |
| `TDT+20++3'` | Main-carriage transport (`20`) by road (`3`) |
| `NAD+CZ` / `CN` / `FW` | Consignor, consignee and freight forwarder |
| `GID+1+2:PX'` | Goods item 1: two pallets (`PX`) |
| `FTX+AAA` | Goods description |
| `MEA+AAE+G+KGM:812'` | Gross weight of the goods item: 812 kg |

The totals in `CNT` must agree with the goods items: two packages and 812 kg here, matching the single `GID` and its `MEA`. Forwarders use them as a check, and a mismatch is a common reason for a rejected instruction.

## IFTMIN Structure at a Glance (D.96A)

| Area | Segment or group | Status | What it holds |
|---|---|---|---|
| Header | `UNH` | M | Message reference and type |
| Header | `BGM` | M | Document code, instruction number, function |
| Header | `CTA`, `COM` | C | Contact for the instruction |
| Header | `DTM` | C | Message, collection and delivery dates |
| Header | `TSR` | C | Transport service requirements |
| Header | `CUX`, `MOA` | C | Currencies and amounts, such as declared value |
| Header | `FTX` | C | Instructions in free text |
| Header | `CNT` | C | Control totals: packages, weight |
| Header | `LOC` group (SG1) | C | Places relevant to the whole consignment |
| Header | `TOD` group (SG2) | C | Terms of delivery |
| Header | `RFF` group (SG3) | C | References: consignor's reference, order numbers |
| Header | `GOR` group (SG4) | C | Customs and other government requirements |
| Header | `CPI` group (SG6) | C | Charge payment instructions |
| Header | `TDT` group (SG8) | C | Transport stage, mode and means, with locations |
| Header | `NAD` group (SG11) | M | Parties: consignor, consignee, carrier, forwarder, delivery party |
| Detail | `GID` group (SG18) | C | Goods items: packages, description, measurements, marks, dangerous goods |
| Detail | `EQD` group (SG37) | C | Equipment such as containers or trailers, with seals |
| Trailer | `UNT` | M | Segment count and message reference |

Statuses are from the UN/EDIFACT D.96A message. Carrier guides make many conditional groups required.

## Key Segments Explained

### BGM: Beginning of Message

```
BGM+610+KC-TI-26-04412+9'
```

| Element | Name | Example | Notes |
|---|---|---|---|
| 1001 | Document name code | `610` | Forwarding instructions. Carrier guides may list other codes for other services |
| 1004 | Document number | `KC-TI-26-04412` | Your instruction number; the carrier quotes it back |
| 1225 | Message function | `9` | Original. GS1 also lists `1` cancellation, `5` replace, `7` duplicate and `31` copy |

### NAD: The Parties

```
NAD+CZ+++Kestrel Castings Ltd+Unit 4 Foundry Way+Walsall++WS2 9ZZ+GB'
```

| Qualifier (3035) | Party |
|---|---|
| `CZ` | Consignor: the party sending the goods |
| `CN` | Consignee: the party the goods are consigned to |
| `CA` | Carrier |
| `FW` | Freight forwarder |
| `DP` | Delivery party, when different from the consignee |

After the qualifier come the party code (with its code list, such as a GLN in EANCOM), then the name and the structured address: street, city, postcode and country. Many carriers want both a code and a full address, because the driver needs the address and the carrier's billing needs the code.

### TDT: Transport Details

```
TDT+20++3'
```

The first element is the transport stage (`20` main carriage); the third is the mode, from UN/ECE Recommendation 19 (`3` road). Pre-carriage and on-carriage, when the instruction covers several legs, each get their own `TDT` group with their own locations and dates.

### GID, MEA and FTX: The Goods

```
GID+1+2:PX'
FTX+AAA+++Machined brake carriers, cast iron'
MEA+AAE+G+KGM:812'
```

`GID` numbers the goods item and gives the number and type of packages, with package types from UN/ECE Recommendation 21 (`PX` pallet, `CT` carton). `FTX+AAA` is the goods description, and `MEA+AAE+G` the gross weight. In EANCOM, each pallet's SSCC goes in a package identification group under the goods item, as `PCI` followed by `GIN+BJ`, the same identifier the [DESADV guide](/guides/edi/edifact-desadv) covers. Dangerous goods go in the `DGS` group under the goods item.

### CNT: Control Totals

```
CNT+7:812:KGM'
CNT+11:2'
```

| Qualifier (6069) | Meaning |
|---|---|
| `7` | Total gross weight |
| `11` | Total number of packages |

## IFTMIN vs the X12 204 and 304

| Data | EDIFACT IFTMIN | X12 204 (road load tender) | X12 304 (ocean shipping instructions) |
|---|---|---|---|
| Who sends it | Shipper or forwarder | Shipper, broker or 3PL | Shipper, forwarder or NVOCC |
| Who receives it | Forwarder or carrier | Truckload carrier | Ocean carrier |
| Instruction number | `BGM` | `B2` shipment ID | `B2` and booking references |
| Parties | `NAD` group | `N1` loops at stops | `N1` loops |
| Dates | `DTM` (`200` collection, `2` delivery) | `G62` at each stop | `R4` port details, with dates per the carrier's guide |
| Mode and legs | `TDT` groups | Implied: motor carrier | `R4` ports, vessel and voyage |
| Goods | `GID`, `FTX`, `MEA` | `L5`, `L3` | `L0`, `L5`, `L3` |
| Equipment | `EQD` | `N7` | `N7` |
| Answer | Carrier guide sets it | [990](/guides/edi/990-response-to-load-tender) accept or decline | Bill of lading data in the [310](/guides/edi/310-freight-receipt-and-invoice-ocean) |

The biggest difference from the 204 is the stop model. A 204 lists every pickup and delivery stop in sequence for one truck. An IFTMIN describes one consignment from consignor to consignee and leaves the routing to the forwarder or carrier.

## Where IFTMIN Sits in the Flow

| Step | Message | Direction | X12 equivalent |
|---|---|---|---|
| 1 | [ORDERS](/guides/edi/edifact-orders) | Buyer to supplier | [850](/guides/edi/850-purchase-order) |
| 2 | [DESADV](/guides/edi/edifact-desadv) | Supplier to buyer | [856](/guides/edi/856-ship-notice) |
| 3 | **IFTMIN** (after IFTMBF and IFTMBC in ocean) | Shipper to carrier or forwarder | [204](/guides/edi/204-motor-carrier-load-tender) or [304](/guides/edi/304-shipping-instructions) |
| 4 | [IFTSTA](/guides/edi/edifact-iftsta) status reports | Carrier to shipper | [214](/guides/edi/214-transportation-carrier-shipment-status) or [315](/guides/edi/315-status-details-ocean) |
| 5 | Freight invoice | Carrier to payer | [210](/guides/edi/210-motor-carrier-freight-invoice) or 310 |

The DESADV goes to the customer and the IFTMIN goes to the carrier, but they describe the same pallets. Build both from the same despatch record so weights, package counts and SSCCs agree.

## Common IFTMIN Errors and How to Prevent Them

| Problem | What happens | Prevention |
|---|---|---|
| `CNT` totals disagree with the goods items | Instruction rejected or queried | Calculate totals from the `GID` and `MEA` values in the same message |
| Consignor or consignee address incomplete | Failed collection or delivery | Send structured addresses as well as party codes |
| Collection date in the past or missing | No vehicle planned | Validate dates before sending; send changes as a replacement |
| Wrong mode or service | Wrong vehicle, wrong price | Map services from the carrier's code list, not free text |
| Several consignments in one IFTMIN | Carrier merges or drops them | One IFTMIN per consignment, as GS1 specifies |
| Weights in the wrong unit | Overweight vehicle or billing dispute | Always send the unit (`KGM`) with each weight |
| Change sent as a new original | Duplicate collection booked | Use the replace or cancel function the carrier supports |

## IFTMIN Implementation Checklist

1. **Get the carrier's or forwarder's guide**: directory, mandatory segments, services and codes.
2. **Agree party identification**: GLNs, customer account numbers or the carrier's own codes.
3. **Agree references** the carrier must quote back on status reports and invoices.
4. **Map package types and services** to the carrier's code lists.
5. **Build totals from the goods items** so `CNT` always agrees.
6. **Decide how changes and cancellations are sent**, and test both.
7. **Test with real consignments**: a single pallet, a multi-item load, and dangerous goods if you ship them.
8. **Set up status reporting** so the carrier's [IFTSTA](/guides/edi/edifact-iftsta) messages update the same shipment record.

## Where OrderSync Fits

Every transport instruction starts with an order. The consignee, the order numbers, the quantities and the delivery date on an IFTMIN all come from purchase orders someone had to get into your ERP, whether they arrived as EDI, a PDF, an email or a spreadsheet. OrderSync reads those inbound orders in any format, matches customers, items and units to your catalog, and outputs clean ERP data or valid X12, so your shipping and transport systems start from accurate orders.

Paste any IFTMIN into the [free EDIFACT inspector](/edifact-inspector) to see it parsed segment by segment, use the [free EDI inspector](/edi-inspector) for X12 204s and 304s, or [book a 15-minute walkthrough](/book-call) to see your own orders processed.

## Frequently Asked Questions

<div className="not-prose">

### What is the X12 equivalent of IFTMIN?

For road freight, the 204 motor carrier load tender. For ocean freight, the 304 shipping instructions. IFTMIN covers both jobs: an instruction to a carrier or forwarder to move one consignment.

### What does BGM+610 mean?

`610` is the UN/EDIFACT document code for forwarding instructions. The second element is your instruction number and the third is the message function, usually `9` for an original.

### Can one IFTMIN contain several consignments?

GS1 says one transport instruction message should always equal one consignment. A consignment can contain several goods items and packages. To book several consignments, send several messages, which can travel in one interchange.

### What is the difference between IFTMIN and IFTMBF?

IFTMBF is a firm booking request, mostly used in ocean freight to reserve space before the cargo details are final; the carrier confirms it with IFTMBC. IFTMIN carries the final instructions for the consignment, which GS1 describes as the message that results in the transport contract.

### Does IFTMIN replace the DESADV?

No. DESADV tells your customer what is coming and how it is packed. IFTMIN tells the carrier what to collect and deliver. They describe the same pallets to different parties, so build both from the same despatch data.

### What reply should I expect to an IFTMIN?

It depends on the carrier. Some confirm with an acknowledgement or an application response, and most report progress with IFTSTA status messages. The carrier's guide says which messages it returns and what they mean.

### Which directory should I use for IFTMIN?

The one your carrier or forwarder specifies. Many road and forwarding guides use D.96A, EANCOM 2002 uses D.01B, and ocean carriers often use later directories. The segment groups are similar, but codes and mandatory segments differ.

</div>

## Related guides

- **[EDIFACT IFTSTA](/guides/edi/edifact-iftsta)**: the status reports that follow
- **[EDI 204 load tender](/guides/edi/204-motor-carrier-load-tender)** and **[EDI 990](/guides/edi/990-response-to-load-tender)**: the X12 road tender cycle
- **[EDI 304 shipping instructions](/guides/edi/304-shipping-instructions)** and **[EDI 300 booking request](/guides/edi/300-reservation-booking-request-ocean)**: the X12 ocean equivalents
- **[EDIFACT DESADV](/guides/edi/edifact-desadv)**: the despatch advice for the same goods
- **[EDIFACT explained](/guides/edi/edifact)** and **[EDIFACT message types](/guides/edi/edifact-message-types)**: syntax and the full catalogue

## Sources

- [UN/EDIFACT D.96A IFTMIN message](https://service.unece.org/trade/untdid/d96a/trmd/iftmin_c.htm), UNECE: definition and structure
- [IFTMIN in directory D.96A](https://www.edifactory.de/edifact/directory/D96A/message/IFTMIN), EDIFACTORY: segment groups
- [EANCOM 2002 S3 IFTMIN instruction message](https://www.gs1.org/sites/default/files/docs/eancom/s3/iftmin.pdf), GS1: principles, code lists and example
- [EANCOM 2002 Syntax 3](https://www.gs1.org/edi/eancom/s3), GS1

Check any IFTMIN or IFTSTA in the free [EDIFACT inspector](/edifact-inspector).