EDI basics · October 25, 2026

EDI Onboarding Checklist: From First PO to Production

A step-by-step EDI onboarding checklist — ISA IDs and qualifiers, connectivity, test scripts, parallel running, go-live, and the stalls that add weeks.

Every EDI onboarding is the same project wearing a different retailer's logo. The steps below are the whole thing, in order, with the stalls flagged — because the calendar is rarely lost to hard problems. It's lost to waiting on the wrong person for a piece of information nobody wrote down.

1. Collect the identities

Before anything technical, both sides need addressing:

  • Your ISA ID and qualifier. The interchange address on every document you trade. Common qualifiers: 01 (DUNS number), 12 (phone), ZZ (mutually defined). Pick one, use it consistently across partners.
  • The partner's ISA ID and qualifier, plus their GS application codes — from their companion guide or EDI team.
  • Your vendor number in the partner's system. Every downstream document must echo it, and onboarding cannot start until purchasing has issued it.

Stall to avoid: waiting a week to learn the partner's test and production IDs differ. Ask for both up front.

2. Establish connectivity

AS2, SFTP, or a VAN — the partner's choice, not yours. AS2 means certificate exchange and MDN configuration; SFTP means credentials and folder conventions; VAN means interconnect setup. With EDISQ this layer is operated for you as part of the service, whichever transport the partner mandates, so the checklist item is "confirm the connection test passed," not "become an AS2 administrator."

3. Map the documents

Get the partner's companion guides for each required transaction — typically 850 in, 855, 856, and 810 out. The map is where their spec meets your data: item cross-references, ship-to location tables, required REF segments, allowance handling. Certified pre-built maps collapse this step from weeks to configuration; what remains is loading your item and location data, which no vendor can do without you.

Stall to avoid: item data. An 850 arrives with a UPC you never loaded and the whole flow stops. Load the full catalog cross-reference before testing, not the three items you expect them to order first.

4. Run the test scripts

Partners test to script: they send scenario documents and expect exact responses. A typical script covers a plain PO, a multi-store PO, a change (860), and your outbound responses — with 997 acknowledgments flowing both directions within minutes, automatically. Work the scenarios until each round-trips clean against the companion guide. This is also where ASN structure gets proven: hierarchy shape, SSCC-18 serials, label parity.

Stall to avoid: the partner's testing queue. Many majors batch certification reviews weekly. Submit complete, correct test results the first time — a failed cycle can cost seven calendar days waiting for the next review slot.

5. Parallel-run the first orders

Go-live is not a light switch. For the first live orders, process the EDI document as the system of record while someone checks it against the old channel — the portal download, the emailed PDF. You are verifying quantities, prices, ship-tos, and dates survived the mapping. One or two clean cycles is usually enough.

Stall to avoid: running parallel forever. Set an exit date. Dual processing is where re-keying errors sneak back in.

6. Go live with monitoring

Turn off the old channel and put the automation on watch: acknowledgment tracking on every outbound document (a missing 997 means retransmit today, not at month-end), ASN transmission tied to ship-confirm, and alerting on documents that fail validation before they reach the partner. Onboarding ends when nobody checks a portal anymore.

The meta-checklist

For each new partner: IDs exchanged, connectivity confirmed, companion guides in hand, item and location cross-references loaded, test script passed, parallel run complete, monitoring on. Seven boxes. The partner's own required document set and typical timeline are listed on their page in our partner directory.

EDISQ was built to make this list short: connectivity operated for you, 2,200+ partners with maps ready, a sandbox that replays partner test scenarios, and per-document pricing with the first 25 documents each month free — so onboarding costs nothing until documents actually flow.

FAQ

How long does EDI onboarding take?

The EDI-side work — IDs, connectivity, mapping, testing — typically takes days with certified maps. The overall calendar is set by the partner's paperwork and testing queue, which can run two to eight weeks.

What is an ISA ID and qualifier?

The addressing pair on every X12 interchange. The qualifier says what kind of identifier follows (01 for DUNS, ZZ for mutually defined, 12 for phone), and the ID is your address. Both sides must agree on them before any document flows.

What does EDI testing actually involve?

The partner sends scripted test documents and expects specific responses: correct 997s, valid 855s and 856s, matching 810s. You pass when every scenario round-trips per their companion guide.

Can I run EDI and my old process in parallel?

Yes, and you should for the first orders — process the EDI document as primary while checking it against the portal or email version until you trust the flow. Then turn the old channel off deliberately.