PlainEDI
← Back to Guides

Lowe's Edi 856

By Alexander Georges|Updated May 5, 2026
TL;DR: This guide gives a practical, step-by-step reference for creating, validating, and converting Lowe's EDI 856 (ASN) files so your shipments meet Lowe's ASN requirements and avoid chargebacks. It includes real EDI code examples, CSV mapping, common Lowe's 856 errors with fixes, and how PlainEDI validation prevents the most frequent ASN problems.

What This Is

This guide explains how to prepare and validate a Lowe's EDI 856 Advance Ship Notice (ASN) using X12 EDI conventions. You will learn the purpose of each key 856 segment (BSN, HL, TD1/TD5, N1, LIN, SN1, etc.), see real-world EDI snippets annotated line-by-line, and receive a reproducible process to convert EDI to CSV for downstream systems like WMS or ERP.

Lowe's ASN requirements are mission-critical: they use the 856 to update receiving systems, initiate cross-dock/putaway workflows, and drive invoice matching. Non-compliant ASNs cause late confirmations, receiving delays, and potential chargebacks. This guide covers both creation and troubleshooting — and shows how PlainEDI automated validation can be used to catch formatting, hierarchy, and data-mapping errors before sending to Lowe's.

Who This Is For

This guide targets EDI developers, integration specialists, supply chain managers, and vendors who ship to Lowe's and must produce compliant EDI 856 ASNs. It's useful if you convert ASNs to CSV for warehouses, integrate with ERP/WMS, or troubleshoot ASN rejections.

Key Segments Explained

Below are the core 856 segments you will see and why each matters for Lowe's processing.

  • BSN (Beginning Segment for Ship Notice)

    The BSN identifies the ASN and shipment creation date/time. Lowe's uses BSN02 as the ASN identifier and BSN03/BSN04 for date/time stamps. Missing or duplicate BSN identifiers generate reconciliation errors and will prevent Lowe's from matching the ASN to the purchase order (PO).

  • HL (Hierarchical Level)

    HL defines the ASN hierarchy: shipment (HL01=1), order, and item levels. Correct parent-child HL relationships are required so Lowe's systems can aggregate carton and pallet details to the correct PO and item.

  • TD1 / TD5 (Carrier and Packaging Details)

    TD1 supplies packing quantities and weights (pallets, cartons, total weight). TD5 includes carrier routing and SCAC. Accurate TD segments are used by Lowe's for inbound scheduling and carrier routing; incorrect SCAC codes cause dock scheduling mismatches.

  • N1 / N3 / N4 (Party and Address Information)

    N1 identifies parties: ST (Ship To - Lowe's DC), SF (Ship From - your warehouse), and BT/PR (Bill To or Purchasing). N3/N4 provide address lines and city/state/ZIP. Lowe's expects precise N1 qualifiers and correct DC identifiers to route inventory correctly.

  • MAN / REF / PRF

    REF and MAN carry additional references: carton numbers, pallet IDs (MAN*GM), and Lowe's PO or ASN references. Lowe's often expects specific REF qualifiers or MAN values for carton tracking and pallet tagging; omit at your risk.

  • LIN / SN1 / CTT

    LIN contains the item identifier (UPC/GTIN/SKU) and SN1 provides shipped quantities. CTT provides the line count and total quantity. Mis-typed GTINs are the top cause of mismatched receipts and chargebacks.

Example EDI Snippet

ISA*00*          *00*          *ZZ*SENDERID      *ZZ*LOWES          *210503*1253*U*00401*000000001*0*P*:~
GS*SH*SENDERID*LOWES*20210503*1253*1*X*004010~
ST*856*0001~
BSN*00*ASN1234567*20210503*125300~
HL*1**S~
TD1*CTN25*50****G*48X40~
TD5*B*2*SCAC**Carrier Name~
REF*CN*CONT1234~
N1*SF*Acme Warehouse*92*WH123~
N1*ST*LOWES DC#1234*92*DC1234~
HL*2*1*O~
PRF*PO987654*20210501~
HL*3*2*I~
LIN**UP*00012345600012*VN*SKU123~
SN1**10*EA~
CTT*1~
SE*13*0001~
GE*1*1~
IEA*1*000000001~

Line-by-line explanation:

  • ISA... - Interchange control header; contains sender/receiver IDs and delimiters. Lowe's validates ISA15/16 for control consistency.
  • GS*SH... - Functional group header for Ship Notice/Manifest (856). GS06 group control number must match GE02 on the trailer.
  • ST*856*0001 - Transaction set header; ST02 is the transaction set control number that must match SE02.
  • BSN*00*ASN1234567*20210503*125300 - BSN01 indicates transaction purpose; BSN02 is ASN number; BSN03/04 are date/time.
  • HL*1**S - Top-level hierarchical level (Shipment). HL01=1; HL03=S denotes shipment level.
  • TD1*CTN25*50****G*48X40 - Packaging details: 25 cartons, gross weight 50, and pallet size 48x40 (example uses G for gross weight qualifier).
  • N1*ST*LOWES DC#1234*92*DC1234 - Ship To Lowe's DC name with entity identifier code 92 used for assigned code.
  • HL*2*1*O - Order level HL (child of shipment HL01).
  • PRF*PO987654*20210501 - PO reference at order level; Lowe's will match this to receive by PO number.
  • HL*3*2*I - Item level HL (child of order).
  • LIN**UP*00012345600012*VN*SKU123 - Contains UPC (UP) and vendor number (VN). Use the identifier your trading partner requires.
  • SN1**10*EA - Indicates 10 units shipped each.
  • CTT*1 - Transaction totals: 1 line item in this example.
  • SE/GE/IEA - Trailers closing the transaction, group, and interchange; control numbers must match respective headers.

CSV Output Example

Example mapping of the EDI ASN into a CSV format commonly used by warehouses. Columns chosen are typical: ASN, PO, SKU, Qty, PackType, CartonID, ShipToDC, Carrier, Weight.

ASN PO SKU Qty PackType CartonID ShipToDC CarrierSCAC GrossWeight
ASN1234567 PO987654 00012345600012 10 CTN CONT1234 DC1234 SCAC 50

Step-by-Step Conversion Process

  1. Extract and Validate ISA/GS/ST Control Data
    1. Read the interchange header ISA to determine delimiters (element separator, component separator, segment terminator). Many tools assume default delimiters; Lowe's uses the separators indicated in ISA.
    2. Validate interchange sender/receiver IDs against your trading profile for Lowe's. Confirm ISA13/ISA14 usage indicators and ISA15/ISA16 control numbers.
    3. Confirm GS/GE and ST/SE control counts match. Mismatched control numbers cause functional rejections.
  2. Parse the Hierarchical Levels (HL)
    1. Traverse HL segments and build a parent-child tree: Shipment -> (Order -> Item).
    2. Use HL03 type codes: S for shipment, O for order, I for item. Ensure each HL with a parent references an HL01 that exists.
    3. If HL numbering or parent references are missing or non-sequential, flag as hierarchy error and fail conversion until corrected.
  3. Map Key Data to CSV Columns
    1. From BSN02 populate CSV ASN column.
    2. From PRF or PO-ref at Order HL populate PO column.
    3. From LIN element (UP/VP/VN) populate SKU column and prefer the identifier Lowe's expects (confirm trading agreement).
    4. From SN1 populate Qty; from TD1 populate pack type and Gross Weight; from REF or MAN populate carton or pallet IDs.
  4. Validate Business Rules
    1. Enforce SKU lookups: confirm SKU or GTIN exists in your item master and in Lowe's item catalog if connected.
    2. Validate totals: check CTT and totals in TD1/TD3 for consistency with summed SN1 quantities.
    3. Check carrier SCAC against approved carriers list for Lowe's routing.
  5. Generate CSV and Run Sanity Checks
    1. Create CSV rows per item or per carton as your WMS requires.
    2. Run checksum validations (row count, required fields not empty). If anything fails, provide a clear error log with segment/element pointers back to the EDI file.
    3. Upload validated CSV for downstream consumption or attach to order in your ERP.
  6. Transmit ASN and Monitor Acknowledgments
    1. Send the 856 to Lowe's and await 997 Functional Acknowledgment. Parse 997 for accept/reject codes and correct issues immediately.
    2. Use PlainEDI validation before transmission to prevent syntactic and common semantic errors. PlainEDI prevents mismatched control numbers and provides HL hierarchy checks and required segment validation when you PlainEDI upload your file.

Common Errors and Fixes

  • ERR: ISA/GS Control Number Mismatch — Fix: Ensure GS02/GS06 group control numbers match GE02; ensure ST02 matches SE02. Rebuild trailer control numbers if your EDI engine resets them.
  • ERR: HL Hierarchy Broken (HL Parent Not Found) — Fix: Re-sequence HL01 numbers and validate HL04 (parent ID) references. Use a tree-building utility to detect or use PlainEDI's HL hierarchy validation to surface exact segment lines.
  • ERR: Missing or Invalid Ship-To (N1*ST) Code — Fix: Replace free-text DC names with Lowe's assigned DC code in N1*92 or N1*ST with qualifier 92. Confirm assigned Lowe's DC numbers in vendor portal.
  • ERR: SKU/GTIN Not Recognized — Fix: Verify item identifiers used in LIN match the identifier Lowe's expects (UPC/GTIN vs. vendor SKU). Crosswalk your SKU to Lowe's item file, and include the correct qualifier (UP, VN, or SK).
  • ERR: Carton ID or Pallet ID Missing (MAN/REF) — Fix: Add MAN segments with qualifier GM for GS1 serial shipping container code (SSCC) or use REF with the qualifier Lowe's expects. Include per-carton MAN segments if retailer requires scanable SSCC.
  • ERR: Quantity Totals Do Not Match (CTT vs SN1 Sum) — Fix: Recompute and ensure CTT01 matches the number of LIN segments with SN1 lines and that quantity sums align with TD1 totals. Check for duplicate item lines causing overcounts.
  • ERR: Carrier SCAC Not Accepted — Fix: Confirm SCAC in TD5 with Lowe's approved carrier list. Use TD5*B*2*SCAC**Carrier Name and validate SCAC code.

Related Resources

Common Lowe's Compliance Notes (Penalties and Requirements)

Effective 2026-05-03, Lowe's enforces ASN accuracy and OTIF (On Time In Full) compliance program requirements. Typical enforcement actions include invoice chargebacks and ASN-related penalties for missing or inaccurate ASNs. Verify current penalty amounts and thresholds with the Lowe's vendor portal; penalties and thresholds are subject to change. To avoid penalties, ensure your ASNs are timely, accurate, and use the DC codes Lowe's assigned.

PlainEDI can help prevent compliance issues by running Lowe's-specific validation rules at upload time, including required segment checks, HL hierarchy validation, and SCAC/GTIN verification. Upload files to PlainEDI to run these validations before you send ASNs to Lowe's.

Case Study: Fixing an HL Hierarchy Error in Production

Scenario: A supplier repeatedly received 997 rejects for HL hierarchy errors after implementing a new WMS-to-EDI export. Investigation revealed the WMS emitted HL segments with non-sequential HL01 values and wrong parent IDs (HL04). The result: Lowe's could not aggregate item-level details into the PO-level node, so the ASN rejected.

Resolution steps applied:

  1. Export the raw EDI file and run a script that builds the HL tree and reports missing parent references using line numbers.
  2. Fixed the WMS EDI template to generate HL01 as an incrementing integer and HL04 as the correct parent HL01 value. Added automated unit tests to check HL integrity.
  3. Validated corrected files with PlainEDI prior to transmission. PlainEDI flagged no HL errors and confirmed segment counts matched.
  4. Resent ASN; Lowe's accepted ASN and subsequent inbound receiving occurred without delays, avoiding chargebacks.

Pro Tips and Best Practices

  • Always parse delimiters from the ISA line — do not assume defaults.
  • Prefer GS/SE and ISA/IEA control consistency checks as a first validation layer.
  • Include SSCCs in MAN*GM where retailer scan requirements exist; Lowe's scanning improves dock throughput.
  • Keep a distinct mapping table for Lowe's expected item identifiers (UPC vs vendor SKU) and validate against it pre-send.
  • Run a pre-send validation with an automated tool such as PlainEDI to catch both syntactic and common semantic errors.

FAQ Section

Q: What is a Lowe's EDI 856 and why is it required?

An EDI 856 (Advance Ship Notice) is the X12 transaction sent to Lowe's to inform them of shipment contents, packaging, carrier, and which purchase orders are included. Lowe's uses the ASN to prepare receiving schedules, direct shipments to the correct DC, and match receipts to invoices. Accurate 856s reduce receiving delays and chargebacks.

Q: Which identifiers should I put in LIN for Lowe's?

Place the identifier that Lowe's expects per your trading partner agreement: typically UPC/GTIN (qualifier UP) or vendor SKU (qualifier VN). Confirm the expected LIN qualifiers and values in Lowe's vendor portal and include both if required for dual-identifier mapping.

Q: What HL segment hierarchy does Lowe's expect?

Lowe's expects a three-level HL hierarchy: shipment (HL with S), order (HL with O), and item (HL with I). Ensure each HL with a parent points to a valid HL01 parent and maintain sequential HL01 numbers. Validate hierarchy at creation time to prevent functional rejections.

Q: What carrier information is required in TD5?

Include the carrier routing code and SCAC in TD5. Use the TD5*B*2*SCAC**Carrier Name format to ensure Lowe's can schedule the inbound carrier. Verify your SCAC against Lowe's approved carrier list in the Lowe's portal.

Q: How do I include carton or pallet SSCCs?

Use the MAN segment with the appropriate qualifier for SSCC (for example, MAN*GM*) at the shipment or carton HL level, based on Lowe's requirements. Also include REF segments if Lowe's requests a specific reference qualifier for carton IDs.

Q: I received a 997 reject — where do I start troubleshooting?

Start by reading the 997 functional acknowledgment. Map the functional group and transaction control numbers from the 997 to the original 856. If the 997 indicates syntactic errors, correct ISA/GS/ST control numbers, delimiters, and segment terminators. If the 997 indicates semantic issues, check HL hierarchy, required N1 qualifiers, and missing required segments like BSN or PRF.

Q: Does Lowe's require a PO number at the order HL level?

Yes. Include the PO number using PRF at the order-level HL so Lowe's can match the ASN to the PO. If Lowe's cannot match by PO, receiving and invoice reconciliation will fail.

Q: How can PlainEDI help with Lowe's 856 compliance?

PlainEDI provides automated validations that check ISA/GS/ST control numbers, HL hierarchy integrity, required segment presence, segment counts, and common semantic rules (e.g., SCAC validation and required N1 qualifiers). Upload your 856 to PlainEDI to catch and fix errors before transmission.

Final CTA

Ready to validate and upload your Lowe's EDI 856 files? Use PlainEDI to run Lowe's-specific ASN checks, HL hierarchy validation, and CSV conversion before sending to Lowe's. Upload your ASN now to prevent rejections and reduce chargebacks.