What is an HL hierarchy in an 856 ASN?
HL loops describe how shipment, order, pack, and item levels relate to each other. Retailers use that hierarchy to match carton labels and receiving detail.
856 ASN errors
HL hierarchy error in EDI 856 ASN
Understand HL hierarchy errors in EDI 856 ASNs, including shipment, order, pack, and item levels, plus steps to fix carton and item nesting.
Why teams evaluate SignalEDI
HIPAA-compliant workflowsAudit trailsSOC 2Published SLA
- Retail supplier< 6 weeks to steady-state
- Healthcare clearing teamFaster first production cutover
- 3PL / logisticsFewer multi-party fire drills
Illustrative example based on representative SignalEDI usage — not a named customer endorsement.
Evaluate without a sales call
Most buyers are not ready to buy on the first visit. Start with a free tool or requirement check — then trial when you are ready.
- Signal sandboxX12 + ASNCheck with SignalEDI validatorUse the free EDI validator to ask Signal to validate X12, check retail ASN readiness, draft setup checklists, and download sandbox reports before onboarding.
- SandboxX12 to JSONEDI mapping previewPreview how healthcare claims, purchase orders, and invoices map into API-ready JSON before production setup.
- CalculatorNamed vendorsNamed competitor EDI cost calculatorModel SignalEDI against Orderful Web EDI, SPS Commerce estimates, and healthcare-only Stedi usage pricing with visible assumptions.
- CalculatorTransparent TCOEDI cost savings calculatorCompare your current provider's setup, base, and per-document fees against SignalEDI's published plans using your own volume.
- LibraryTrading partner compatibilityCheck retailer and marketplace document requirements before you commit to a trial.
- IntegrationsConnector catalogBrowse ERP, accounting, and API connectors without booking a sales call.
What is SignalEDI?
Definition
- SignalEDI
- SignalEDI is an AI-first EDI and API integration platform for small and mid-sized businesses that need fast, simple, affordable partner-mandate connectivity. This guide explains the HL hierarchy error EDI validation pattern — causes, fixes, and prevention — without customer payloads or PHI.
Key takeaways
- The ASN's hierarchical loops do not follow the structure the partner expects, such as shipment to order to pack to item.
- Identify the hierarchy pattern the partner guide requires for the 856.
- Compare shipment, order, pack, and item levels in the outbound HL loops.
HL hierarchy error — page-specific context
- HL errors usually connect to physical packing reality; the X12 fix often requires WMS cartonization data, not only map changes.
- Retailers can require different ASN hierarchy patterns, so a generic shipment/item structure may pass one buyer and fail another.
- SignalEDI validates ASN hierarchy alongside label and shipment context so teams see the operational cause of the X12 failure.
Meaning
What this error means
The ASN's hierarchical loops do not follow the structure the partner expects, such as shipment to order to pack to item.
Static validator references: RULEPACK_ELEMENT_REQUIRED. These are public rule identifiers, not customer transaction data.
Where this error appears
Common causes
- Pack-level cartons are missing even though the retailer requires carton detail.
- Item loops are attached to the wrong parent HL level.
- SSCC label data is present but not nested under the expected pack loop.
Step-by-step fix
- Identify the hierarchy pattern the partner guide requires for the 856.
- Compare shipment, order, pack, and item levels in the outbound HL loops.
- Add missing parent levels or correct HL parent-child references.
- Retest with carton and item examples that match the physical shipment.
How to prevent it next time
- Model ASN hierarchy from actual cartonization data, not only order lines.
- Validate HL parent references and level codes before sending ASNs.
- Keep SSCC/MAN label validation tied to pack-level hierarchy rules.
SignalEDI prevention
How SignalEDI handles this pattern
- Validates HL loop structure against partner ASN expectations.
- Surfaces hierarchy errors before label and receiving problems become chargebacks.
- Links ASN errors to shipment, carton, and item context for operator review.
Related fix paths
HL hierarchy error FAQ
Why do retailers reject 856 hierarchy errors?
A broken hierarchy makes it hard to know which items are in which cartons or which order a carton belongs to, creating receiving and chargeback risk.
How does SignalEDI catch HL hierarchy problems?
SignalEDI validates the ASN hierarchy pattern and identifies missing or misplaced levels before the document is sent.
Validate before you resend
Run the public validator on a synthetic sample, then retry only when the correction is clear.
Explore SignalEDI
Related paths
Pricing, checkout, solutions, support, partner requirements, and trust artifacts stay linked so buyers do not dead-end on a single page.