Automotive EDI integration is an electronic data interchange (EDI) link that brings customers' delivery schedules (DELFOR, DELJIT) straight into your ERP and sends the despatch advice (DESADV, usually called the ASN) back automatically from the same data. Done properly, it ends manual copying from customer portals and markedly reduces the risk of mismatched shipments, wrong labels and missed schedule revisions.
Key takeaways
- In the automotive EDI cycle, the customer sends a DELFOR or DELJIT delivery schedule and the supplier replies with a DESADV despatch advice (ASN).
- Version 3.1 of VDA 4987, the despatch advice recommendation based on EDIFACT DESADV, was published in 2023 and replaces the legacy VDA 4913.
- The ASN should never be typed by hand; generate it from pack labels scanned at loading and keep it identical to the e-İrsaliye.
- Implementation takes seven steps: message inventory, master data clean-up, schedule logic, ASN generation, label link, error handling and customer testing.
- Digital Bridge builds automotive EDI integration through a needs analysis and a single-customer pilot, not an off-the-shelf package.
How does the EDI desk really work at most automotive suppliers?
At many automotive suppliers, EDI is the job of one or two people who log in to a web portal, or a converter supplied by the vehicle maker, every morning. The schedule is read off the screen, pasted into a spreadsheet and then keyed into the order lines in the ERP. On shipping day the same person types the delivery note details, part numbers, pack quantities and label numbers back into the portal.
Manual EDI handling works with one customer. It breaks when a third OEM, a second export market or the first Tier-1 abroad arrives, because every customer uses a different message version, reads fields differently and applies its own call-off logic. Mix up the firm and forecast horizons of a schedule and production is planned against the wrong numbers; send an ASN that does not match the physical load and the goods sit at the customer's receiving dock.
The deeper risk is that customer-specific EDI knowledge lives in one person's head. When the EDI coordinator is on leave or moves on, nobody has written down how each customer interprets each field. We cover the general problem of disconnected systems in our guide to API integration; in automotive, the difference is that a data error can become a line-side shortage within hours.
What does a supplier lose without automotive EDI integration?
Türkiye's automotive sector is large and export-driven, and EDI traffic grows with it. According to the Automotive Manufacturers Association (OSD)'s "2025 Results Announced" release, total vehicle production in Türkiye rose 4% to 1,419,464 units in 2025, and automotive exports rose 12% to $41.5 billion according to the Turkish Exporters Assembly (TİM) figures quoted in the same release.
According to the Association of Automotive Parts and Components Manufacturers (TAYSAD), TAYSAD's 540+ members represent 85% of Türkiye's automotive supplier production and 80% of its exports, and employ more than 250,000 people. (TAYSAD — About us)
The OSD and TAYSAD figures show that the supplier base is closely tied to exports and, as a result, often to European customers' data discipline. The standards keep moving too. According to the German Association of the Automotive Industry (VDA)'s "VDA 4987 – Despatch Advice with EDI V3.1" publication page, version 3.1 of the VDA 4987 despatch advice recommendation, based on EDIFACT DESADV, was published on 18 July 2023 and replaces the legacy VDA 4913 message. A supplier still producing the old flat-file format has little time to adapt once a customer makes the switch mandatory.
The cost of manual EDI never shows up as a single line on an invoice. It is spread across goods held at receiving because of a wrong ASN, premium freight after a schedule change was spotted too late, excess or short stock, and a slipping score on the customer's supplier scorecard. That scorecard is usually the first document on the table when the next programme is sourced.
Which messages and standards does automotive EDI use?
Automotive EDI is not a single file but a family of messages that carries the order-to-invoice cycle. The table below maps the most common ones to their ERP counterparts:
| Message | What it carries | Direction | ERP counterpart |
|---|---|---|---|
| DELFOR (VDA 4984, formerly VDA 4905) | Firm and forecast delivery schedule | Customer → supplier | Open order lines, planning input |
| DELJIT | Just-in-time or sequenced call-off | Customer → supplier | Daily or hourly shipping list |
| DESADV (VDA 4987, formerly VDA 4913) | Despatch advice: parts, quantities, packaging, label numbers | Supplier → customer | Delivery note and packing records |
| RECADV | Receiving advice | Customer → supplier | Shipment-to-receipt reconciliation |
| INVOIC | Commercial invoice | Supplier → customer | Sales invoice |
Automotive EDI messages travel over AS2 (Applicability Statement 2), OFTP2 (Odette File Transfer Protocol 2) or a VAN (value-added network); the customer usually decides which. Smaller customers sometimes offer web-EDI instead, but a portal still asks you to key or download data by hand, so it does not deliver the real benefit of automation.
There is also a Turkish layer to consider. The electronic delivery note (e-İrsaliye) submitted to the Revenue Administration (GİB) describes the same shipment as your ASN, so quantities, parts and dates in the two must agree exactly. Designing EDI together with your e-invoice and e-delivery note integration removes the double entry.
How do you implement automotive EDI integration? A seven-step framework
- Build a customer and message inventory. For each customer, record which messages, versions and protocols are required, along with test and production connection details. The customer's supplier EDI guideline is the key document here.
- Clean your part and address master data. The mapping between customer part numbers and your item codes, the unloading point codes and the packaging definitions must be complete. Duplicate and obsolete records are among the most common sources of errors; our article on data quality and duplicate records sets out a clean-up method.
- Carry the schedule logic into the ERP correctly. Keep firm and forecast horizons in separate fields and show planners exactly what changed with each new schedule. This is the main input for capacity planning and APS production scheduling.
- Generate the ASN from the physical shipment. Build the DESADV from the pack labels scanned during loading rather than typing it. The notice then matches the crates that actually went on the lorry.
- Link labels to traceability. Numbers on the VDA 4902 or Odette/GTL label must come from the same source as the packaging numbers in the ASN. Lot and serial tracking is covered in our production traceability guide.
- Set up error and acknowledgement handling. Rejected, late or unacknowledged messages should raise an alert on screen and by email, and the person responsible for acting on each one should be named in writing.
- Run customer testing to a plan. Agree test messages, a sample shipment and a period of parallel running with every customer, and go live only with their sign-off.
Which indicators show EDI performance?
Feeling that EDI works is not enough; a handful of simple measures will tell you:
- Schedule-to-plan lead time: how long it takes for a new delivery schedule to reach the production plan.
- ASN accuracy: the share of shipments that match the despatch advice at the customer's goods receipt.
- Rejected or failed messages: tracked weekly, per customer.
- Manual touch rate: the share of messages someone had to correct by hand, the most honest measure of whether automation is working.
Common mistakes in automotive EDI projects
The most common mistake is to treat EDI as file translation. A translator reads the message, but it does not decide how a schedule should change your plan or how an ASN should be derived from warehouse movements. The second is producing the ASN separately from the warehouse: an ASN with no link to your warehouse management system (WMS) leaves the risk of wrong crates and short quantities exactly where it was.
The third is not recording where EDI errors come from. When a customer raises an ASN mismatch as a complaint, you need to document root cause and corrective action, and the 8D problem-solving method works just as well for EDI failures as for part defects.
For most suppliers EDI is the first step; we set out the traceability, MES and quality steps that follow in digital transformation for automotive suppliers.
How we deliver automotive EDI integration at Digital Bridge
We do not sell an off-the-shelf package. We start with a needs analysis and then provide a written proposal setting out scope, phases and cost. Within our automotive supplier solutions, the approach looks like this:
- Discovery and needs analysis. We review your customers' EDI guidelines, your ERP and your warehouse and labelling processes, and map together which message is handled on which screen, by whom and when.
- Pilot with one customer. We pick the busiest or most troublesome customer and build schedule intake and ASN generation for them first. Once validated in the customer's test environment, the pilot goes live and further customers are added to the same structure.
- ERP integration. Messages are handled in an API integration and system integration layer and connected to your existing ERP system. Our MES solution also integrates with Logo, SAP, Mikro and bespoke ERPs.
- Warehouse and label link. To build ASNs from barcode scans at loading, we cover the production traceability and barcode side in the same project.
- Monitoring and handover. You receive an alert screen for rejected or unacknowledged messages, error logs and a written process document, so EDI knowledge no longer depends on one person.
Where a small customer insists on a portal, we look at removing the repetitive keying with RPA process automation, although direct message integration is always the lasting fix. If EDI is part of a wider change programme, our Industry 4.0 roadmap for SMEs is a useful framework to start from.
Next step
One page is enough to begin: list your customers, the messages each one sends, the protocol used, and who handles EDI today and for how long each day. Bring that list to us via our contact page, and in the first conversation we will agree which customer to pilot with and where your ERP should connect. If EDI is part of a broader Industry 4.0 plan, we can also start with a free on-site assessment. For other data flows on the shop floor, browse our Industry 4.0 guides.