The LOC segment identifies a specific place. Qualifier 1=place of despatch, 7=place of delivery, 11=place of loading, 83=freight and charges paid to. Used in DESADV for despatch and delivery locations, and in ORDERS for line-level delivery locations in multi-site orders.
LOCHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
LOC+7+SYD-DC::92'Place of delivery: SYD-DC.
| 1 | Location type | 7Place of delivery |
| 2.1 | Location: ID | SYD-DC |
| 2.3 | Location: Agency | 92Assigned by buyer |
{
"locations": {
"placeOfDelivery": "SYD-DC"
}
}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 | Location type | 1.1 Code |
| 2 | Location | 2.1 ID, 2.2 Code list, 2.3 Agency |
| Code | Meaning |
|---|---|
7 | Place of delivery |
9 | Place of loading |
11 | Place of discharge |
18 | Warehouse |
20 | Final destination |
| Code | Meaning |
|---|---|
9 | GS1 |
16 | DUNS |
91 | Assigned by supplier |
92 | Assigned by buyer |
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 LOC in it? The explainer breaks down every segment and runs in your browser.
Explain my message