The FTX segment carries free-form text that does not fit into structured data fields. Common uses include delivery instructions, special handling notes, and product descriptions that exceed the IMD segment capacity. The qualifier identifies the purpose: DEL=delivery instructions, AAI=general information, PUR=purchasing information.
FTXHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
FTX+DEL+++DELIVER TO LOADING DOCK B ONLY'Delivery information: DELIVER TO LOADING DOCK B ONLY.
| 1 | Subject | DELDelivery information |
| 4 | Text | DELIVER TO LOADING DOCK B ONLY |
{
"notes": [
{
"subject": "deliveryInformation",
"text": "DELIVER TO LOADING DOCK B ONLY"
}
]
}Example shape. In production the field names and structure follow your own API contract.
Elements are separated by + and their parts by :. Positions match the explainer, so 2.3 is the third part of the second element.
| Position | Element | Parts |
|---|---|---|
| 1 | Subject | 1.1 Code |
| 2 | Function | Single value |
| 3 | Text reference | Single value |
| 4 | Text | 4.1 Line 1, 4.2 Line 2, 4.3 Line 3, 4.4 Line 4, 4.5 Line 5 |
| 5 | Language | Single value |
| Code | Meaning |
|---|---|
AAI | General information |
AAB | Payment terms |
DEL | Delivery information |
PUR | Purchasing information |
PKG | Packaging information |
REG | Regulatory information |
SIN | Special instructions |
ZZZ | Mutually agreed |
Common EANCOM and UN/EDIFACT values. Your trading partner's implementation guide is the final word on which codes they send.
Have a real message with FTX in it? The explainer breaks down every segment and runs in your browser.
Explain my message