EDI Integration | EDIFACT, DESADV for Automotive

TL;DR

What EDI is: Automatic exchange of business documents between systems. Orders, delivery notes, invoices. In automotive, a condition of doing business. In retail, a requirement from major buyers.
Typical scenario: Your customer sends a spec (EDIFACT D.96A or D.07A, message types ORDERS/DESADV/INVOIC). Often with a firm go-live date.
Implementation paths: EDI platform, direct API connection, or a customer web portal. A platform covers most cases.
Timeline: First customer via EDI platform: 4-8 weeks. Each additional customer on the same platform: 1-3 weeks.
Costs: Depend on number of partners, message volume and ERP type. We quote after an initial call.
Who delivers: Prague-based team, CET timezone, EU contracts. Lagardère: EDI playbook for retail distribution.

What EDI consists of and why it is not just "sending files"

EDI (Electronic Data Interchange) is a standard for automated document exchange between you and your trading partners. Orders, delivery notes and invoices flow between systems without manual intervention. It is not an email with an attachment. It is a protocol, a format and a workflow combined. For EDI in a logistics context, see our logistics and ERP guide. For ERP selection in a manufacturing company from scratch, see our ERP in manufacturing guide.

EDIFACT and its versions

The dominant EDI standard in Europe. The customer specifies a directory version (D.96A, D.01B, D.07A) in their spec, and you must match it exactly. EANCOM is a retail-specific subset based on GS1 identifiers. Major automotive OEMs (Tier 0 and Tier 1) typically require D.96A or D.07A.

Message types: ORDERS, DESADV, INVOIC

Three core messages. ORDERS = purchase order from the customer. DESADV = advance shipping notice (ASN) you send. INVOIC = electronic invoice. Additional types include ORDRSP (order response), RECADV (receiving advice) and APERAK (application acknowledgment). Each message flows in a specific direction.

Communication protocols: AS2, SFTP, OFTP2

How messages physically travel. AS2 (HTTP-based, most common in automotive). SFTP (simpler, used by some smaller companies). OFTP2 (Odette standard, European OEMs). VAN (Value Added Network) is a legacy option but still common in older supply chain setups. Most implementation guides skip this layer entirely.

Data mapping: ERP fields to EDI segments

The core of every implementation. Each ERP has different field names and structures. EDI has fixed segments (BGM, DTM, NAD, LIN, QTY, MOA). Mapping means defining which ERP field goes where in the EDI message. This is where most implementation time goes when connecting dozens of suppliers.

Message validation and acknowledgment

CONTRL message (syntax acknowledgment). APERAK (application-level acknowledgment). What happens when a message fails validation. Why you need monitoring from day one. Without active monitoring, you learn about a problem when the customer calls about a missing shipment.

Identifiers and code lists: GLN, EAN, DUNS

GLN (Global Location Number) identifies your company and every branch or warehouse. EAN/GTIN identifies products. DUNS for some US-based OEMs. You need a GLN before you can start anything.

How EDI implementation works step by step

EDI implementation is not one big project. It is a sequence of steps where each one depends on the previous. This process is based on our projects, including EDI integration for retail.

1

Customer sends EDI specification

The OEM or retail chain sends a document specifying the EDIFACT version, message types, protocol and their GLN. Sometimes it is a 5-page PDF, sometimes a 50-page guideline. Read the entire thing before you do anything else. Every OEM has their own specifics.

2

Choose your EDI path: platform, direct connection or portal

An EDI platform handles format translation and connectivity for you. Direct API connection makes sense only with one partner that offers it. A customer web portal is sometimes offered to small suppliers, but it is manual and unsustainable with more than one customer.

3

GLN registration and communication channel setup

Register with your national GS1 member organization if you do not have a GLN yet. Set up AS2 or OFTP2 certificates with the platform or partner. This takes 1-2 weeks and is the step people most often forget.

4

Data mapping between ERP and EDI

The most labor-intensive step. Map every field your ERP uses for orders, shipments and invoices to the corresponding EDI segment. Test with sample messages. We encountered suppliers sending products with unknown EAN codes and had to implement fallback matching using supplier part numbers.

5

Testing with the customer

Send test messages to the customer test environment. They validate structure, content and codes. Expect 2-4 rounds of corrections. The customer EDI team has their own backlog. Allow 3-5 business days per round for the customer to respond.

6

Go-live and monitoring

Switch from test to production. First few days: watch every message. Set up alerts for failed deliveries, validation errors and missing acknowledgments. After 2 weeks of clean operation, you can relax. But monitoring must stay on permanently.

For the first customer, plan 4-8 weeks.

EDI platform, direct connection or customer portal?

Implementation options, each for a different situation. Most companies end up with a platform because it covers the widest range of partners. But it is not the only path. The decision depends on number of trading partners, message volume and your ERP capabilities.

EDI platform makes sense

More than 1 trading partner with EDI requirements
Customers use different EDIFACT versions or proprietary formats
You want one integration from ERP and the platform handles the rest
You need monitoring, archival and audit trail
You do not want to manage AS2/OFTP2 certificates yourself
ERP has no native EDI module

Direct connection or portal

Single customer with an open REST/SOAP API
Customer offers a web portal for small suppliers
Message volume is low (single digits monthly) with no growth potential
ERP has a built-in EDI module with customer connector
Customer explicitly requires direct connection (no VAN)
Temporary solution to verify EDI makes sense

Criterion	EDI Platform	Direct Connection	Customer Portal
Number of partners	Unlimited, platform handles it	1 partner per integration	That one customer only
Setup cost	Platform setup + connector	Custom connector	Usually free
Monthly operation	Fee based on message volume	Connector maintenance only	Free (your time is not free)
Deployment time	4-8 weeks	2-6 weeks	1-2 weeks
Scalability	Next partner in 1-3 weeks	Each partner = new project	None, manual work
Monitoring	Included in platform	You must build it yourself	Does not exist
Best for	Most companies, automotive and retail	Technically advanced firms, 1 partner	Small suppliers starting out

swipe to see the full table

How EDI connects to your ERP

EDI on its own does not create an order in your system. You need connectivity between the EDI platform and your ERP. The difficulty depends on which ERP you use and how customized it is. Here are the scenarios we typically see. For API integration details see our ERP integration service.

Dynamics 365 Business Central

BC has well-documented APIs, which makes connecting the EDI platform faster to build. We build the integration directly on top of those APIs, map BC fields to EDI messages and set up monitoring. Works for both cloud and on-premises deployments.

SAP Business One, Oracle NetSuite and mid-market ERPs

Mid-market ERPs vary widely in EDI readiness. SAP B1 has EDI add-ons. Oracle NetSuite has SuiteCloud connectors. The key question is whether your ERP can export and import structured data (XML, JSON, flat file) that the EDI platform can read and process. When connecting a retail client with dozens of suppliers, we set up automated scheduled transfers of XML files between the ERP and the EDI platform.

SAP S/4HANA and ECC

SAP has built-in IDoc-based EDI, but configuring it is complex. Many companies struggle because the original setup does not cover new customer requirements (a new message type, a new partner, a format change). The question is whether to keep extending native IDoc, or put an EDI platform on top of SAP.

When your ERP has no EDI support

Middleware approach. A custom integration layer that reads from the ERP database or file exports and feeds the EDI platform. This works but requires maintenance when either side changes. The EU ViDA directive will push more ERP vendors to add native EDI and e-invoicing support.

Where EDI projects get delayed

Skipping the spec, underestimating testing, missing GLN registration, mapping without a template and no monitoring. The five things that delay EDI projects most often.

Starting without reading the customer specification

The OEM EDI guideline contains the version, message types, mandatory segments, code lists and testing procedure. Skipping it and assuming "standard EDIFACT" led to failed test rounds in every project we have seen.

Underestimating the testing phase

Testing is not "send one message and done." Plan for 2-4 rounds of corrections over 2-4 weeks. Most companies budget 2-3 days. That is why projects run late.

Not securing GLN and certificates early

AS2/OFTP2 certificate exchange with the platform or partner takes days, GS1 registration takes additional weeks. Start both processes as soon as the contract is signed.

Mapping without a template

Use a mapping template (a spreadsheet with ERP field, EDI segment, transformation rule and example value). Without it, developers guess, testers find errors one at a time, and nothing is reusable for the next customer.

Setting up monitoring only after the first problem

EDI messages fail without notification. Without monitoring (CONTRL checks, delivery receipts, business-level alerts), the first sign of a problem is a penalty charge or a customer line stoppage. Set up monitoring before go-live.

Automotive EDI: how it differs from retail

Automotive EDI is a world of its own. The standards, message types and typical flow differ from retail and general distribution. If a Tier 1 supplier or OEM asks you for EDI, expect specifications you would not see in other industries. This section covers what makes automotive different.

Odette and VDA: the European automotive standards

Odette is the European organization that defines data formats, communication protocols and processes for the automotive supply chain. VDA (Verband der Automobilindustrie) is the German counterpart, used primarily by the Volkswagen Group, BMW, Mercedes-Benz and Audi. Some OEMs use VDA-specific EDIFACT subsets (for example VDA 4905 for orders, VDA 4913 for despatch advice). Odette JAUTOMOTIVE uses more modern EDIFACT messages. In practice, you need to find out what the specific OEM requires, not just assume "EDIFACT".

Message types: DELFOR, DELJIT and extended DESADV

In automotive, the classic trio of ORDERS / DESADV / INVOIC is not enough. You also encounter DELFOR (delivery forecast: a forward-looking delivery plan covering weeks), DELJIT (just-in-time call-off: specific call-offs for parts) and an extended DESADV with details such as transport packaging numbers, packing sequences and RFID codes. Each VDA version has its own specifics. If the OEM asks for an "ASN", you only find out the exact format from their specification.

OFTP2 as the preferred protocol

AS2 dominates in retail. In automotive, OFTP2 (Odette File Transfer Protocol 2) is more common, offering end-to-end encryption and support for large transfers. If you supply the Volkswagen Group, Stellantis, BMW or Mercedes-Benz, you will most likely need OFTP2. Commercial VAN providers (Seeburger, OpenText) support OFTP2 as a standard option.

Tier 0, Tier 1, Tier 2: who sends what to whom

The automotive supply chain has a clear hierarchy. Tier 0 is the OEM (the car manufacturer). Tier 1 delivers modules directly to the OEM. Tier 2 delivers components to Tier 1. EDI specifications "propagate" downward: if you are Tier 2 supplying Tier 1, they may require EDI in the same way they receive it from the OEM. EDI is therefore not optional but a precondition of the contract. Being in the supply chain is enough.

Just-in-time and just-in-sequence: timing

Just-in-time (JIT) means parts are delivered when they are needed, typically a day or two before assembly. Just-in-sequence (JIS) is stricter: parts arrive in the exact order they will be mounted on the production line. EDI in the JIS variant requires the DESADV to contain a sequence number and your logistics system to process call-offs in minutes, not hours. This is not just an IT project but also an operations setup.

WebEDI portals from Tier 1 suppliers

SupplyOn, Covisint (now part of OpenText) and similar portal platforms are offered by Tier 1 suppliers to smaller vendors as an alternative to full EDI integration. They work for low volumes, but when volumes grow (above ten orders per day), manually filling in web forms stops being viable. At that point you face a decision: invest in full EDI integration, or accept that manually retyped orders mean errors and delays.

Frequently Asked Questions

How much does EDI integration cost?

Depends on number of partners, message volume and ERP type. The main components: EDI platform setup, monthly operating fee and an ERP connector. Each additional customer on the same platform is cheaper because the infrastructure exists. We quote after an initial call where we map your situation.

How long does it take to connect the first EDI customer?

4-8 weeks if you start immediately. The biggest variables: speed of the customer EDI team during testing and whether you already have a GLN. If your timeline is tight, start the same week. From our projects, we know it is achievable when the scope is clear.

We use a mid-market ERP without an EDI module. Can we still connect?

Yes. The EDI platform handles the translation. Your ERP just needs to export and import structured data (XML, CSV, database). We have connected EDI to ERP systems with no native EDI support at all. The connector is custom, but the pattern is a scheduled export from ERP into the EDI platform.

What is a DESADV (ASN) and why does the customer require it?

DESADV stands for Despatch Advice (the EDIFACT standard term), also called an Advance Shipping Notice or ASN. It tells the customer what you shipped, in what quantities and packaging, and when to expect the truck. In automotive, the customer uses the DESADV to plan unloading and receiving. Without it, the warehouse cannot plan unloading and may reject the shipment or charge a penalty.

Do we need EDI if we only supply one customer?

If that customer requires it, yes. The question is which path: platform, direct connection or their portal. For a single customer, a direct API or portal might work. But if there is any chance of a second EDI customer in the next 1-2 years, invest in a platform from the start. Switching later costs more than setting it up correctly from the start. For smaller partners that do not require EDI, a B2B portal is often more efficient.

What is ViDA and how will it affect EDI?

ViDA (VAT in the Digital Age) is an EU directive mandating electronic invoicing. Poland launches KSeF in 2026, Czech Republic is expected around 2030. This means structured electronic invoicing will become mandatory, not optional. Companies that already have EDI infrastructure will have an easier transition.

How does EDI in automotive differ from retail?

It differs in standards (VDA and Odette instead of EANCOM), in message types (DELFOR, DELJIT and an extended DESADV with sequence data appear on top of the basic ORDERS/DESADV/INVOIC trio) and in protocol (OFTP2 instead of AS2). Automotive also tends to require stricter timing: just-in-time or just-in-sequence deliveries mean the EDI workflow has to run in minutes rather than hours. Details in the automotive section above.

EDI Integration for Manufacturers: What You Need to Know