What are EDI 856 Hierarchy Levels?

Definition

EDI 856 hierarchy levels define how shipment information is organized within an Advance Ship Notice (ASN). The hierarchy lets a trading partner communicate shipment structure from the overall shipment down to individual orders, cartons, packs, and items. Each level identifies a different business object and establishes its relationship with the levels above and below it.

The hierarchy is represented through HL segments in an EDI 856 transaction. An HL segment assigns an identifier to a level, identifies its parent level when applicable, and indicates the type of information represented. This structure allows a retailer, distributor, or supplier to interpret shipment contents consistently and prepare receiving, inventory, and reconciliation activities.

Table of Contents

How EDI 856 Hierarchy Levels Work

An EDI 856 typically begins with a shipment-level hierarchy and then moves downward into increasingly specific information. The exact structure depends on the trading partner's implementation guide, so not every transaction contains every possible level.

  • Shipment level: Describes the overall shipment, such as carrier, shipment identification, and shipment-related dates.
  • Order level: Connects shipment contents to a specific customer order or purchase order.
  • Tare or pack level: Represents a physical handling unit, such as a carton, pallet, or other packaged grouping.
  • Item level: Identifies individual products, quantities, units of measure, and related item details.

For example, one shipment can contain several orders, each order can contain multiple cartons, and each carton can contain multiple items. The parent-child relationships in the HL segments preserve this structure throughout the transaction.

Key Components of the Hierarchy

The most important component is the HL segment, which establishes the relationship between hierarchy levels. An HL identifier uniquely identifies the current level, while a parent identifier connects it to the preceding level. The hierarchy code then indicates whether the segment represents a shipment, order, pack, or item.

This structure becomes especially useful when a receiving system needs to determine which items belong to which carton and which cartons belong to which order. A well-structured hierarchy therefore supports accurate receiving, inventory updates, and shipment reconciliation.

Procurement controls can also influence the quality of information flowing into downstream shipment documents. For example, PO Configurability can support customization of PR and PO fields, severity levels, and inclusion rules so that procurement data remains aligned with downstream transaction requirements.

EDI 856 Hierarchy and ERP Integration

When an EDI 856 is integrated with an ERP, hierarchy mapping determines how shipment data is interpreted inside the receiving or inventory workflow. The integration should preserve parent-child relationships rather than treating each HL segment as an unrelated record.

This is particularly relevant during ERP migration or when extending finance and supply-chain workflows around an existing platform. Understanding How Many Levels Does a Typical ERP System Include? can provide broader context for how application, integration, data, and workflow layers interact when EDI transactions connect with an ERP.

At the procurement stage, the purchase order establishes the commercial reference that can later be connected to shipment information in the EDI 856. This connection helps receiving teams compare what was ordered with what was shipped and subsequently received.

Business Use Cases and Data Flow

EDI 856 hierarchy levels are valuable when a business needs detailed visibility into shipment composition. A retailer can use the hierarchy to prepare receiving instructions before physical goods arrive, while a supplier can communicate exactly how products are grouped for transportation and handling.

The hierarchy also supports downstream financial and operational workflows. Shipment information can contribute to matching activities, inventory records, and invoice validation. For example, an EDI Invoice can carry billing information that is evaluated alongside order and receipt data, creating a more connected procure-to-pay information flow.

Other electronic business processes can use related structured data. An EDI Tax Filing can support standardized exchange of tax-related information, while an EDI Payment File supports structured payment instructions after the relevant purchasing and settlement processes are completed.

Best Practices for Managing EDI 856 Hierarchies

  • Follow the trading partner guide: Use the hierarchy levels, codes, and required segments specified by the receiving partner.
  • Preserve parent-child relationships: Ensure every order, pack, and item remains connected to its appropriate parent hierarchy.
  • Maintain consistent identifiers: Use stable shipment, order, package, and item identifiers across related transactions.
  • Validate quantities and units: Confirm that quantities at lower hierarchy levels reconcile with the shipment structure and applicable business rules.
  • Align approvals and workflows: Understanding EDI 856 hierarchy levels alongside Sync Approvals & Workflows: 6 Keys to Seamless Alignment helps teams connect shipment data with organizational approval processes and understand how workflow alignment supports controlled business operations.

Summary

EDI 856 hierarchy levels provide the structural framework for representing shipments from the overall shipment through orders, packages, and individual items. HL segments establish parent-child relationships so receiving and ERP systems can interpret the transaction accurately. Correct hierarchy design supports shipment visibility, receiving accuracy, inventory coordination, order reconciliation, and connected financial workflows.