EDI Onboarding with a New Automotive Customer: A Practical Checklist
"Please set up EDI with us" usually arrives as a short email with a big PDF attached. This checklist is the distilled version of what happens next, in the order that wastes the least time.
Phase 1 - Collect the facts
- Get the plant-specific message implementation guides for every message in scope (usually 4984 inbound, 4987 outbound, invoicing later). The generic VDA recommendation is not enough.
- Identify the transport channel: OFTP2 direct, or an EDI service provider / VAN? Who pays?
- Collect codes: your supplier number, their plant codes, unloading points, dock codes - the values that go into NAD/LOC segments.
- Clarify label requirements: VDA goods tag (4902) version, printer, and who assigns label number ranges.
Phase 2 - Build the mapping
- Map your ERP fields to the guideline's segments - start with the mandatory set (BGM, the three DTM dates, NAD parties, weights, LIN/QTY).
- Decide the packaging model: how do your pallets and boxes map to CPS levels and PAC types?
- Build the label-number logic (
PCI/GIN) together with shipping - it must match the physical tags.
Phase 3 - Test
- Validate every test file structurally before sending it anywhere - a validator catches date formats, missing segments and broken control counts in seconds.
- Run the customer's official test phase: send test DESADVs against real delivery notes, receive test DELFORs.
- Print physical labels and have the customer scan-test them - a perfect message with an unscannable label still blocks the gate.
Phase 4 - Go-live
- Start with one plant / one material before the full rollout.
- Monitor the first weeks daily: rejections usually cluster in the first shipments.
- Keep the guidelines versioned - OEMs update them, and "we always did it this way" breaks silently after an update.
The traps that bite most suppliers
- Mapping to the generic VDA document instead of the OEM's own guideline.
- Forgetting that date/quantity formats are strict (
CCYYMMDD, numeric only, no German decimal comma). - Treating the test phase as a formality - it is where every assumption gets falsified for free.
- Label numbers that look right on screen but do not match what is printed on the goods tag.