How to Onboard with a New Retailer: A Step-by-Step Guide

You’ve landed a new retail account. The buyer is ready, the product is ready, and now there’s a gate between you and your first purchase order: EDI setup and certification. The process looks straightforward on paper — six steps, follow the guide, go live. In practice, first-time suppliers hit predictable walls at steps three through five that add weeks to the timeline, and those walls are where the useful information lives.

Step 1: Get the Vendor Compliance Guide

Every major retailer publishes a vendor compliance manual — sometimes called a routing guide or supplier handbook. Request it from your buyer or find it on the retailer’s vendor portal. This document contains every EDI, labeling, packaging, and shipping requirement the retailer enforces. Read it before you do anything else, because every subsequent step references requirements defined in this guide.

Step 2: Register for the Vendor Portal

Most retailers have a self-service vendor portal (Walmart’s RetailLink, Target’s Partners Online, Home Depot’s EDI portal). Register early — portal approval is a manual review process on the retailer’s side, and it can take several business days. The most common mistake here is treating registration as a quick admin task and doing it late, then discovering that the EDI connection testing step (Step 5) can’t begin until portal access is approved. Start registration the day you sign the vendor agreement, not the day you’re ready to test.

Step 3: Configure Your EDI Connection

This is where first-time suppliers lose the most time. You need to establish a connection method — either AS2 (direct, encrypted, certificate-based) or VAN (intermediary network that routes your documents). Many major retailers (Walmart, Amazon, Target) mandate AS2, which means you need an AS2 server with digital certificates installed, or a managed EDI provider that maintains the connection on your behalf.

What goes wrong: AS2 setup involves exchanging digital certificates with the retailer’s EDI team, configuring connection endpoints, and verifying bidirectional transmission. First-time suppliers often assume their IT team can handle this, then discover that their IT team has never set up an AS2 connection before — certificate exchange takes multiple rounds, endpoint configuration has retailer-specific quirks, and the testing process to verify the connection works in both directions can stretch across a week of back-and-forth. The retailer’s EDI team has a queue of other vendors they’re onboarding simultaneously, so each round of "your certificate didn’t match" or "the endpoint returned an error" is gated by their response time, not yours. If you’re using a managed EDI provider, this step is dramatically faster because they’ve already established connections with every major retailer and can skip the certificate exchange and endpoint debugging entirely. For the full testing process, see our EDI certification guide.

Step 4: Set Up Required Transaction Sets

At minimum, you’ll need: 850 (inbound PO), 855 (outbound acknowledgment), 856 (outbound ASN), 810 (outbound invoice), 997 (functional acknowledgment, both directions). The transaction set list itself is standard across retailers — what’s not standard is the data mapping within each document.

What goes wrong: "Setting up transaction sets" sounds like configuration, but it’s actually data mapping — translating the fields in your ERP or order management system into the specific segment and element positions the retailer’s system expects. Every retailer maps EDI fields differently. Walmart’s 856 ASN expects pack structure in a specific hierarchical order; Target’s expects it slightly differently; Home Depot has retailer-specific reference qualifiers in the 850 that your system needs to recognize and route correctly. First-time suppliers often build a generic mapping that transmits successfully but fails the retailer’s format validation — the document arrives, but the data is in the wrong segments, or required fields are missing, or the pack hierarchy is structured incorrectly. The retailer’s compliance team rejects the test transaction, and you’re back to revising the mapping. This cycle — submit, get rejected, revise, resubmit — can repeat three or four times if you’re doing the mapping yourself without retailer-specific experience. A provider who’s already mapped documents for that retailer submits clean test transactions on the first round, because they know exactly which segments and elements that retailer’s system expects.

Step 5: Testing & Certification

Retailers require you to send test transactions before going live. Most require multiple test scenarios: single-line PO, multi-line PO, partial shipment, and sometimes dropship or direct-to-store scenarios. The retailer’s compliance team reviews each test transaction for format accuracy, field completeness, and label compliance.

What goes wrong: Two things. First, test transactions that fail format validation send you back to Step 4 — each rejection is a revision cycle that depends on the retailer’s review queue turnaround, which you can’t control. A test transaction submitted on Monday might not get reviewed until Thursday, and if it fails, you revise and resubmit and wait another several days. Second, label review is a separate gate — you submit physical sample GS1-128 carton labels for the retailer’s compliance team to inspect. Label rejections are common for first-time suppliers because zone content, barcode format, and field placement have retailer-specific requirements that aren’t always obvious from the compliance guide. A label that looks correct to you can fail because a field is in the wrong zone position or an Application Identifier is missing. Each label revision is another review cycle. The testing phase is where the timeline stretches most unpredictably, because it’s gated by the retailer’s review queue and by how many revision cycles your test transactions and labels need before they pass.

Step 6: Go Live

Once certified, your first live PO can arrive at any time. Have your team ready and your processes documented — the retailer doesn’t coordinate a specific go-live date with you. The first live PO is where you discover whether your production transactions work as well as your test transactions did, so monitor your first few shipments closely.

A Realistic Timeline

The entire process typically takes 2–6 weeks from portal registration to first live PO. In the best case — where portal approval is fast, the connection is already established through a managed provider, test transactions pass on the first round, and labels are approved without revision — it can be compressed to closer to two weeks. Suppliers who attempt the process without retailer-specific EDI experience, who handle AS2 setup and transaction mapping themselves, and who go through multiple test revision cycles routinely see the timeline stretch to six weeks or more. The variable isn’t the retailer’s process; it’s how many revision cycles your test transactions and labels need before they pass, and those cycles are almost entirely determined by whether you have retailer-specific mapping experience or are learning the format as you go.