The LIN segment begins a line item group and carries the line number and product identifier. Element 1 is the line number (sequential, starting at 1). Element 3 is a composite containing the product ID and its type code. Each LIN is followed by PIA, IMD, QTY, PRI, MOA, TAX, and other segments that describe the line.
LINHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
LIN+1++9312345678901:EN'Line 1: item 9312345678901 (GTIN barcode).
| 1 | Line number | 1 |
| 3.1 | Item: Number | 9312345678901 |
| 3.2 | Item: Number type | ENGTIN barcode |
{
"lines": [
{
"lineNumber": 1,
"gtin": "9312345678901"
}
]
}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 | Line number | Single value |
| 2 | Action | 2.1 Code |
| 3 | Item | 3.1 Number, 3.2 Number type |
| 4 | Sub-line | Single value |
| 5 | Configuration level | Single value |
| Code | Meaning |
|---|---|
1 | Added |
3 | Changed |
5 | Accepted without amendment |
7 | Not accepted |
| Code | Meaning |
|---|---|
EN | GTIN barcode |
SRV | GTIN barcode |
SA | Supplier's article number |
IN | Buyer's item number |
BP | Buyer's part number |
MF | Manufacturer's article number |
UP | UPC |
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 LIN in it? The explainer breaks down every segment and runs in your browser.
Explain my message