Resources · European automotive EDI

ODETTE messages, versions and OFTP2

Odette is the European automotive supply chain organization. It publishes EDIFACT-based messages for orders, delivery schedules, despatch advices, invoices and payments, XML messages for finished-vehicle logistics, and the OFTP2 protocol that carries them securely. This page lists them all with their EDIFACT base, version and date.

Organization
Odette International
Message base
UN/EDIFACT D.96A to D.21A, XML
Transport
OFTP2 (RFC 5024)
List read
November 2026
Entries listed
55
ODETTE message mapA map of Odette messages grouped into ordering and product data, delivery schedules, despatch and receiving, invoicing, inventory and packaging, finished-vehicle logistics, acknowledgements and OFTP2.ODETTE message map55 entries in 8 groupsOrdering and product data6 entriesPurchase orders, changes and responses,price lists and product data.OM13OM14OM15OM16OM26OM47Delivery schedules and call-offs7 entriesForecasts, schedules, just-in-time andKanban calls, and schedule exceptions.JM01JM02OM02OM03OM04OM05OM06Despatch and receiving advice3 entriesWhat was sent and what was received.JM03OM08JM05Invoicing and payment5 entriesInvoices, statements of account andremittance advices.JM06OM09OM18JM07OM17Inventory, packaging and tracking8 entriesStock reports, empty packaging processes,transport status and batteries.JM08OM30–OM33OM35–OM39OM34, OM40OM41, OM42LG19OM41OM51Finished-vehicle logistics14 entriesThe joint Odette, ECG and VDA messageset for moving finished vehicles: 12EDIFACT messages and a family of XMLmessages.FV01–FV12FV13a / FV13bFV14a / FV14bFV15FV16FV17FV18FV19FV20FV21…Acknowledgement, performanceand support5 entriesApplication errors and acknowledgements,performance reports and implementationguidance.OM44OM45OM46OS11OS10OFTP2 and secure exchange7 entriesThe protocol, its guidelines, certificatesand test service.RFC 5024OP08OP09SE01SE02EN01OA03
ODETTE message mapA map of Odette messages grouped into ordering and product data, delivery schedules, despatch and receiving, invoicing, inventory and packaging, finished-vehicle logistics, acknowledgements and OFTP2.ODETTE message map55 entries in 8 groupsOrdering and product data6 entriesPurchase orders, changes and responses,price lists and product data.OM13OM14OM15OM16OM26OM47Delivery schedules and call-offs7 entriesForecasts, schedules, just-in-time and Kanbancalls, and schedule exceptions.JM01JM02OM02OM03OM04OM05OM06Despatch and receiving advice3 entriesWhat was sent and what was received.JM03OM08JM05Invoicing and payment5 entriesInvoices, statements of account andremittance advices.JM06OM09OM18JM07OM17Inventory, packaging and tracking8 entriesStock reports, empty packaging processes,transport status and batteries.JM08OM30–OM33OM35–OM39OM34, OM40OM41, OM42LG19OM41OM51Finished-vehicle logistics14 entriesThe joint Odette, ECG and VDA message setfor moving finished vehicles: 12 EDIFACTmessages and a family of XML messages.FV01–FV12FV13a / FV13bFV14a / FV14bFV15FV16FV17FV18FV19FV20FV21…Acknowledgement, performance andsupport5 entriesApplication errors and acknowledgements,performance reports and implementationguidance.OM44OM45OM46OS11OS10OFTP2 and secure exchange7 entriesThe protocol, its guidelines, certificates andtest service.RFC 5024OP08OP09SE01SE02EN01OA03

Each colored card is a group of Odette messages. The codes are Odette's own reference numbers; the tables give each message's EDIFACT code, base directory and version.

Expand diagram Download SVG

Overview

What ODETTE is

Odette started as the Organization for Data Exchange by Tele-Transmission in Europe. Its messages are EDIFACT subsets with rules written for car makers and suppliers. Many exist twice: an "Odette" version based on an older directory such as D.96A (DELINS, AVIEXP, KANBAN) and a newer "Joint Automotive" version agreed with other regions, based on a later directory such as D.04A to D.20B (DELFOR, DELJIT, DESADV, INVOIC, REMADV, RECADV, INVRPT).

For finished-vehicle logistics Odette, ECG and VDA publish a joint set of twelve EDIFACT messages (FV01 to FV12) and a family of XML messages (FV13 to FV25) for transport orders, vehicle status, damage reports and capacity reservation.

The messages usually travel over OFTP2, the secure version of the Odette File Transfer Protocol. OFTP2 adds session encryption, mutual authentication, file signing and encryption, compression and signed end-to-end responses, and it is backward compatible with OFTP1. ECOM's B2B gateway handles the messages and the OFTP2 connection in one place.

  • Automotive suppliers

    Receive delivery schedules and call-offs and send despatch advices and invoices to European vehicle makers.

  • Logistics providers

    Exchange transport status, empty packaging orders and finished-vehicle messages.

  • Vehicle makers

    Run one set of messages and one OFTP2 connection model for many suppliers.

Ordering and product data

Purchase orders, changes and responses, price lists and product data.

Reference Message EDIFACT code and base Version and date
OM13 Odette Purchase Order Message Purchase orders. Version 6.1 · Dec 2023 · ORDERR · ORDERS D.05B · Syntax v4
OM14 Odette Purchase Order Change Message Changes to a purchase order. Version 6.1 · Dec 2023 · ORDCHG · ORDCHG D.05B · Syntax v4
OM15 Odette Purchase Order Response Message Supplier response to an order. Version 6.1 · Dec 2023 · REPORD · ORDRSP D.05B · Syntax v4
OM16 Odette Price List Message Price lists. Version 3.0 · Sep 2022 · PRILST · PRICAT D.96A · Syntax v4
OM26 Odette Product Data Message Product master data. Version 3.0 · Dec 2024 · PRODAT · PRODAT D.03A
OM47 Suppliers Long Term Declaration Message Structured supplier declaration of part origin. Version 1.0 · Dec 2021 · XML

Delivery schedules and call-offs

Forecasts, schedules, just-in-time and Kanban calls, and schedule exceptions.

Reference Message EDIFACT code and base Version and date
JM01 Joint Automotive Delivery Forecast Message Delivery forecast. Version 2025 · Feb 2026 · DELFOR · D.04A · Syntax v4
JM02 Joint Automotive JIT Delivery Instructions Message Just-in-time delivery instructions. Version 2025 · Feb 2026 · DELJIT · D.18A · Syntax v4
OM02 Odette Delivery Schedule Message Delivery schedule. Version 5.0 · Sep 2022 · DELINS · DELFOR D.96A · Syntax v4
OM03 Odette Schedule Exception Handling Message Exceptions to a schedule, and the reply. Version 2.0 · Sep 2022 · EXHAND-EXHRSP · DELFOR D.04A · Syntax v4
OM04 Odette Call-Off Delivery Message Call-off of a delivery. Version 3.0 · Sep 2022 · CALDEL · DELJIT D.98B · Syntax v4
OM05 Odette Synchronised Delivery Message Deliveries synchronized to the line. Version 6.0 · Sep 2022 · SYNCRO · DELJIT D.03A · Syntax v4
OM06 Odette KANBAN Delivery Message Kanban calls. Version 5.0 · Sep 2022 · KANBAN · DELJIT D.96A · Syntax v4

Despatch and receiving advice

What was sent and what was received.

Reference Message EDIFACT code and base Version and date
JM03 Joint Automotive Despatch Advice Message Despatch advice. Version 2025 · Feb 2026 · DESADV · D.20B
OM08 Odette Despatch Advice Message Despatch advice. Version 6.0 · Sep 2022 · AVIEXP · DESADV D.96A · Syntax v4
JM05 Joint Automotive Receiving Advice Message Receiving advice. Version 2025 · Feb 2026 · RECADV · D.07A · Syntax v4

Invoicing and payment

Invoices, statements of account and remittance advices.

Reference Message EDIFACT code and base Version and date
JM06 Joint Automotive Invoice Message Invoice. Version 2025 · Feb 2026 · INVOIC · D.07A · Syntax v4
OM09 Odette Invoice Message Invoice. Version 7.0 · Sep 2022 · INVOIC · INVOIC D.03A · Syntax v4
OM18 Odette Statement of Account Message Statement of account. Version 4.0 · Sep 2022 · STATAC · STATAC D.96A · Syntax v4
JM07 Joint Automotive Remittance Advice Message Remittance advice. Version 2022 · Sep 2022 · REMADV · D.04A · Syntax v4
OM17 Odette Remittance Advice Message Remittance advice. Version 4.0 · Sep 2022 · REMADV · REMADV D.96A · Syntax v4

Inventory, packaging and tracking

Stock reports, empty packaging processes, transport status and batteries.

Reference Message EDIFACT code and base Version and date
JM08 Joint Automotive Inventory Report Message Inventory report. Version 2025 · Feb 2026 · INVRPT · D.13A · Syntax v4
OM30–OM33 Empty Packaging Order Message Family Order proposal, order, order change and order response for empty packaging. Version 2025 · Feb 2026
OM35–OM39 Empty Packaging Transport Order Message Family Transport orders for empty packaging, DESADV-based or IFT-based options. Version 2025 · Feb 2026
OM34, OM40 Empty Packaging Despatch Message Family Advance notification and despatch advice for packaging. Version 2025 · Feb 2026
OM41, OM42 Empty Packaging Delivery Message Family In-transit and post-unload status. Version 2025 · Feb 2026
LG19 Digitalising the Part Packaging Agreement Includes OM48 packaging master data, OM49 packaging data sheet and OM50 packaging data code lists. Version 1.1 · Feb 2026
OM41 Odette Transport Status Report Message Transport status. Version 2.2 · Feb 2026 · IFTSTA · D.20B
OM51 Odette Battery Data Exchange Message Battery traceability data. Version 1.0 · Dec 2024 · PRODAT · D.21A S4-S3 profile, Part 11

Finished-vehicle logistics

The joint Odette, ECG and VDA message set for moving finished vehicles: 12 EDIFACT messages and a family of XML messages.

Reference Message EDIFACT code and base Version and date
FV01–FV12 FVL EDIFACT Messages (suite of 12) Outbound logistics processes described in FV00. Version 1.2 · Sep 2023 · EDIFACT
FV13a / FV13b Vehicle Transport Forecast and Response Forecast of transport capacity and the reply. Version 1.3 · Oct 2024 · XML
FV14a / FV14b Vehicle Transport Order and Response Transport order and the reply. FV14a 1.4 · Feb 2026; FV14b 1.3 · Oct 2024 · XML
FV15 Vehicle Status Request Ask for the status of a vehicle. Version 1.3 · Oct 2024 · XML
FV16 Vehicle Status Report Report the status of a vehicle. Version 1.3 · Oct 2024 · XML
FV17 Vehicle Transport Status Report Status of a transport. Version 1.3 · Oct 2024 · XML
FV18 Vehicle Service Order Order for a service on a vehicle. Version 1.4 · Feb 2026 · XML
FV19 Vehicle Inventory Report Inventory of vehicles. Version 1.3 · Oct 2024 · XML
FV20 Vehicle Damage Report Damage information from the logistics provider to the vehicle maker. Version 1.3 · Oct 2024 · XML
FV21 Compound Geo Fence Data Geo-fence data for compounds. Version 1.3 · Oct 2024 · XML
FV22 FVL Envelope Envelope for the XML messages. Version 1.3 · Oct 2024 · XML
FV23 FVL Code Lists Code lists. Version 1.4 · Feb 2026
FV24 Acknowledgement Message Acknowledges FVL messages. Version 1.3 · Oct 2024 · XML
FV25a / FV25b Vehicle Transport Capacity Reservation and Response Reserve transport capacity and the reply. Version 1.3 · Oct 2024 · XML

Acknowledgement, performance and support

Application errors and acknowledgements, performance reports and implementation guidance.

Reference Message EDIFACT code and base Version and date
OM44 Odette Application Error and Acknowledgement Acknowledges receipt, reports syntax and data errors. Version 3.1 · Dec 2023 · APERAK · D.08A · Syntax v4
OM45 Odette Deviation Report Message Report of a logistics catalogue deviation to a supplier. Version 1.0 · May 2021 · XML
OM46 Odette Delivery Accuracy Report Message Report a delivery accuracy rating to a supplier. Version 1.0 · May 2021 · XML
OS11 Structure of an EDIFACT Interchange Guide aligned with ISO 9735. Version 2.1 · Feb 2026
OS10 Model EDI Agreement Template agreement. Version 2.0 · Sep 2010

OFTP2 and secure exchange

The protocol, its guidelines, certificates and test service.

Reference Message EDIFACT code and base Version and date
RFC 5024 OFTP2 specification Odette File Transfer Protocol version 2; backward compatible with OFTP1. OFTP 2.0
OP08 OFTP2 Implementation Guideline Implementation, certificates and archiving; includes partner data exchange using XML. Version 3.2 · Mar 2026
OP09 OFTP2 Interoperability Testing Service Test cases software must pass to earn OFTP2 Tested Software status. Version 3.3 · Mar 2026
SE01 Security Certificate Exchange (SCX) Exchanging security certificates. Version 1.0 · Jan 2009
SE02 Security and Risk Reduction (S2R) Security recommendations. Version 1.0 · Apr 2006
EN01 ENGDAT Engineering data exchange. Version 3.0 · Mar 2006
OA03 Security features for APIs Guidance on security features when developing APIs. Version 1.0 · Dec 2023

Structure

Odette and Joint Automotive messages

An Odette message is an EDIFACT message limited to the segments, codes and sizes the automotive industry agreed. "Syntax v4" means the message uses EDIFACT syntax version 4. Where a row shows two codes, the first is Odette's own name for the message (for example DELINS) and the second is the EDIFACT message it is based on (DELFOR) with its directory version (D.96A).

The Joint Automotive messages (JM01 to JM08) are agreed between Odette and its counterparts in other regions, so a supplier that serves vehicle makers on several continents can use the same message definitions.

An OFTP2 exchangeA sequence between a supplier and a vehicle maker: secure session, signed and encrypted file, signed end-to-end response.An OFTP2 exchangeHow a supplier and a vehicle maker move an automotive message securelySupplier gatewayVehicle makerSecure sessionTLS with certificates on both sidesFileSigned, encrypted and compressedEnd-to-end responseSigned proof of receiptReply messageFor example DESADV acknowledgement (APERAK)
An OFTP2 exchangeA sequence between a supplier and a vehicle maker: secure session, signed and encrypted file, signed end-to-end response.An OFTP2 exchangeHow a supplier and a vehicle maker move anautomotive message securelySupplier gatewayVehicle makerSecure sessionTLS with certificates on bothsidesFileSigned, encrypted andcompressedEnd-to-end responseSigned proof of receiptReply messageFor example DESADVacknowledgement (APERAK)

OFTP2 first sets up a secure session with certificates on both sides, then sends the file signed, encrypted and compressed. The receiver replies with a signed end-to-end response, which is the proof that the file arrived.

Expand diagram Download SVG

Versions

Directory versions in use

Odette messages are published with a document version and a date, and each is based on a UN/EDIFACT directory version. Several directory versions are in use at once.

ItemDetail
D.96ADELINS, AVIEXP, KANBAN, PRILST, STATAC, REMADV (OM17)
D.98B and D.03ACALDEL (D.98B); SYNCRO, INVOIC (OM09) and PRODAT (OM26) (D.03A)
D.04A and D.05BDELFOR (JM01), EXHAND, REMADV (JM07); ORDERS, ORDCHG, ORDRSP (OM13 to OM15)
D.07A to D.21ARECADV and INVOIC (D.07A), APERAK (D.08A), INVRPT (D.13A), DELJIT (D.18A), DESADV and IFTSTA (D.20B), battery PRODAT (D.21A)
OFTPOFTP2 (RFC 5024), backward compatible with OFTP1; OP08 version 3.2 (March 2026)

ECOM B2B Gateway

How ECOM handles ODETTE

The gateway pairs the message handling with the OFTP2 connection, so certificates, signed receipts and the business documents are managed together.

  1. 1

    Connect over OFTP2

    Exchange files with signed, encrypted sessions and certificate checks.

  2. 2

    Read the message

    Parse the EDIFACT message or XML for the Odette version in use.

  3. 3

    Validate and acknowledge

    Check against the Odette message rules and return acknowledgements such as APERAK.

  4. 4

    Map to your ERP

    Create schedules and shipments in the ERP and send despatch advices and invoices back.

How the gateway handles ODETTEFour steps showing how ECOM's B2B gateway handles ODETTE: connect over oftp2, read the message, validate and acknowledge, map to your erp.How the gateway handles ODETTEFrom the partner connection to your ERP1Connect over OFTP2Exchange files with signed,encrypted sessions andcertificate checks.Step 12Read the messageParse the EDIFACTmessage or XML for theOdette version in use.Step 23Validate andacknowledgeCheck against the Odettemessage rules and returnacknowledgements such asAPERAK.Step 34Map to your ERPCreate schedules andshipments in the ERP andsend despatch advices andinvoices back.Step 4
How the gateway handles ODETTEFour steps showing how ECOM's B2B gateway handles ODETTE: connect over oftp2, read the message, validate and acknowledge, map to your erp.How the gateway handlesODETTEFrom the partner connection to your ERP1Connect over OFTP2Exchange files with signed, encryptedsessions and certificate checks.Step 12Read the messageParse the EDIFACT message or XMLfor the Odette version in use.Step 23Validate and acknowledgeCheck against the Odette message rulesand return acknowledgements such asAPERAK.Step 34Map to your ERPCreate schedules and shipments in theERP and send despatch advices andinvoices back.Step 4

The gateway pairs the message handling with the OFTP2 connection, so certificates, signed receipts and the business documents are managed together.

Expand diagram Download SVG

Good to know

What this page does and does not cover

  • This list shows the messages and recommendations on Odette's public messaging page on the date shown. Odette publishes new versions regularly, and a customer may still use an earlier version of a message.
  • Where Odette's page does not state a field (for example the syntax version of some 2025 messages), the field is left out rather than guessed.
  • The OFTP versions before OFTP2 (1.1 to 1.4) are not described on the Odette pages read, so their differences are not listed here. The OFTP2 implementation guideline holds the version-specific detail, and ECOM confirms the version and configuration for each partner during scoping.

Sources, read November 3, 2026

Frequently asked questions

What is the difference between DELINS, DELFOR and DELJIT?

DELINS is Odette's delivery schedule message, based on EDIFACT DELFOR D.96A. The Joint Automotive DELFOR (JM01) is the newer forecast message. DELJIT is the just-in-time delivery instruction message; Odette's KANBAN, CALDEL and SYNCRO are based on it.

What is OFTP2 and do I need it?

OFTP2 is the secure file transfer protocol used across the European automotive supply chain. Many vehicle makers require it. ECOM's B2B gateway supports OFTP and OFTP2, and confirms the version and configuration each partner needs during scoping.

Are Odette messages the same as EDIFACT?

They are EDIFACT messages with automotive rules: a subset of the standard message with agreed segments, codes and sizes. A generic EDIFACT translator can read them if it applies the Odette rules.

Do you handle the finished-vehicle XML messages?

The gateway maps XML as well as EDIFACT, and the finished-vehicle logistics set (FV01 to FV25) is part of the Odette coverage described on this page.

Connect a ODETTE partner

Tell us which ODETTE messages and versions your partner requires. An ECOM specialist confirms the connection, the map and the test plan.