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
HL — Hierarchical Level
Understand X12 HL segments in EDI 856 ASNs: parent/child shipment, order, pack, and item levels retailers require.
HL segment facts
- HL03 level codes define the ASN tree — skipping a pack level breaks carton-to-item reconciliation at major retailers.
- HL02 parent pointers must reference a prior HL01 or parsers cannot rebuild the shipment hierarchy.
- SignalEDI validation flags orphaned HL rows before an 856 reaches a partner mailbox.
What the HL segment does
HL builds the shipment → order → pack → item tree in an 856. HL03 parent ID links each level so retailers can reconcile nested quantities.
Loop: Multiple per 856
Common transaction sets: 856
Key elements
| Element | Name | Description |
|---|---|---|
| HL01 | Hierarchical ID number | Sequential ID within the transaction. |
| HL02 | Hierarchical parent ID | Points to parent HL01; empty at shipment root. |
| HL03 | Hierarchical level code | S=shipment, O=order, P=pack, I=item. |
Example HL segment
HL*1**S~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common HL errors
- Broken parent pointers
- Missing item-level HL when cartons are declared
- Duplicate HL01 IDs
Related reference
FAQ
Frequently asked questions
Retailers require complete S-O-P-I chains with quantities that roll up correctly at each level.
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.”