--- title: "Lowe's EDI Integration | Stacksync" description: "Lowe's EDI: 7 listed document types, channel comparison, record mapping and validation guidance for your integration." canonical: https://www.stacksync.com/edi/lowes last_modified: 2026-09-15 --- # *Lowe's* EDI integration guide. Plan your Lowe's EDI integration using 7 listed document types across 2 channels. Compare channels, map business records and test the operational handoff. [Book an EDI demo](https://www.stacksync.com/book-a-demo) Explore EDI documents | | | | | --- | --- | --- | | Listed documents | 7 | Partner document references | | Listed channels | 2 | Lowe's (via Rithum) → Lowes | | Implementation | Plan | Map, validate and reconcile | ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Implementation guide ## Lowe's: EDI implementation plan Build a reliable EDI workflow for Lowe's. Use 7 document types across 2 channels to plan record mapping, prevent duplicate processing and reconcile results in your business systems. The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | [X12 850 Purchase Order](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-850-purchase-order) Listed on 2 channels: Lowe's (via Rithum), Lowes | **purchase order or sales order** buyer purchase order, order line and trading-party identifiers | Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. | | [X12 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-846-inventory-inquiry-advice) Listed on 2 channels: Lowe's (via Rithum), Lowes | **inventory availability record** item, location, quantity type and snapshot time | Distinguish on-hand, available and reserved quantities before publishing availability. Deliver an old snapshot after a new one and prevent stale stock from replacing current values. | | [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-860-purchase-order-change-request-buyer-initiated) Listed on 2 channels: Lowe's (via Rithum), Lowes | **buyer order-change request** original purchase order, change revision and affected line | Apply a quantity reduction to the existing order instead of creating another order. Test a cancellation arriving after allocation or shipment and route it to an exception owner. | | [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-855-purchase-order-acknowledgment) Listed on 2 channels: Lowe's (via Rithum), Lowes | **purchase-order response** original purchase order, response revision and order line | Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. | | [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-856-ship-notice-manifest) Listed on 2 channels: Lowe's (via Rithum), Lowes | **shipment notice (ASN)** shipment, order, package and item references | Reconcile item quantities through shipment, order and packaging levels against the physical shipment. Test split shipments for one purchase order and prevent the second ASN from replacing the first. | | [X12 810 Invoice](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-810-invoice) Listed on 2 channels: Lowe's (via Rithum), Lowes | **accounts-receivable or accounts-payable invoice** invoice number, purchase order and invoice line | Reconcile line amounts, allowances, charges and tax to the invoice total. Submit the same invoice twice and verify that it cannot create a second payable. | | [X12 820 Payment Order Remittance Advice](https://www.stacksync.com/edi/lowes/lowes/x12-820-payment-order-remittance-advice) Listed on 1 channel: Lowes | **payment or remittance record** payment reference, invoice references and amounts applied | Allocate a partial payment across several invoices and preserve the remaining balances. Keep receipt of remittance information distinct from confirmation that funds settled. | ### Implementation steps 1. #### Choose the trading account and channel Choose among Lowe's (via Rithum), Lowes. Confirm the business unit and account before copying a mapping from another channel. 2. #### Map records and assign owners Start with purchase order or sales order, inventory availability record, buyer order-change request. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event. 3. #### Test a complete exchange Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Lowe's production handoff and save the results of each approved test. 4. #### Check results after launch Match records between systems using buyer purchase order, order line and trading-party identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries. ### Go-live checklist - The required X12 documents, versions and sample files are agreed. - Sender and receiver IDs, test connections and production connections are agreed with the channel owner. - Delivery receipts, document validation and business responses have monitoring and a named owner. - Tests cover duplicates, partial processing and reconciliation with realistic business records. ### Related documents and resources - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [Evaluate your integration requirements](https://www.stacksync.com/blog/integration-evaluation-worksheet) **Sources.** Directory data as of 2026-05-07. Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) - [Lowe's document reference](https://www.orderful.com/network/lowes) Document catalog ## EDI documents listed for Lowe's 13 transactions across 2 channels. ### [Lowe's (via Rithum)](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum) 6 docs - [X12 850 Purchase Order](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-850-purchase-order) - [X12 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-846-inventory-inquiry-advice) - [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-860-purchase-order-change-request-buyer-initiated) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-855-purchase-order-acknowledgment) - [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-856-ship-notice-manifest) - [X12 810 Invoice](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-810-invoice) ### [Lowes](https://www.stacksync.com/edi/lowes/lowes) 7 docs - [X12 820 Payment Order Remittance Advice](https://www.stacksync.com/edi/lowes/lowes/x12-820-payment-order-remittance-advice) - [X12 860 Purchase Order Change Request Buyer Initiated](https://www.stacksync.com/edi/lowes/lowes/x12-860-purchase-order-change-request-buyer-initiated) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/lowes/lowes/x12-855-purchase-order-acknowledgment) - [X12 846 Inventory Inquiry Advice](https://www.stacksync.com/edi/lowes/lowes/x12-846-inventory-inquiry-advice) - [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/lowes/lowes/x12-856-ship-notice-manifest) - [X12 810 Invoice](https://www.stacksync.com/edi/lowes/lowes/x12-810-invoice) - [X12 850 Purchase Order](https://www.stacksync.com/edi/lowes/lowes/x12-850-purchase-order) Document flow ## Example document relationships for Lowe's Where each document sits in its trading cycle, based on the 7 document types listed for Lowe's across 2 channels. These are example relationships; the trading agreement determines the required sequence. ### Order-to-cash All example steps listed 1. [850 Purchase Order](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-850-purchase-order) 2. [855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-855-purchase-order-acknowledgment) 3. [856 Ship Notice Manifest](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-856-ship-notice-manifest) 4. [810 Invoice](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-810-invoice) ### Catalog & inventory Some example steps listed 1. 832 Price / Sales Catalog not listed for Lowe's 2. [846 Inventory Inquiry Advice](https://www.stacksync.com/edi/lowes/lowe-s-via-rithum/x12-846-inventory-inquiry-advice) 3. 852 Product Activity Data not listed for Lowe's - 810 Invoice — is listed on 2 of Lowe's's 2 channels - 820 Payment Order Remittance Advice — is listed on 1 of Lowe's's 2 channels - 846 Inventory Inquiry Advice — is listed on 2 of Lowe's's 2 channels - 850 Purchase Order — is listed on 2 of Lowe's's 2 channels - 855 Purchase Order Acknowledgment — is listed on 2 of Lowe's's 2 channels - 856 Ship Notice Manifest — is listed on 2 of Lowe's's 2 channels - 860 Purchase Order Change Request Buyer Initiated — is listed on 2 of Lowe's's 2 channels Network context ## Lowe's channel references for Rithum These network names are derived from the listed Lowe's channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method. ### Rithum 25 channels · 23 trading partners in the catalog Lowe's channel on this network: Lowe's (via Rithum) Most frequently listed documents - 850 25 ch - 856 25 ch - 846 24 ch - 810 20 ch - 870 10 ch Also listed with Rithum - [Staples Advantage](https://www.stacksync.com/edi/staples-adv) - [HD Supply Holdings, Inc.](https://www.stacksync.com/edi/hd-supply-commerce-hub) - [Men's Wearhouse via DSCO](https://www.stacksync.com/edi/mens-wearhouse) - [URBN](https://www.stacksync.com/edi/urbn) - [JOANN](https://www.stacksync.com/edi/joann) - [Michaels Stores](https://www.stacksync.com/edi/michaels-stores) LEGACY EDI MIGRATION FUND ## Still with a legacy EDI vendor? Ask about a contract buyout. Stacksync can buy out your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. Eligibility and terms are confirmed on a call. [Check your eligibility for the EDI migration fund](https://www.stacksync.com/book-a-demo) | | | | --- | --- | | | [Migrate from SPS Commerce](https://www.stacksync.com/sps-commerce-alternative) | | | Migrate from Cleo | | | Migrate from TrueCommerce | | | Migrate from OpenText | SECURITY ## Security teams trust Stacksync As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### SSO & SCIM Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more. ### Alerts Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more Related references ## Partners with related document listings Compare document requirements for similar business processes. [The Home Depot 48 docs · 11 channels](https://www.stacksync.com/edi/the-home-depot) [Nordstrom 28 docs · 8 channels](https://www.stacksync.com/edi/nordstrom) [JCPenney 25 docs · 20 channels](https://www.stacksync.com/edi/jcpenney) [Target 23 docs · 4 channels](https://www.stacksync.com/edi/target) [Macy's 17 docs · 5 channels](https://www.stacksync.com/edi/macys) [PetSmart 11 docs · 2 channels](https://www.stacksync.com/edi/petsmart) [Costco 55 docs · 12 channels](https://www.stacksync.com/edi/costco) [Walmart 32 docs · 8 channels](https://www.stacksync.com/edi/walmart) [Dillard's Department Stores, Inc. 30 docs · 3 channels](https://www.stacksync.com/edi/dillards-department-stores-inc) [Amazon 24 docs · 4 channels](https://www.stacksync.com/edi/amazon) [NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) [AAFES (Army and Air Force Exchange Service) 15 docs · 3 channels](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service) [Mountain High Outfitters 12 docs · 2 channels](https://www.stacksync.com/edi/mountain-high-outfitters) [Bealls Inc. 11 docs · 2 channels](https://www.stacksync.com/edi/bealls-inc) [Williams Sonoma 10 docs · 2 channels](https://www.stacksync.com/edi/williams-sonoma) [Evereve.com 10 docs · 2 channels](https://www.stacksync.com/edi/everevecom-evereve) [Chewy 10 docs · 2 channels](https://www.stacksync.com/edi/chewy) [Crate & Barrel 9 docs · 2 channels](https://www.stacksync.com/edi/crate--barrel) [Wayfair LLC 9 docs · 1 channel](https://www.stacksync.com/edi/wayfair-llc) [Jordan's Furniture 8 docs · 1 channel](https://www.stacksync.com/edi/jordans-furniture) [MSC Industrial Supply Co. 8 docs · 1 channel](https://www.stacksync.com/edi/msc-industrial-supply) [Browse the full directory](https://www.stacksync.com/edi) FAQ ## Lowe's EDI questions ### Which EDI documents are listed for Lowe's? X12 850 Purchase Order; X12 846 Inventory Inquiry Advice; X12 860 Purchase Order Change Request Buyer Initiated; X12 855 Purchase Order Acknowledgment; X12 856 Ship Notice Manifest; X12 810 Invoice; X12 820 Payment Order Remittance Advice. Confirm which documents, directions and versions apply to your account. ### How should I choose the Lowe's EDI channel? The directory lists 2 channels for Lowe's, including Lowe's (via Rithum), Lowes. Match the channel to your actual trading relationship and compare its document list before reusing a mapping. ### Which identifiers should the Lowe's mapping preserve? For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 846 Inventory Inquiry Advice, use item, location, quantity type and snapshot time. Use the partner guide to locate these values and check their allowed formats. ### Does a successful EDI receipt mean Lowe's accepted the business document? Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed. ### What should be tested before launching Lowe's EDI? Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch. ## Your last integration took months. Your next one takes a prompt. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)