Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 segment reference
LIN — Item Identification
X12 LIN segment on EDI 856 ASNs identifies shipped SKUs at item HL levels — product qualifiers and shipped quantities.
LIN segment facts
- LIN product IDs must align with PO1 lines from the original 850 — unapproved substitutions trigger chargebacks.
- Item-level HL loops pair LIN with SN1 or QTY segments depending on partner guide variants.
- Inbound 856 JSON from SignalEDI exposes normalized line SKU and quantityShipped for WMS ingestion.
What the LIN segment does
LIN appears at item-level HL loops in 856 ASNs. It binds shipped product IDs and quantities to the original PO lines for retailer receiving and three-way match.
Loop: Once per item HL level
Common transaction sets: 856
Key elements
| Element | Name | Description |
|---|---|---|
| LIN01 | Assigned identification | Optional line reference within the ASN. |
| LIN03 | Product ID qualifier | UP, VN, SK — mirrors PO1 identifier family. |
| LIN04 | Product ID | UPC or SKU shipped — must match PO and label. |
Example LIN segment
LIN**UP*012345678905~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common LIN errors
- Shipped SKU not on original PO
- Quantity at LIN not matching CLD roll-up
- Wrong qualifier for the retailer catalog
Related reference
FAQ
Frequently asked questions
Receiving scans compare LIN product IDs to PO and label data — substitutions must be acknowledged on the 855 or reflected consistently on the ASN.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”