BMW EDI Requirements for Suppliers: Messages, Labels and OFTP2 Transport
Winning a BMW Group contract comes with a second onboarding project that rarely fits on the same slide: EDI. The good news is that none of it is exotic. BMW, like the other German OEMs, runs on the standard German automotive EDI stack: VDA application guidelines layered over EDIFACT, moved over OFTP2. If you already supply Volkswagen, Mercedes-Benz, Audi or a German Tier-1, you own most of the machinery. This article maps which message serves which process, what you need on the transport side, and where new suppliers typically stumble. For anything plant-specific, the current BMW implementation guideline your buyer hands you always wins over general articles like this one.
The message chain, step by step
BMW's EDI flows follow the physical flow of parts, and each step has one message you need to handle well:
| Process step | Message | What you must get right |
|---|---|---|
| Forecast and call-off | VDA 4984 (DELFOR) | Consume the right schedule type, track cumulative quantities, and react to firm zones versus planning zones. |
| Sequenced JIT/JIS supply | VDA 4988 (DELJIT) | Only for lines running sequenced. Sequence number discipline is the whole game here. |
| Shipment notification | VDA 4987 (DESADV) | Send per shipment, on time, matching the labels on the boxes exactly. |
| Invoicing | VDA 4938 (INVOIC, self-billing) | You receive and verify, you do not send. Reconcile against your DESADV data. |
If you are a classic warehouse supplier, 4984 and 4987 carry almost all of the traffic and 4988 never appears. If you supply sequenced modules, 4988 becomes the message your production line listens to, and a missed or misnumbered sequence stops a car build, not a warehouse slot. Our VDA 4988 article explains why JIT needs its own message instead of a tighter DELFOR.
On the invoice side, expect self-billing. BMW creates the invoice from its own goods-receipt data and sends it to you as VDA 4938; your job is fast, structured verification against your own delivery data. Teams that keep waiting for "their" invoice to arrive discover months later that the receivable has been sitting in the 4938 mailbox all along. See our VDA 4938 guide for what to check before confirming.
Labels ride along
EDI and labels are one system, not two. Shipments in German automotive are labelled per the VDA 4902 transport label recommendation, and the label content mirrors the DESADV: SSCC, part number, quantity, supplier. When a label and a 4987 disagree, the goods-receipt scan fails and somebody's shift gets long. Treat the label template as part of the EDI specification and test both together, box by box, in the test phase.
Transport: OFTP2, done properly
File exchange runs over OFTP2, the Odette File Transfer Protocol, and BMW's connectivity requirements sit on top of what the industry tightened anyway: mutual TLS authentication with Odette-issued or accepted certificates, current TLS versions, and Odette IDs as the addressing scheme on both ends. If you have been postponing your TLS profile work, BMW traffic is one more reason to finish it; the industry-wide direction and the practical checklist are covered in our OFTP2 TLS 1.3 migration article.
You have two realistic setups. Operate your own OFTP2 server if you have the EDI competence in-house, or route everything through an EDI service provider who holds the certificates and the connectivity on your behalf. Both are normal; what BMW cares about is that files arrive complete, on time, and with functioning end-to-end responses.
The onboarding sequence that works
- Get the current implementation guideline first. BMW publishes message-specific guidelines per process, and the version matters. Build and test against the exact document your contact gives you, not a generic VDA interpretation.
- Set up addressing. Odette IDs, certificates, and the OFTP2 endpoints for test and production, on your side or your provider's.
- Build mappings per message. DELFOR consumption, DELJIT sequencing, DESADV generation. Test each mapping with the guideline's example scenarios before any live-like data.
- Run the test cycle. Structured test messages, then a simulated full cycle: schedule in, goods out, 4987 back, label scan. Fix label and message mismatches here, where it is cheap.
- Parallel run, then cut over. Run old and new channels side by side for the agreed window and reconcile daily. Go live per plant, not per corporation, if volumes allow it.
Where new BMW suppliers stumble
The same four mistakes account for most rough first years. Ship-to confusion: one supplier number, several BMW plants, and a mapping that sends every DESADV with the wrong ship-to or wrong storage location. Sequence drift on 4988: production changes the build sequence and the EDI sequence numbers do not follow, or vice versa. Late DESADV: the truck leaves at 06:00 and the 4987 leaves at 07:30, which in a tightly timed goods receipt is the same as not sending it. And skipped self-billing reconciliation: nobody owns the 4938 check, so price and quantity drift surface at year-end instead of the week they happened.
All four are detectable before BMW's systems see them. A DESADV with a broken envelope, a wrong date format, or a control-count mismatch fails the same way everywhere, and our VDA 4987 validator and VDA 4984 validator check exactly those properties on your real files, in the browser. Run every mapping change through them before it reaches the test gateway; it is the cheapest quality gate in the whole project.
Related reading: VDA 4984 DELFOR explained, VDA 4987 DESADV explained, and the EDI onboarding checklist.