PlainEDI
← Back to Guides

Home Depot Edi 846

By Alexander Georges|Updated April 21, 2026
TL;DR: This guide explains Home Depot EDI 846 (Inventory Inquiry/Advice) end-to-end: what segments Home Depot requires, how to parse and convert 846 to CSV, why common errors occur, and practical fixes you can apply immediately. Use the step-by-step conversion process and validation checks (including PlainEDI validation) to prevent rejections and reduce compliance penalties effective 2026-04-19.

What This Is

This guide covers processing Home Depot EDI 846 Inventory Inquiry/Advice files. An 846 transmits inventory levels and availability details for SKU-location combinations. Vendors and 3PL partners send 846s to Home Depot to communicate on-hand quantities, available to sell, and stock statuses used by replenishment and ordering systems.

You'll learn the specific segments you must validate, line-by-line parsing examples, conversion to CSV for downstream ERP/warehouse systems, and troubleshooting for the most common failures seen in Home Depot 846 exchanges. This is a practical manual for developers, EDI analysts, and operations staff who receive or produce Home Depot 846 messages.

Who This Is For

This guide is for EDI developers, integration engineers, vendor compliance teams, and third‑party logistics (3PL) operators responsible for generating, validating, or ingesting Home Depot 846 files into order-management or replenishment systems.

Key Segments Explained

  • ISA / IEA (Interchange Control Header/Trailer)

    The ISA header defines the interchange: sender/receiver IDs, delimiters, and control number. Home Depot requires consistent ISA control numbers and matching IEA counts. Validate ISA05 (Interchange Sender ID) and ISA07 (Interchange Receiver ID) against your trading partner agreement. The IEA segment must contain the same control count used in ISA.

  • GS / GE (Functional Group Header/Trailer)

    GS groups multiple transaction sets. Validate GS02 (Application Sender's Code) and GS03 (Application Receiver's Code). GE01 must equal the count of ST/SE transaction sets in the group. Mismatched GE counts cause functional rejections.

  • ST / SE (Transaction Set Header/Trailer)

    ST begins the 846 transaction (ST*846*0001). SE closes it and includes the segment count. Ensure SE01 equals the number of segments between ST and SE inclusive. Home Depot will reject if SE segment counts are off.

  • BIA (Beginning Inventory Advice)

    BIA identifies the inventory advice type and date. BIA02 is the Advice Type Code; Home Depot commonly expects a code indicating current inventory snapshot. BIA03 is the Date/Time reference which your systems must map to file timestamps in CSV outputs.

  • N1 / N3 / N4 (Name and Address Loop)

    N1 identifies the location (Home Depot Store or DC). N1*ST identifies a store, N1*SU may identify a supplier. N3 and N4 provide address and city/state/ZIP. Accurate store/ship-to identifiers are essential for location-level inventory.

  • LIN (Item Identification)

    LIN identifies the product using qualifiers like UPC, UPC/EAN (LIN*UP*...), or SKU qualifiers used by Home Depot. LIN is the core element used to map to your internal SKU or UPC in ERP.

  • SN1 (Item Detail - Inventory)

    SN1 provides quantity on hand, available quantity, and unit of measure. SN1*Quantity*UnitOfMeasure*... must be parsed carefully: Home Depot systems expect integers for counts and specific UOM codes. Validate numeric fields for non-numeric characters.

  • CTT / SE (Transaction Totals / Trailer)

    CTT gives a count of line items. SE must be validated for segment counts and transaction control numbers. Ensure CTT01 matches the number of LIN loops sent in the ST/SE envelope.

Example EDI Snippet

ISA*00*          *00*          *ZZ*SENDERID      *ZZ*HOMEDEPOTID   *210419*0830*U*00401*000000905*0*P*>~
GS*IN*SENDERID*HOMEDEPOTID*20210419*0830*905*X*004010~
ST*846*0001~
BIA*00*INVENTORY*20210419~
REF*ZP*STORE12345~
N1*ST*THE HOME DEPOT*92*0012345~
N3*123 MAIN ST~
N4*ATLANTA*GA*30303~
LIN**UP*0012345678905*VN*SKU12345~
SN1**50*EA~
LIN**UP*0012345678912*VN*SKU54321~
SN1**0*EA~
CTT*2~
SE*13*0001~
GE*1*905~
IEA*1*000000905~

Line-by-line explanation:

  • ISA*00* ... * - Interchange header. ISA control number is 000000905. Delimiters: '*' element, '~' segment terminator, '>' component element separator (declared in ISA).
  • GS*IN*...*904*X*004010 - Functional group header. GS06 is version 004010.
  • ST*846*0001 - Transaction set 846 with control number 0001.
  • BIA*00*INVENTORY*20210419 - Beginning Inventory Advice dated 2021-04-19.
  • REF*ZP*STORE12345 - Reference qualifier ZP (Store Number) with value STORE12345. Map this to Home Depot store ID.
  • N1*ST*THE HOME DEPOT*92*0012345 - Name loop identifying the store; N1 code ST indicates a ship-to/store. N1*92 contains the Home Depot assigned location number 0012345.
  • N3*, N4* - Address and city/state/ZIP for the location.
  • LIN**UP*0012345678905*VN*SKU12345 - Item identification: UPC followed by Vendor SKU.
  • SN1**50*EA - Quantity on hand 50 EACH.
  • CTT*2 - Two line items reported. Confirm count.
  • SE*13*0001 - Segment count is 13 from ST to SE inclusive; must match the actual count.
  • GE*1*905 and IEA*1*000000905 - Group and interchange trailers; control numbers must match GS and ISA.

CSV Output Example

StoreID HomeDepotLocationID ReportDate UPC VendorSKU OnHandQty UOM
STORE12345 0012345 2021-04-19 0012345678905 SKU12345 50 EA
STORE12345 0012345 2021-04-19 0012345678912 SKU54321 0 EA

This CSV structure is typical for ingestion into an ERP or WMS. Ensure your CSV uses consistent date formats (ISO 8601 recommended) and integer quantities. Include headers in the first row for automated imports.

Step-by-Step Conversion Process

  1. Receive and validate the interchange and group headers
    1. Read ISA and record ISA control number, delimiters, and sender/receiver IDs.
    2. Validate ISA05/ISA07 (sender/receiver) against your trading partner file for Home Depot.
    3. Confirm GS/GE counts and GS control number match across messages.
  2. Validate transaction-level control and segment counts
    1. Confirm ST02 and SE02 control numbers match.
    2. Validate SE01 equals actual segment count from ST to SE inclusive.
  3. Parse BIA and REF for report metadata
    1. Extract BIA date (inventory snapshot date) and BIA type code to determine record timestamp.
    2. Map REF qualifiers (example: ZP store number) to vendor/store identifiers.
  4. Loop through N1/N3/N4 to identify locations
    1. For each N1*ST loop, extract the Home Depot location ID (often in N1*92 or REF segment) and standardize it to your internal location code.
    2. Store address lines from N3/N4 when needed for multi-DC mapping.
  5. Parse item loops (LIN..SN1)
    1. For each LIN loop, extract identifiers: UPC (UP), SKU (VN), or other qualifiers. Prefer UPC for mapping to Home Depot catalog.
    2. Parse SN1 to extract quantity and UOM. Cast SN1 quantity to integer and validate UOM against an accepted list (EA, PK, CT).
    3. Collect LIN/SN1 pairs into a row structure ready for CSV.
  6. Validate totals and business rules
    1. Confirm CTT line count equals the number of LIN loops processed.
    2. Apply business rules: no negative quantities, UOM allowed values, and per-store SKU mapping exists.
  7. Generate CSV and run post-processing validation
    1. Emit CSV with headers matching your ERP import mapping. Use the exact column order the ERP expects.
    2. Run a final validation pass using PlainEDI validations (schema, segment counts, data-type checks) before sending to Home Depot systems or your internal ingestion pipeline: PlainEDI.

Common Errors and Fixes

  • Error: SE segment count mismatch — SE01 does not match actual segments.

    Fix: Re-count segments between ST and SE. Many processors accidentally count control trailer segments or omit empty lines. Use deterministic parser to compute segment count and set SE01 accordingly.

  • Error: ISA/IEA control number mismatch (Control No. X12-ISA) — IEA02 does not match ISA control number.

    Fix: Ensure your interchange control number generator increments uniquely per interchange. Do not reuse ISA control numbers within the same trading period.

  • Error: Invalid N1 location ID — Home Depot rejects because N1*92 or REF store ID is missing or improperly formatted.

    Fix: Map your internal store identifiers to Home Depot's location numbers before generating N1/REF. Validate format and leading zeros; Home Depot often expects fixed-width numeric IDs. Check the N1 qualifier used in your Home Depot trading profile.

  • Error: Non-numeric SN1 quantity — Quantity contains punctuation or decimal.

    Fix: Strip commas and convert decimals to integer units when UOM is EA. If quantity should be fractional, confirm UOM supports decimals and update mapping rules.

  • Error: LIN product identifier mismatch — Home Depot's UPC vs. Vendor SKU mismatch.

    Fix: Use Home Depot’s preferred identifier (UPC) in LIN*UP when required. Maintain a reliable master mapping table between vendor SKU and Home Depot UPC. If multiple identifiers are used, ensure LIN uses the qualifier and sequence acceptable to Home Depot.

  • Error: Unknown elements due to wrong delimiters — Parser fails because delimiters declared in ISA are not honored.

    Fix: Read element delimiter (ISA[3]), component element separator (ISA[16]), and segment terminator (last character after ISA) from ISA and configure the parser accordingly. Hardcoding '*' or '~' is a common mistake.

  • Error: CTT line count mismatch — CTT01 does not equal number of LIN loops.

    Fix: Recalculate CTT count from parsed LIN loops. If nested loops exist, ensure you count only top-level LIN occurrences relevant to CTT semantics.

Related Resources

Troubleshooting Case Studies

Case Study 1: Store-level Quantity Zeroes Causing Replenishment Gaps

Problem: A vendor sent an 846 with several SKUs showing SN1 quantity zero. Home Depot replenishment flagged sudden zero inventory and placed chargebacks on cancelled allocations. Analysis revealed vendor used a nightly job that defaulted to zero when inventory feed failed.

Solution: Add a health-check to the inventory extraction job to stop generation if upstream feed is stale. Implement a flag in BIA or a REF segment to indicate estimated or actual snapshot. Validate with PlainEDI pre-submission checks to ensure no accidental zero-sending: PlainEDI validation can enforce non-null inventory values or require an explicit reason code in REF.

Case Study 2: ST/SE Control Number Inconsistency Rejection

Problem: A scheduler job concatenated multiple ST/SE pairs without updating SE02 values, causing mismatched control numbers. Home Depot 997 rejections referenced segment count and control mismatch.

Solution: Update transaction set generator to reuse unique sequential transaction set control numbers per ST and ensure SE02 equals ST02. Automate addition of sequence numbers and validate with a parser that flags control number reuse. PlainEDI upload step flagged the mismatch before transmission and prevented penalties.

Compliance and Penalties (Home Depot)

Home Depot enforces vendor compliance and may apply penalties for non-compliant ASN and inventory transmissions, including OTIF and ASN accuracy penalties. Effective 2026-04-19, Home Depot continues to require precise ASN and inventory data; vendors must consult the Home Depot vendor portal for the latest penalty thresholds and specifics. Verify current requirements with the Home Depot vendor portal for exact penalty amounts and effective program changes.

Best Practices and Validation Checklist

  • Always parse ISA delimiters dynamically from the ISA segment.
  • Run checksum validations: SE segment counts, GE/IEA counts, and CTT line totals.
  • Keep a master SKU-to-UPC mapping and validate LIN qualifiers against it.
  • Use the BIA date for consistent report timestamps; if multiple dates appear, prioritize BIA03.
  • Apply character-set normalization (strip non-printable control characters) before parsing.
  • Automate pre-send validation with PlainEDI to catch structural and business-rule violations before transmission.

FAQ Section

Q: What is the purpose of the EDI 846 for Home Depot?

The 846 communicates inventory status for specific SKUs at Home Depot locations (stores, DCs). It provides on-hand counts, available-to-sell quantities, and location identifiers so Home Depot can reconcile inventory for replenishment and order planning.

Q: Which segments are most likely to cause Home Depot rejections?

Common rejection triggers are incorrect ISA/IEA control numbers, mismatched SE segment counts, invalid or missing N1/REF location identifiers, SN1 non-numeric quantities, and LIN identifier mismatches. Validate these segments first when troubleshooting.

Q: How should I map Home Depot location IDs from the 846 to internal systems?

Extract location IDs from N1*92 or REF qualifiers as specified by your Home Depot trading profile. Normalize leading zeros, and maintain a mapping table that links Home Depot location IDs to your internal location or store codes.

Q: What is the correct way to handle quantities with decimals in SN1?

If UOM is EA, convert quantities to integers and ensure upstream inventory systems provide integer counts. If the UOM supports decimals (e.g., LB), retain decimals and validate precision rules against Home Depot requirements.

Q: How often should I send 846 files to Home Depot?

Frequency depends on your agreement and supply chain needs. Common cadences include daily or multiple times per day for fast-moving goods. Confirm frequency with Home Depot’s trading partner guidelines and your vendor onboarding documentation.

Q: What does PlainEDI provide for 846 validation?

PlainEDI provides schema and business-rule validation for 846 files before submission. It checks ISA/GS/ST control numbers, segment counts, data types, and custom rules such as required REF qualifiers and SKU mapping enforcement. Use PlainEDI to validate files and prevent common errors from reaching Home Depot.

Q: Why does the SE segment count error happen even though file looks correct?

SE count errors occur when segment terminators or empty trailing lines are included or excluded inconsistently during segment counting. Use a strict parser that counts segments based on the declared segment terminator from ISA and ensure the count includes ST and SE segments.

Q: Who do I contact for Home Depot-specific mapping requirements?

Contact your Home Depot EDI onboarding or vendor support representative listed in the Home Depot vendor portal. For technical validation prior to submission, use a third-party validator like PlainEDI and reference the Home Depot trading partner guide for exact qualifiers and required segments.

Final Call to Action

Ready to validate your Home Depot 846 files and prevent rejections? Upload your 846 now for full structural and business-rule validation using PlainEDI. Our validator checks ISA/GS/ST controls, segment counts, N1 location mapping, LIN/SN1 consistency, and produces CSV-ready outputs for ERP ingestion.