Order-to-cash
All example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment
- 856 Ship Notice / Manifest (ASN)
- 810 Invoice
Plan your Home Depot EDI integration: the trading relationship, required documents, source system and business responses. Start with the current partner guide and sample files.
Implementation guide
Plan the business records your ERP or warehouse needs to exchange with Home Depot, using the retailer examples below.
A verified document list for Home Depot is not available here. These are planning examples; confirm the required documents with the partner before implementation.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 850 Purchase OrderPlanning example; partner requirement unconfirmed | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 860 Purchase Order Change Request Buyer InitiatedPlanning example; partner requirement unconfirmed | buyer order-change request original purchase order, change revision and affected line |
|
| X12 855 Purchase Order AcknowledgmentPlanning example; partner requirement unconfirmed | purchase-order response original purchase order, response revision and order line |
|
| X12 856 Ship Notice ManifestPlanning example; partner requirement unconfirmed | shipment notice (ASN) shipment, order, package and item references |
|
| X12 810 InvoicePlanning example; partner requirement unconfirmed | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
| X12 820 Payment Order Remittance AdvicePlanning example; partner requirement unconfirmed | payment or remittance record payment reference, invoice references and amounts applied |
|
Ask Home Depot for the supplier or customer account, business unit, implementation guide and testing contact. Record what still needs confirmation before work starts.
Start with purchase order or sales order, buyer order-change request, purchase-order response. 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.
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 Home Depot production handoff and save the results of each approved test.
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.
Use these retailer examples to plan the exchange. Confirm which documents Home Depot requires for your account. Obtain the current partner guide before mapping fields.
Document flow
Where each document sits in its trading cycle, based on the transaction sets a retailer typically trades. Confirm the current Home Depot requirements with the partner. These are example relationships; the trading agreement determines the required sequence.
Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.
Check your eligibility for the EDI migration fundAs 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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Related references
Compare document requirements for similar business processes.
Showing 21 of 48 references
Browse the full directoryFAQ
This entry does not include a verified Home Depot document list. The suggested X12 850 Purchase Order, 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 documents are planning examples; their use by the partner is unconfirmed. Request the current partner guide and sample exchanges before implementation.
Obtain the business-unit name, supplier/customer number, implementation guide and transport contact from Home Depot. Confirm the connection method with the partner’s EDI contact.
For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 860 Purchase Order Change Request Buyer Initiated, use original purchase order, change revision and affected line. Use the partner guide to locate these values and check their allowed formats.
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.
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.