Lowe's Edi 855

What This Is

This guide covers the Lowe's-specific processing of X12 EDI 855 Purchase Order Acknowledgments. An EDI 855 is the supplier's response to a retailer purchase order (EDI 850). Lowe's requires timely, accurate 855 acknowledgments to confirm acceptance, rejections, or changes to ordered items. The 855 defines whether items are accepted as-is, accepted with changes (quantity, ship date), or rejected.

The goal of this guide is to give you concrete, repeatable procedures: how to read key segments in a Lowe's 855, map them to CSV for ERP/import, troubleshoot common rejection causes, and apply fixes before sending or ingesting. It includes realistic code examples, CSV output samples, and testing/validation steps you can implement immediately. References to retailer policy use the Lowe's "Last Updated" stamp: 2026-01-25 where relevant; verify portal specifics in Lowe's vendor portal for the latest penalty thresholds and program changes.

Who This Is For

This guide is for EDI developers, integration engineers, operations teams, and supply chain specialists who are responsible for receiving, validating, converting, or troubleshooting Lowe's EDI 855 acknowledgments. If you automate order acknowledgments into an ERP, WMS, or drop-ship system, this guide gives the actionable details you need.

Key Segments Explained

Below are the segments you will use most when processing a Lowe's EDI 855. Each section explains the segment purpose, required elements for Lowe's processing, typical values, and why errors occur.

• ST — Transaction Set Header

  Purpose: Marks the start of the 855 transaction set and contains the transaction set identifier code and control number. For an 855, ST01=855. Lowe's systems rely on ST02 to match the trailer SE02 for set-level consistency.

  Why errors occur: Mismatched ST/SE control numbers, missing ST, or wrong transaction set ID (e.g., sending 860 instead of 855) will lead to functional rejections (997) or automated routing failures.

• BAK — Beginning Segment for Purchase Order Acknowledgment

  Purpose: Indicates the acknowledgment type (acceptance, rejection, etc.), the referenced PO number, and acknowledgment date. Key elements: BAK01 - Acknowledgment Type Code; BAK03 - Purchase Order Number; BAK04 - Date.

  Why errors occur: Wrong acknowledgment type codes or missing PO numbers cause Lowe's to treat the acknowledgment as invalid. Lowe's expects the PO number to match an existing EDI 850 in their system (Last Updated 2026-01-25).

• N1 — Name (Buyer/Seller)

  Purpose: Identifies parties: buyer (Lowe's), seller (vendor). Use the correct entity identifiers and qualifier codes (N101 = entity ID code like BY buyer, ST ship-to). Lowe's expects consistent vendor identifiers matching their vendor master file.

  Why errors occur: Wrong or mismatched vendor numbers create routing errors and vendor master mismatches. Lowe's rejection rules enforce N1 consistency with PO data (verify vendor portal for details, 2026-01-25).

• ACK / PO1 — Line Item Acknowledgment

  Purpose: Line-level acceptance/rejection. For 855s you typically see a PO1 line followed by an ACK segment (Acknowledgment). ACK01 is the Acknowledgment Code (IA = Item accepted, IP = Item accepted with change, RE or RA = Rejected), ACK02 is quantity accepted, and ACK05 is date (new ship/deliver date).

  Why errors occur: Incorrect ACK codes, inconsistent quantities (ACK02 not matching your system's available inventory), or missing date formats cause operational mismatches. Lowe's enforces timely acknowledgments, and late or missing 855s may trigger chargebacks or non-compliance reports (see penalties note referencing 2026-01-25).

• CTT and SE — Transaction Totals and Trailer

  Purpose: CTT carries the line item count for validation; SE ends the transaction and repeats the segment count and control number. Lowe's automatic parsing validates CTT counts against the number of PO1 loops; SE control must match ST.

  Why errors occur: Incorrect line counts, missing SE, or mismatched control numbers produce functional rejections (997) and automated reconciliation failures.

Example EDI Snippet

Below is a real-world 855 snippet representative of Lowe's PO acknowledgment. The snippet uses common delimiters: element *, segment terminator ~. Line-by-line annotations follow.

ST*855*0001~
BAK*AC*001*PO1234567*20260120~
REF*IA*L00012345~
N1*BY*LOWE'S COMPANIES INC*92*1000001~
N1*SU*ACME SUPPLY CO*92*VEND1234~
PO1*1*10*EA*15.00*VN*12345*UP*000123456789~
ACK*IA*10*EA***20260125~
PO1*2*5*EA*8.50*VN*54321*UP*000987654321~
ACK*IP*5*EA***20260201~
CTT*2~
SE*11*0001~

Line-by-line explanation:

• ST*855*0001~ — ST01 is 855 (PO Acknowledgment); ST02 control number 0001. This must match SE02.
• BAK*AC*001*PO1234567*20260120~ — BAK01=AC (ack type: Accept with Changes or Acceptance Code depending on implementation), BAK03=PO1234567 is the referenced PO, BAK04=20260120 is ack date (YYYYMMDD in this example).
• REF*IA*L00012345~ — REF used for internal identifiers (e.g., Lowe's internal allocation). REF qualifier IA is illustrative; ensure the qualifier conforms with Lowe's spec.
• N1*BY*LOWE'S COMPANIES INC*92*1000001~ — Buyer N1 with ID qualifier 92 and Lowe's entity number 1000001.
• N1*SU*ACME SUPPLY CO*92*VEND1234~ — Seller N1 with vendor ID matched to Lowe's vendor master.
• PO1*1*10*EA*15.00*VN*12345*UP*000123456789~ — PO1 line 1: 10 units of item identifier 000123456789, vendor SKU 12345, unit price 15.00.
• ACK*IA*10*EA***20260125~ — ACK for the previous PO1: IA = Item Accepted, quantity 10, unit EA, ACK date 20260125 (new commit/ship date).
• PO1*2*5*EA*8.50*VN*54321*UP*000987654321~ — PO1 line 2.
• ACK*IP*5*EA***20260201~ — ACK: IP = Item Accepted with Change (changed ship date to 20260201). The quantity remains 5.
• CTT*2~ — Two line items acknowledged.
• SE*11*0001~ — SE segment: 11 segments in this transaction; control number matches ST02.

CSV Output Example

This table shows a practical mapping from the 855 to a CSV format suitable for ERP import. Columns include PO-level and line-level fields. When converting, preserve the PO-level fields (BAK, N1 buyer/seller) on each line row.

Step-by-Step Conversion Process

1. Ingest and Delimit
   1. Read the raw EDI payload and detect delimiters from the ISA header (ISA16 indicates segment terminator by convention when not explicitly stated) or assume standard * and ~ if provided.
   2. Normalize line endings and ensure segment termination tokens are preserved.
2. Validate Envelope and Transaction Headers
   1. Confirm ISA/IEA and GS/GE envelopes if present. Ensure ISA control numbers and GS groups are consistent for message routing.
   2. Confirm ST01=855; if not 855, route to exception queue.
3. Parse PO-level Segments
   1. Extract BAK values (ack type, PO number, ack date) into PO-level variables.
   2. Extract N1 loops for buyer and seller IDs. Compare seller vendor ID to your vendor master and attach vendor metadata.
4. Parse Line Items and ACKs
   1. For each PO1 loop, parse the line number, quantity ordered, unit, and SKU identifiers.
   2. Immediately consume the next ACK segment that corresponds to the PO1. Map ACK01 to an acknowledgment status field and ACK02 to quantity acknowledged.
   3. Apply business rules: if ACK01 indicates rejection, set an alert and route to the operations team.
5. Reconcile Totals and Control Counts
   1. Check the CTT line count equals the number of PO1 loops parsed. If mismatch, reject or flag for manual review.
   2. Confirm ST02 equals SE02.
6. Transform to CSV and Enrich
   1. Emit a CSV row per PO1/ACK combination using the mapping table above. Include PO-level fields on each row for clear import.
   2. Enrich CSV with your ERP’s internal vendor ID and GL coding. If ACK indicates changed ship date, map to your scheduling fields.
7. Validate Business Rules and Submit
   1. Run validation rules: negative quantities, unsupported unit of measure, or SKU not found in master must be blocked.
   2. Upload or deliver final CSV to downstream systems. Use PlainEDI for validation and conversion to reduce manual errors — PlainEDI validates ST/SE counts, CTT totals, and required elements.

Common Errors and Fixes

• Error: Mismatched ST/SE control numbers (Functional Rejection) — Solution: When a 997 indicates SE02 != ST02, re-generate the 855 with matching control numbers. Use your EDI engine to auto-sync ST/SE across generation. PlainEDI's validation blocks ST/SE mismatches during upload to /upload.
• Error: Missing BAK PO Number (Validation Fail) — Solution: Ensure BAK03 contains the same PO number as the originating 850. If your system extracts PO from a different segment, update mapping to prefer BAK03. Re-submit with corrected BAK.
• Error: ACK codes not recognized by Lowe's (Routing Failure) — Solution: Replace non-standard acknowledgment codes with Lowe's approved codes (e.g., use standard X12 ACK values like IA, IP, RE). Validate codes against Lowe's spec; if unsure, consult Lowe's vendor portal (Last Updated 2026-01-25).
• Error: Line count (CTT) mismatch — Solution: Recount PO1 loops and ensure you are not missing conditional loops. Some implementations include PO1s without ACKs — ensure your parser associates ACKs correctly. Use CTT value as final check and reject if inconsistent.
• Error: Vendor ID mismatch in N1 — Solution: Confirm vendor ID qualifier and ID match Lowe's vendor master. If your vendor has multiple IDs, map alternate IDs into your vendor master to allow for Lowe's 92 qualifiers. Update your EDI translation rules to map the incoming N1 92 to internal vendor records.
• Error: Date format inaccuracies (YYYYMMDD vs MMDDYYYY) — Solution: Standardize date parsing to ISO (YYYYMMDD) as Lowe's accepts that format for 855 date elements. Convert dates during ingestion and validate with regex before transformation.

Related Resources

For related Lowe's and EDI topics, see these guides:

• reading Lowes EDI files
• Lowes EDI 850 (Purchase Orders)
• reading 997 functional acknowledgments
• resolving EDI 997 rejection codes
• understanding EDI X12 delimiters and structure

Why These Errors Happen (Root Causes)

Understanding WHY errors occur is essential to prevent recurrence.

• Human data-entry mistakes in the vendor master cause N1/vendor ID mismatches; automate vendor mapping to remove manual errors.
• Incorrect serialization of segment counts and control numbers is usually a defect in the EDI generator; implement unit tests to assert ST/SE and CTT counts pre-send.
• Non-standard acknowledgment codes or custom qualifiers occur when suppliers reuse internal codes; standardize to X12 codes and document mapping rules.
• Late acknowledgments stem from slow internal order processing — create SLA-based workflows to ensure 855s are sent within retailer-specified timeframes. Lowe's enforces compliance policies (refer to vendor portal; last updated 2026-01-25).
• Date format mismatches happen when systems default to locale-specific formats; normalize all EDI dates to X12 standard YYYYMMDD during generation.

Case Study: Resolving a Persistent Line-Level ACK Discrepancy

Problem: A vendor was receiving chargebacks because Lowe's reported differences between acknowledged quantities and shipped quantities. Investigation showed the vendor's EDI generator emitted ACK02 as a free-form decimal (10.0) and their ERP expected integer counts.

Fix implemented:

1. Updated the EDI generator to cast quantities to integer for unit items and to two decimal places for weight-based items using PO1 UOM.
2. Added validation in the conversion pipeline to reject ACK quantities that are negative or zero and to flag decimals when UOM=EA.
3. Integrated PlainEDI validation in pre-send testing to catch UOM/quantity mismatches. PlainEDI's pre-validation blocked the problematic 855 files and returned actionable error messages (ST/SE mismatch, invalid ACK02 format).
4. After deployment, the vendor's chargebacks stopped and operational reconciliation time reduced by 70% (internal metric).

PlainEDI Validation Features That Prevent Common Lowe's 855 Errors

Use PlainEDI to automate pre-ingest checks. PlainEDI performs:

• ST/SE and GS/GE control number validation
• Segment presence validation (BAK, PO1, ACK, CTT required in Lowe's profile)
• Element validation (date formats, numeric types, qualifier codes)
• Vendor ID matching rules to your configured vendor master

These validations prevent the most common functional rejections and operational chargebacks when used before production submission.

Common Compliance Notes and Penalties (Lowe's)

Lowe's enforces acknowledgment and ASN accuracy as part of its vendor compliance programs. Retailers typically assess penalties for missing or late 855 acknowledgments, inaccurate ACK codes, and ASN/ASN timing mismatches. The retailer policy landscape was last updated 2026-01-25; verify current penalty amounts and thresholds in the Lowe's vendor portal. Typical penalty types include OTIF-related deductions, ASN accuracy penalties, and chargebacks for incorrect shipments.

FAQ

Q: What is EDI 855?

The EDI 855 is the Purchase Order Acknowledgment transaction set used to acknowledge receipt of an EDI 850 Purchase Order. It indicates acceptance, rejection, or acceptance with changes at both PO and line levels.

Q: Which segments are required for Lowe's 855?

Required segments include ST (855 header), BAK (beginning acknowledgment with PO number), N1 loops for buyer/seller identification, PO1 for line items paired with ACK segments for line-level acknowledgment, CTT for line counts, and SE to close the transaction. Validate these before sending.

Q: How should dates be formatted in Lowe's 855?

Use X12 standard date format YYYYMMDD in date-bearing elements (e.g., BAK04, ACK05). Normalize dates to ISO during generation to avoid locale issues.

Q: What ACK codes should I use in ACK01?

Use standard X12 acknowledgment codes such as IA (Item accepted), IP (Item accepted with change), and RE or RA for rejected items per your agreed code list. Confirm Lowe's accepted code list on their vendor portal (Last Updated 2026-01-25).

Q: How do I map an 855 to my ERP?

Map PO-level fields (BAK, N1 buyer/seller) to PO header fields in the ERP and map each PO1/ACK pair to a line row. Include vendor ID, line number, item identifier, acknowledged quantity, unit of measure, ack code, and ack date. Emit one CSV row per line and include PO header fields on each row.

Q: What should I do if Lowe's returns a 997 rejection?

Review the 997 functional acknowledgment to identify which segment or element caused the rejection (ST/SE mismatch, missing required segment, invalid element). Correct the source EDI file, re-run validation with PlainEDI, and re-submit the corrected 855.

Q: Can I send combined acknowledgments for multiple POs in one 855?

Yes, you can include multiple BAK/PO1 loops within a single 855 transaction set as long as enveloping (ST/SE counts) and CTT counts are correct and Lowe's supports batched acknowledgments under their current trading partner agreement. Check the Lowe's vendor portal for batching rules last updated 2026-01-25.

Q: How do I prevent chargebacks related to 855 errors?

Automate pre-send validation (ST/SE, CTT, vendor ID, ACK codes, date formats), integrate with your vendor master for N1 validation, and use a tool like PlainEDI to block invalid files. Also implement SLAs for sending 855 acknowledgments within Lowe's required windows; verify SLA specifics on Lowe's portal.

Final Notes and Next Steps

This guide gave you segment-level knowledge, parsing examples, CSV mappings, and remediation steps specific to Lowe's 855 Purchase Order Acknowledgment. Implement these checks in your EDI translation layer, and use the provided examples to build unit tests that assert ST/SE, CTT, N1 vendor mapping, and ACK code validity.

Ready to validate and convert your Lowe's 855 files now? Upload a sample to PlainEDI for automated validation, error reporting, and CSV conversion.