Home Depot Edi 856

What This Is

This guide is a practical, hands-on reference for creating, validating, and converting Home Depot EDI 856 Advance Ship Notice (ASN) documents. It focuses on the structure and segments that are most likely to cause validation failures with Home Depot and shows exactly how to map an ASN to a flattened CSV for ERP or warehouse systems.

The Home Depot trading partner program enforces strict ASN requirements for shipment-level and item-level data, including hierarchical structure (HL), pallet SSCCs (MAN), carrier and routing details (TD1/TD5), and accurate item identification (LIN, SN1). This guide gives real EDI snippets, line-by-line explanations, conversion mappings, common error codes with fixes, and step-by-step processes you can apply immediately. Note: Home Depot program details were last updated 2026-01-11; verify current requirements with Home Depot's vendor portal.

Who This Is For

This guide is for EDI analysts, integration engineers, 3PLs, and vendors who send ASNs to Home Depot or convert Home Depot 856 files into CSV for ERPs, WMS, or accounting systems.

Key Segments Explained

Below are the Home Depot-specific ASN segments you will encounter frequently. Each explanation includes why the segment is required and what commonly fails during validation.

• ISA / GS / ST — Envelope and transaction header. These set delimiters, control numbers, and functional groupings. Errors here cause immediate functional rejections (997) because downstream parsers cannot interpret the file if the ISA delimiters or control numbers are incorrect.
• BSN (Beginning Segment for Ship Notice) — Identifies the ASN number and creation date/time. Home Depot expects the BSN02 ASN number to match references in their portal; mismatches lead to ASN reconciliation failures and chargebacks.
• HL (Hierarchical Level) — Defines the three-level hierarchy used by Home Depot: Shipment HL, Order HL, and Item HL. The correct parent-child HL structure is mandatory. Common failure: missing HL parent or incorrect HL level code causing item lines to be orphaned.
• TD1 / TD5 / REF (Carrier and Handling) — TD1 provides weight and packaging details (e.g., pallets count), TD5 provides carrier/SCAC, and REF carries bill of lading or shipping reference. Home Depot validates carrier SCAC and often requires TD5/REF pairing; missing SCAC or invalid SCAC causes manual hold.
• MAN (Marks and Numbers) — Used for SSCC pallet serial shipping container codes. Home Depot typically expects an SSCC for each pallet and validates uniqueness by ASN; duplicates or missing MAN/GM segments are a frequent cause of rejections.
• LIN / SN1 / PO4 — Item identification and quantity shipped. LIN contains product IDs (UPC/GTIN or vendor SKU) with qualifiers; SN1 carries shipped quantity and unit of measure; PO4 may provide carton dimensions. Incorrect qualifiers (e.g., using UPC when Home Depot expects GTIN) cause quantity mismatches and receiving errors.

Example EDI Snippet

Below is a realistic Home Depot-style 856 ASN (trimmed to essentials). Each line is annotated after the code block with line-by-line explanations. Use this as a template when building or validating ASNs.

ISA*00*          *00*          *ZZ*SENDERID      *ZZ*HOMEDEPOTID   *210101*1200*U*00401*000000905*0*P*>~
GS*SH*SENDERID*HOMEDEPOTID*20210101*1200*905*X*004010~
ST*856*0001~
BSN*00*ASNNUM12345*20210101*1200*0001~
HL*1**S~
TD1*CTN*10****G*5000~
TD5*B*2*UPSN*****SCAC~
REF*BM*BOL123456~
N1*SF*Vendor Name*92*VEND123~
N3*123 Supplier Rd~
N4*City*ST*ZIP~
HL*2*1*O~
PRF*PO123456*20201201~
HL*3*2*I~
LIN**SK*1234567890123~
SN1**100*EA~
MAN*GM*123456789012345678~
SE*12*0001~
GE*1*905~
IEA*1*000000905~

Line-by-line explanation:

• ISA — Interchange header. The delimiters are shown by the asterisk; ensure ISA segment positions are fixed-width per X12. ISA13-16 contain control number and usage, which must be unique and numeric.
• GS — Functional group header. GS06 is the group control number and must match data in the IEA control envelope pairing rules.
• ST — Transaction set header. ST02 is the transaction control number matched by SE02.
• BSN*00*ASNNUM12345* — ASN identifier. Use an internal ASN ID consistent with Home Depot references in their portal.
• HL*1**S — Shipment level HL. “S” indicates shipment. The second HL element missing indicates no parent (top-level).
• TD1 — Packaging quantity and weight. Adjust elements to match pallets/cartons counts required by Home Depot.
• TD5*B*2*UPSN*****SCAC — TD5 identifies carrier. The last component commonly contains SCAC; validate SCAC against Home Depot accepted carriers.
• REF*BM*BOL123456 — Reference: BOL number.
• N1 / N3 / N4 — Ship From name and address.
• HL*2*1*O — Order HL, parent is HL 1 (shipment).
• PRF*PO123456 — Purchase order reference for this order-level HL.
• HL*3*2*I — Item HL for a shipped item; parent is the order HL 2.
• LIN**SK*1234567890123 — LIN with product ID qualifier SK (vendor SKU) and GTIN/UPC value.
• SN1**100*EA — Shipped quantity 100 each.
• MAN*GM*123456789012345678 — SSCC pallet identifier with qualifier GM.
• SE/GE/IEA — Transaction, functional group, and interchange trailers.

CSV Output Example

When converting an 856 ASN to CSV for your WMS or ERP intake, produce a line per pallet or per item depending on business requirements. Example below maps the above ASN into a CSV table that a receiving system expects.

Step-by-Step Conversion Process

1. Pre-parse validation
   1. Detect delimiters from ISA: character in ISA element 16 is the component element separator; element separators are the characters following the ISA fixed-length area. If your parser fails here, the file cannot be read.
   2. Verify ISA control numbers uniqueness and GS/IEA counts. Use reading 997 functional acknowledgments to confirm prior acknowledgements.
2. Logical parsing & HL hierarchy validation
   1. Read HL segments sequentially and build an in-memory tree. Confirm parent HL exists for each child (HL02 references). If HL parent references are missing, flag a hierarchy error.
   2. Ensure hierarchy codes: S = Shipment, O = Order, I = Item (or your site's accepted codes). If Home Depot expects a three-level ASN, validate presence of at least shipment and item HLs.
3. Field-level validation
   1. Check mandatory fields: BSN02 (ASN number), TD5 SCAC, REF BM (BOL), MAN SSCC for pallets if required.
   2. Validate item identifiers: LIN qualifiers (e.g., UPC/GTIN vs vendor SKU) and ensure the qualifier matches the Home Depot primary ID preference. Use your master GTIN map to translate SKUs to GTINs.
4. Business-rule enforcement
   1. Validate totals: ensure summed item quantities match any declared totals (if present) and pallet counts equal number of MAN segments.
   2. Carrier and route checks: cross-check TD5/SCAC with approved carriers list.
5. Flatten to CSV
   1. Decide granularity (per pallet vs per item). Map hierarchical data to row-level: e.g., shipment-level fields repeated per item row.
   2. Normalize dates to ISO format, map UOMs to internal codes, and export to CSV with headers. Example mapping is shown in the CSV Output Example above.
6. Validation before transmission
   1. Run a pre-send validation tool such as PlainEDI to catch delimiter, HL, and required-segment errors.
   2. Generate a test ASN in Home Depot's vendor sandbox (if available) and reconcile expected acknowledgments using 997 acknowledgments.
7. Monitoring and reconciliation
   1. Monitor for 997 or 824 notifications. Use resolving 997 rejection codes to interpret errors and respond quickly.
   2. Load the converted CSV into WMS and validate counts against POD or receiving transactions; flag discrepancies for investigation.

Common Errors and Fixes

Below are frequent Home Depot ASN errors, a representative error code or identifier you’ll see in EDI acknowledgements or rejection reports, the cause, and a concrete fix.

• Error: ISA Control Number Mismatch (ISA13/IEA02) — Cause: Non-unique or unsynchronized interchange control numbers. Fix: Ensure ISA13 and IEA02 numeric control numbers match and increment per interchange. Use automated control-number generation in your EDI gateway.
• Error: ST/SE Segment Count Mismatch — Cause: SE01 count does not equal actual transaction segments. Fix: Recalculate ST/SE segment counts after you assemble the transaction set. Many toolkits provide libraries that auto-generate SE counts; use them.
• Error: HL Hierarchy Error (Orphan HL) — Cause: An HL segment references a parent HL that does not exist. Fix: Rebuild HL sequence ensuring each child HL has the correct parent ID and level code. Validate the HL tree prior to sending with PlainEDI to catch this.
• Error: Missing or Invalid TD5 SCAC — Cause: Carrier SCAC not supplied or not on Home Depot's carrier list. Fix: Provide TD5 with valid SCAC and description; confirm SCAC with Home Depot operations. Update your approved carrier table.
• Error: Missing MAN SSCC or Duplicate SSCC — Cause: Pallet SSCC not present or repeated across ASNs. Fix: Generate unique SSCCs per pallet, include MAN with qualifier GM, and confirm SSCC format (18-digit) where required. Maintain SSCC issuance logs to ensure uniqueness.
• Error: LIN Product ID Qualifier Mismatch — Cause: Wrong qualifier used for product identifier (e.g., using vendor SKU when Home Depot requires UPC/GTIN). Fix: Configure mapping to use Home Depot-preferred product ID qualifier and populate LIN accordingly. Cross-reference your master item catalog.
• Error: Address/Location Code Not Found (N1/N4 validation) — Cause: Ship-to or ship-from N1 identifiers don't match Home Depot master locations. Fix: Use the ship-to/ship-from code provided by Home Depot; reconcile DUNS/92 identifiers. Update your vendor mappings.

Related Resources

• how to validate edi files before sending
• how to fix edi 856 hierarchy errors
• reading 997 functional acknowledgments
• resolving 997 rejection codes
• edi conversion for 3pl warehouses
• freight-forwarder edi-to-csv

FAQ Section

Q: What is the Home Depot 856 (ASN) used for?

The Home Depot 856 Advance Ship Notice communicates shipment, pallet, and item-level packing information to Home Depot prior to physical arrival. It enables receiving to pre-stage shipments, match expected quantities, and validate carrier and pallet SSCCs.

Q: Which HL hierarchy levels are required in a Home Depot ASN?

Home Depot expects a hierarchical HL structure that typically includes a Shipment HL, an Order HL for each PO on the shipment, and an Item HL for each shipped item. Ensure each HL has proper parent references and the HL03 hierarchy code set to S (Shipment), O (Order), or I (Item) as appropriate.

Q: Do I need to send an SSCC for each pallet?

Yes. Home Depot requires pallet-level identification using MAN segments with SSCC values (qualifier GM). Generate unique SSCCs and include them at the appropriate HL level. Validate uniqueness across ASNs to avoid receiving exceptions.

Q: What common cause triggers a 997 rejection for an ASN?

Immediate causes for 997 rejections include envelope/syntax errors (ISA/GS/ST issues), segment count mismatches (ST/SE), invalid delimiters, and missing mandatory segments like BSN or HL. Use pre-send validation to prevent these rejections.

Q: How do I map LIN qualifiers for Home Depot?

Map LIN product qualifiers to the Home Depot-preferred identifier (GTIN/UPC or vendor SKU depending on agreement). Confirm which identifier Home Depot expects for each item and set LIN02 (product ID qualifier) and LIN03 accordingly. Maintain a master cross-reference table to translate your SKU to the Home Depot ID.

Q: How should I handle carrier SCAC and routing information?

Include TD5 with the carrier code and SCAC and REF segment for BOL references. Confirm the SCAC is on Home Depot’s approved carrier list. If shipping via a third party or broker, include additional REF codes per the trading partner agreement.

Q: What should I check if quantities in the ASN do not match the PO?

Verify SN1 shipped quantities against the PO quantities referenced in PRF/PO segments. Check for unit-of-measure mismatches (e.g., EA vs CA). If differences are intentional (partial shipments), ensure ASN references partial shipment indicators and document exceptions in the PRF or REF segments.

Q: How can PlainEDI help me avoid Home Depot ASN errors?

PlainEDI provides delimiter detection, HL hierarchy validation, mandatory-segment validation, and field-level checks that catch many errors before transmission. Upload your ASN to PlainEDI to receive a validation report and fix issues such as missing MAN segments, invalid LIN qualifiers, or TD5/SCAC problems.

Troubleshooting Case Studies

Two short real-world scenarios show how to diagnose and fix Home Depot ASN issues.

Case Study 1 — Orphan Item Lines

Problem: Shipments were being rejected because receiving could not associate item lines with the order. Diagnosis: HL segments were generated without correct HL02 parent IDs for order-level HLs. Approach: Rebuilt HL sequence to ensure HL02 referenced the correct parent HL and validated with PlainEDI. Result: Rejections stopped, and on-time receiving improved.

Case Study 2 — Duplicate SSCCs

Problem: Home Depot flagged duplicate SSCCs across multiple ASNs, causing chargebacks. Diagnosis: SSCC generation logic used a sequence reset after midnight resulting in reuse. Approach: Implemented ISO SSCC generation incorporating company GLN and a daily-incrementing serial element; updated logs. Also ran a pre-send uniqueness check to prevent duplicates. Result: No duplicate-related rejections.

Home Depot Compliance & Penalties

Retailers including Home Depot enforce ASN compliance and apply penalties for failures in OTIF (on-time in-full) and ASN accuracy. These penalties include chargebacks and operational holds when ASNs are inaccurate or missing required data elements. The Home Depot program information was last updated 2026-01-11; verify current requirements and penalty schedules in Home Depot's vendor portal. Best practice: maintain automated validation (for example, via PlainEDI) to reduce compliance risk.

Final Checklist Before Sending an ASN

• Verify ISA/GS/ST envelopes, delimiters, and control numbers are correct.
• Confirm BSN ASN identifier matches internal and Home Depot references.
• Validate HL hierarchy for Shipment → Order → Item.
• Include MAN SSCC for each pallet and ensure uniqueness.
• Validate TD5 SCAC against Home Depot approved carriers.
• Ensure LIN qualifiers align with Home Depot preferred IDs.
• Run pre-send validation in PlainEDI and resolve all errors before transmission.

If you want to validate or convert your Home Depot 856 files now, upload your ASN to PlainEDI for automated validation reports and CSV conversion.