The COM segment provides a communication number for the contact named in the preceding CTA segment. The qualifier indicates the channel: EM=email, TE=telephone, FX=fax, TL=telex. A NAD group can have multiple COM segments for different channels.
COMHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
COM+jane@supplier.com:EM'Email: jane@supplier.com.
| 1.1 | Contact: Number or address | jane@supplier.com |
| 1.2 | Contact: Channel | EMEmail |
{
"contacts": [
{
"email": "jane@supplier.com"
}
]
}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 | Contact | 1.1 Number or address, 1.2 Channel |
| Code | Meaning |
|---|---|
TE | Phone |
EM | |
FX | Fax |
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 COM in it? The explainer breaks down every segment and runs in your browser.
Explain my message