Got Your Retailer's EDI Implementation Guide? Here's Exactly What Happens Next.

You got approved as a vendor. Walmart, Target, Home Depot, Kroger, Costco, Sam’s Club, Lowe’s, Chewy, Wayfair — doesn’t matter which. You’re in.

Then they sent you a document. It might be called an “EDI Implementation Guide,” an “EDI Specification,” a “Supplier Onboarding Guide,” or just a PDF with a title like “850 Transaction Specification for New Suppliers.” It’s usually 50 to 300 pages long.

Most new vendors open it, scroll through three pages of segment tables and qualifier codes, and close it.

That’s the right instinct. Here’s what it actually contains and what you do with it.

What’s in an EDI Implementation Guide

Every implementation guide covers the same territory, though the format varies by retailer:

1. ISA sender and receiver IDs These are the envelope addresses for your EDI transactions. Every EDI file starts with an ISA (Interchange Control Header) segment. The retailer’s ISA06 (their sender ID when they send you a PO) and ISA08 (their receiver ID when you send them transactions) are in the guide. You need these exact values — no guessing.

2. GS Application IDs The GS (Functional Group Header) segment has its own sender/receiver IDs — GS02 and GS03. These are different from the ISA IDs. Both sets need to be correct or the trading partner’s system won’t accept your transactions.

3. Transaction specifications The bulk of the document. For each transaction type — 850 Purchase Order, 856 Ship Notice, 810 Invoice, 997 Functional Acknowledgment — the guide specifies which segments are required, which are optional, and what values go in each element. This is your mapping blueprint.

4. Test endpoint information Separate from production. The retailer maintains a test environment where you submit transactions before they’ll let you go live. The guide includes the test SFTP address, AS2 endpoint, or VAN routing information you need to connect.

5. Certification timeline and contacts How long the test window is, who to contact at the retailer’s EDI team, and what “passing” looks like. Some retailers have a specific test transaction suite you have to submit in sequence. Others have a more flexible window.

6. Appendices and code tables Qualifier codes, unit of measure codes, routing codes, carrier SCAC codes. Reference material you’ll use constantly during mapping.

The 4 Things You Need Before You Start

The implementation guide is one of four things. You need all four before setup can begin:

1. The implementation guide itself. Obvious, but confirm you have the current version. Some retailers update their specs annually. Walmart’s 856 requirements have changed over the years; building against an old spec wastes your certification window.

2. Your assigned ISA IDs. When you registered as a supplier, the retailer’s EDI team issued you an EDI sender ID. It’s in their system. You need to know your own ID — not just theirs. If you don’t have it, contact their EDI onboarding team and ask.

3. Your connection credentials. For SFTP: the test server address, your username, your password or SSH key. For AS2: your AS2 ID (assigned by the retailer), your AS2 certificate, and their public certificate. For VAN: your VAN account number and the retailer’s VAN routing ID.

If you’re setting up SFTP, this is usually a username/password pair the retailer issues. If you’re setting up AS2 — which Target, Kroger, and increasingly other retailers prefer — there’s a certificate exchange step before you can even connect.

4. Your product catalog. You need a source for your item data — UPC/GTIN, item descriptions, pack quantities, dimensions and weights (for the 856 at carton level), and your internal item numbers. The maps you build pull this data from somewhere. “Somewhere” needs to be defined before you start.

The Test vs. Production Process

Test phase: You connect to the retailer’s test environment and submit transactions. The retailer’s system validates your EDI against their specification and returns 997 Functional Acknowledgments — or error codes when something fails.

Common first-pass failures:

• Wrong ISA or GS qualifier codes
• Missing mandatory segments
• Incorrect qualifier values in DTM (date) or REF (reference) segments
• 856 loop hierarchy errors
• SSCC-18 label format issues (Target, Walmart, and others)

You fix, resubmit, iterate. Some retailers have an automated validator that gives you instant feedback. Others require their EDI team to review submissions manually, which adds turnaround time.

Certification sign-off: Once your test transactions pass, the retailer’s EDI team reviews and signs off. For Walmart, this goes through Retail Link. For Target, through their supplier portal. For Home Depot and Costco, through their supplier onboarding teams.

Certification sign-off is the gate. You cannot go live without it. Some retailers require specific test transaction sequences — one complete order cycle (850 → 856 → 810 → 997) with correct values before they’ll approve.

Production go-live: After certification, you update your connection to point at the production endpoint instead of test, and you’re live. The first real PO comes in as an 850. You ship, send your 856, send your 810. The retailer sends a 997 confirming receipt.

The first live cycle always feels like a milestone. It is.

How Long This Takes

Be realistic:

• Walmart: 3–6 weeks from starting setup to certification sign-off
• Target: 4–6 weeks; add time if the AS2 certificate exchange takes multiple rounds
• Home Depot: 4–8 weeks; they certify each document type separately
• Kroger: 3–5 weeks; their test validation is thorough
• Costco: 4–6 weeks
• Sam’s Club, Lowe’s, Best Buy, Dollar General, Dollar Tree, CVS, Walgreens, Meijer, Albertsons, Publix: 3–6 weeks depending on their current onboarding volume

These timelines assume no major rework. If your first 856 submission has structural errors and takes two rounds of fixes, add a week. If your AS2 certificates don’t exchange cleanly, add another.

How TebcoForge Does It

When you hand TebcoForge your implementation guide and the other three items above, here’s what happens:

Week 1: We build your maps. 850 inbound processing, 856 outbound (carton level), 810 outbound, 997 auto-acknowledgment. We load them into EDIBridge — the platform we use for all managed customers.

Week 1–2: We set up your connection to the retailer’s test environment. SFTP credentials configured, AS2 certificates exchanged if applicable, VAN routing confirmed.

Weeks 2–5: We run the test transactions. We submit, review the 997 responses and any error feedback from the retailer’s system, and fix anything that doesn’t pass. We handle the communication with the retailer’s EDI support team.

End of certification window: Certification sign-off from the retailer. We switch your connection to production.

Go-live: You receive your first real 850. We’re available during the first live cycle to confirm everything’s flowing correctly.

After go-live, you have full visibility into your setup in EDIBridge. You can see every map, every transaction, every log. If Walmart updates their 856 spec six months from now, we update your maps. That’s part of the managed service.

If you want to run it yourself after seeing how it works, you can — EDIBridge supports self-service, and we built it so that managed-to-self-service transitions are clean.

The Common Mistake

The most common mistake new vendors make is waiting. You get the vendor approval, you sit on the implementation guide for two weeks because it looks intimidating, you finally reach out to an EDI provider, and now your buyer is asking for a go-live date you can’t hit.

The certification window is a scheduled commitment with your trading partner. Missing it means rescheduling — and some retailers put new suppliers in a queue that’s weeks long.

If you’ve got the guide, start now.

For a deeper look at how EDI requirements vary across major retailers before you start, read EDI Requirements Compared: Walmart, Target, Home Depot, Kroger, and Costco. If you want to understand how to read the spec documents themselves, How to Read a Trading Partner EDI Specification Document covers the mechanics.

Or contact TebcoForge and skip all of it. Give us the guide, we give you a go-live date.