VDA EDI Tools

Taking EDI Live with an Automotive OEM: A Project Checklist That Survives Reality

VDA EDI Tools Blog · 2026-11-13

Every EDI project plan looks the same on a slide: requirements, mapping, testing, go-live. Real projects fail in the gaps between those boxes - the guideline revision that arrived mid-mapping, the label printer that prints one digit short, the test file that passed because the tester was the same person who wrote the mapping. This checklist is organised around what actually has to be true at each gate, with explicit sign-off evidence, so a status meeting can ask “show me” instead of “are we done?”.

Gate 0 - Scope freeze (week 0)

Gate 1 - Codes and master data (week 1-2)

Gate 2 - Mapping complete, self-tested (week 2-4)

Gate 3 - Customer test phase (week 4-6)

Gate 4 - Pilot (week 6-8)

Gate 5 - Steady state and change management

The three timelines that actually slip

  1. Certificates and connectivity (OFTP2, AS2, provider onboarding) - external dependencies you cannot hurry by working weekends.
  2. Label printing alignment - the label system, not the EDI mapping, owns the GIN numbers; it is a different team, often with its own vendor and lead time.
  3. Test-file turnaround - each customer test cycle takes days of queue time on their side; build two extra cycles into the plan, because you will need them.

None of this is exotic - it is simply the discipline of evidence at every gate. The projects that slip are the ones where “done” meant “the mapper thinks it works”. The ones that ship on time can answer, for every gate: show me the file, show me the validation report, show me the written approval.

A note for small suppliers

If you are a tier-2 or tier-3 without a dedicated EDI team, compress - do not skip - the gates. Gates 0 and 1 become one phone call with your EDI provider who has done this OEM before and owns the code sheet. Gate 2 stays yours: run three realistic files through a structural validator and archive the reports. Gates 3 and 4 are unavoidable regardless of company size, but your provider usually fronts the customer test cycle, which removes most of the turnaround pain. The budget version of this checklist is still: pinned guideline version, written codes, three validated golden files, written customer approval, two clean pilot weeks. Everything else is optimisation.

← All articles