How to Set Up EDI with Home Depot (Step by Step)

Home Depot is really three EDI programs wearing one document set — stock replenishment, special order, and dropship COM — and a setup that treats them as one program is the root of most first-quarter pain. The build itself is quick (1–3 days with certified maps); the craft is in making it program-aware from the start. Here's the path for Home Depot, with the requirement detail in the Home Depot EDI requirements guide.

What you need before the technical work

From Home Depot: your vendor agreement, vendor identifiers, and — critically — clarity on which programs you're enrolled in, because stock, SO, and dropship carry different rules through identical-looking documents. From your own house: an item file ready to cross-reference, and a warehouse process that can produce carton-level pack data, since Home Depot receiving validates UCC-128 labels against your ASN.

Connect the ERP and declare the programs

Attach your business system — NetSuite, Epicor Kinetic, or another of the 30+ supported platforms — and configure the connector per program. The distinction matters immediately on inbound orders: stock POs may arrive with SDQ segments packing multi-store quantities into single lines, which must explode into store-level allocations before anything is picked. Special order POs carry customer detail that has to survive the trip through your system and reappear on the 856 — that round-trip is how Home Depot ties your shipment to a waiting customer.

Build the cross-references

Three tables run the relationship: items (Home Depot's identifiers against your SKUs), ship-tos (stores and DCs, since both flows exist), and program assignment per order type. While loading them, encode the hierarchy rules too — store-direct and DC shipments follow different ASN structures at Home Depot, and the map should choose based on the order, not a global default.

Test each program separately

This is where Home Depot setups earn their reliability. Run a stock 850 with SDQ distribution through to allocation. Run a special order and verify the customer detail lands on the ASN untouched. Run each flow's 856 and validate its hierarchy against the right rule set, with MAN serials matching the labels your warehouse would actually print. A test matrix organized by program catches the class of bug that generic happy-path testing sails past — the same class that later becomes deductions under THD supplier compliance, as covered in How to Avoid Home Depot EDI Chargebacks.

Go live and keep two gauges in view

Certification with pre-validated maps is normally one pass. In production, watch the acknowledgment stream — every transmission should return a 997, and silence means resend now — and watch ASN generation latency against ship-confirm, because label/ASN agreement plus timely transmission is nearly the whole of Home Depot compliance.

How the 1–3 days actually divide

For planning purposes: the connection and ERP attachment are measured in hours, the cross-references take as long as your data quality allows, and program-aware testing fills whatever remains — which is the right allocation, since testing is where multi-program setups either earn confidence or defer problems. Run the Home Depot paperwork track in parallel rather than in sequence; partner-side onboarding has its own clock, and the technical build should be waiting on Home Depot rather than the other way around. If you trade other big-box hardware channels, note that the SDQ-explosion and label-lineage work you do here transfers almost unchanged.

Operating cost

The meter is per document and starts at zero: 25 documents monthly free, then from $0.50 each, tapering to $0.10 at the highest tier under marginal-tier billing. Program-specific maps, connectivity, sandbox, and monitoring are inside the rate rather than adjacent to it — there is no setup charge, and adding Home Depot next to your other retailers is a flat $50/month as an additional live partner, not a project. Details at pricing.

FAQ