Home Depot is one of the largest building supply chains in the world and by the list below they also have some large EDI requirements. If you go to Home Depot’s Supplier Center they list out all the EDI specifications and implementation guides to match Home Depot’s EDI requirements. Below I have listed the documents you may come across when trading with Home Depot:
EDI 204 - Load Tender
EDI 210 - Freight Invoice
EDI 214 - Shipment Status Invoice
EDI 315 - Ocean Shipment
EDI 810 - Invoice
EDI 812 - Debit / Credit Memo
EDI 816 - Store Listing
EDI 820 - Remittance Advice
EDI 850 - Purchase Order
EDI 852 - Point of Sale
EDI 856 - Advance Ship Notice
EDI 860 - Purchase Order Update
EDI 864 - Text Message
EDI 870 - Order Status Report
EDI 990 - Load tender Response
EDI 997 - Functional Acknowledgment
Looking at the list of documents the only ones on the list you may not understand and that have not been covered previously are the first 4: EDI 204 - Load Tender, EDI 210 - Freight Invoice, EDI 214 - Shipment Status Invoice and EDI 315 - Ocean Shipment. Odds are that you will not have to worry about these documents. These documents provide various details of shipments and are only exchanged between Home Depot and their Logistics partners.
When you formally sign with Home Depot, they will dictate which documents they would like to trade with you and you will need to communicate that information to your EDI provider and make sure it is a transaction set they have and support. This is a good time to explain the added value of eBRIDGE Software’s ePortal EDI Solution. Our Trading Partner Kits for ePortal provide you with all the documents that are required by a given trading partner. In the case of Home Depot, if they ask for only an 810 (Invoice) and 850 (Purchase Order) or they ask you for 10 different documents, the Home Depot Trading Partner Kit for ePortal will include them all.
For more information on our Home Depot Trading Partner kit or any other Trading Partner kit, feel free to leave a message here or contact me directly.
Thanks,
Jay
No comments:
Post a Comment