The GIN segment carries identification numbers for goods, most commonly SSCCs (Serial Shipping Container Codes) and batch/lot numbers. GIN+BJ identifies a batch/lot number. GIN+ML or GIN+SRV identifies an SSCC. Used in DESADV messages within packaging groups.
GINHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
GIN+BJ+LOT-2026-001'Serial shipping container code (SSCC): LOT-2026-001.
| 1 | Identity type | BJSerial shipping container code (SSCC) |
| 2 | Identity number | LOT-2026-001 |
{
"serialShippingContainerCodeSscc": "LOT-2026-001"
}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 | Identity type | 1.1 Code |
| 2 | Identity number | 2.1 Number, 2.2 To number |
| Code | Meaning |
|---|---|
BJ | Serial shipping container code (SSCC) |
BN | Serial number |
BX | Batch number |
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 GIN in it? The explainer breaks down every segment and runs in your browser.
Explain my message