What are Odette Message Types?
Odette 
message types are standardized EDI formats maintained by Odette International, a European automotive organization. They define electronic communication across manufacturing, logistics, and financial operations. Common Odette messages include ORDERS (Purchase Order), ORDRSP (Order Response), DELINS (Delivery Instruction), DELJIT (Delivery Just-in-Time), INVOIC (Invoice), RECADV (Receiving Advice), and SLSRPT (Sales Report). These messages are compatible with and ANSI X12 standards, supporting seamless European and global automotive integration.
How Does PartnerLinQ Use Odette messages?
PartnerLinQ enables trading partners to manage Odette EDI right alongside their ANSI X12, EDIFACT, VDA, and SAP IDoc transactions. Through PartnerLinQ’s unified framework, European OEMs and Tier 1, 2, and 3 suppliers can exchange orders, shipments, and payment data promptly and efficiently, ensuring compliance with Tier 1 requirements, Odette standards and interoperability with global partners.
What responses to the Odette message are expected/sent?
Odette 
message responses mirror their EDIFACT equivalents. For example, an ORDERS message may generate an ORDRSP acknowledgment; DELINS and DELJIT may be followed by DESADV and RECADV, and financial exchanges use INVOIC and REMADV. PartnerLinQ orchestrates these responses within integrated workflows.
What does the Odette message workflow support?
The Odette message suite completely supports supply chain automation in automotive industries — order initiation, confirmation, delivery scheduling, invoicing, and payment. PartnerLinQ bridges Odette standards and gaps within automotive supply chain automation with X12, VDA, EDIFACT and SAP IDoc transactions like DELFOR, DESADV, INVOIC, and REMADV, ensuring synchronized European and global communication.
Accepting an Odette ORDERS (Purchase Order) message from your automotive trading partner is typically insufficient for complete EDI compliance. Most automotive trading partners will expect other Odette EDI transactions in response to or following an Odette ORDERS (Purchase Order) message such as:
| Transaction | Purpose | Role |
|---|---|---|
| ORDERS | Purchase Order | Used to place an order for goods or services. |
| ORDRSP | Order Response | Confirms receipt of the Purchase Order |
| ORDCHG | Order Change | Used to support order changes |
| DESADV | Despatch Advice (ASN) | Describes the contents of the shipment. |
| DELFOR | Delivery Forecast | Used to support supplier delivery schedules and forecasting |
| DELINS | Delivery Instruction | Provides detailed delivery instructions and calls. |
| DELJIT | Delivery Just-in-Time | Used to provide ‘just-in-time’ delivery sequences. |
| INVOIC | Invoice | Used to provide detailed billing for goods or services. |
| RECADV | Receiving Advice | Used to provide receipt and acknowledge the condition of delivered goods in terms of OSD – Over, Short, or Damaged |
| SLSRPT | Sales Report | Used to reports sales data and inventory levels, actual stock quantities tied to those locations. |
What are the Key Features of Odette? 
- Standardized across European automotive networks
- Compatible with UN/EDIFACT, X12, SAP IDoc, and VDA standards
- Supports Just-in-Time (JIT) and Just-in-Sequence (JIS) deliveries
- Enables end-to-end supply chain visibility
What is the purpose of the Odette message workflow?
The purpose of Odette message set, developed by Odette International, a European automotive industry organization, is to enable and ensure that a harmonized, seamless, automated, exchange of data for automotive OEMs, suppliers, and logistics providers exists across Europe, improving accuracy, compliance, and operational agility. Its primary purpose is to achieve consensus-based solutions for key business processes—such as purchasing, scheduling, shipping, invoicing, and inventory reporting reducing errors, speeding up transactions, and improving overall efficiency in the automotive sector.
What information is included in the Odette message workflow?
The Odette message set carries detailed data including purchase order data, delivery instructions, shipment IDs, schedule details, invoice amounts, and receipt confirmations providing a seamless, automated, exchange of data for automotive OEMs, their suppliers, and logistics providers.
What are the Essential Components of an Odette message?
- Header (message metadata)
- Line item details (quantities, parts, schedules)
- Totals and trailer segments
What are the Common segments of an Odette message?
Common segments include: UNH (Message Header), BGM (Beginning of Message), DTM (Date/Time), NAD (Party Information), LIN (Item), QTY (Quantity), and UNT (Message Trailer).
| Segment | Name |
|---|---|
| UNH | Message Header |
| BGM | Beginning of Message |
| DTM | Date/Time/Period |
| NAD | Name and Address |
| RFF | Reference |
| CUX | Currencies |
| LIN | Line Item |
| QTY | Quantity |
| PRI | Price Details |
| UNS | Section Control |
| UNT | Message Trailer |
What Status Codes are used with an Odette message?
Odette uses codes that represent order acknowledgment, acceptance, modification, or rejection, similar to UN/EDIFACT BGM1225 and X12 BAK02 values.
What Reason Codes are used with an Odette message?
Reason Codes are used to explain order changes or exceptions, such as quantity discrepancies, production delays, or delivery rescheduling.
What use cases does the Odette message workflow support? 
- OEM-to-supplier order transmission
- Delivery scheduling (DELINS/DELJIT)
- Invoice and remittance processing (INVOIC/REMADV)
- Sales reporting (SLSRPT)
What are the Benefits of Odette?
- Global standardization for procurement
- Faster, more accurate order processing
- Improved cross-border compliance
- Reduced errors and disputes
- Improves cross-border trade efficiency
- Enhances supply chain synchronization
- Reduces administrative overhead
- Enables digital transformation for European OEMs
How Efficient is Odette?
Speeds up order placement and reduces processing delays. Automates procurement and logistics transactions across multiple ERP environments.
How compliant is Odette?
Complies with Odette, UN/EDIFACT, and ISO/UN/CEFACT global data interchange standards. Most automotive trading partners will expect other Odette EDI transactions in response to or following an Odette ORDERS (Purchase Order) message such as:
| Transaction | Purpose | Role |
|---|---|---|
| ORDERS | Purchase Order | Used to place an order for goods or services. |
| ORDRSP | Order Response | Confirms receipt of the Purchase Order |
| ORDCHG | Order Change | Used to support order changes |
| DESADV | Despatch Advice / Advance Ship Notice | Describes the contents of the shipment. |
| DELFOR | Delivery Forecast | Used to support supplier delivery schedules and forecasting. |
| DELINS | Delivery Instruction | Provides detailed delivery instructions and calls. |
| DELJIT | Delivery Just-in-Time | Used to provide just-in-time’ delivery sequences. |
| INVOIC | Invoice | Used to provide detailed billing for goods or services. |
| RECADV | Receiving Advice | Used to provide receipt and acknowledge the condition of delivered goods, OSD (Over, Short, or Damaged) |
| SLSRPT | Sales Report | Used to reports sales data and inventory levels, actual stock quantities tied to those locations. |
| REMADV | Remittance Advice | Used to communicate how a payment is applied to one or more invoices, including adjustments, deductions, credits, or disputes. |
What is the format of an Odette message?
Odette messages follow structured EDIFACT-based syntax with defined segments, codes, and qualifiers, supporting XML and flat-file implementations for integration with ERP systems.
How Accurate is an Odette message?
Ensures consistent, auditable communication between automotive trading partners across Europe.
What are the Limitations of an Odette message?
Odette messages are primarily Europe-centric and may require mapping for integration with non-European standards like X12 or VDA.
Are Guidelines & Sample Files for Odette messages available?
Yes, sample Odette message structure and implementation guides that support testing and partner onboarding are available through PartnerLinQ.
Sample Odette message implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding. Customized specification documents for use in on boarding and technical development are available upon request.
PartnerLinQ provides:
- Odette message implementation guide
- Sample payloads
- Qualification and testing maps
- Error handling and best-practice notes
What are the Basic Questions for Integrating Odette
- Which Odette message types are mandatory for your OEM?
- Are DELINS and DELJIT both required?
- How are ORDERS and ORDRSP reconciled?
- Are shipment confirmations automated?
- Is invoice exchange (INVOIC) linked to payment (REMADV)?
What Business Level Workflow does the Odette message standard support?
- OEM sends an Odette ORDERS message.
- Supplier confirms via ORDRSP.
- Delivery instructions issued (DELINS/DELJIT).
- Shipment and receipt managed through DESADV and RECADV.
- Invoice sent using INVOIC.
- Payment advice transmitted via REMADV.
What are the Best Practices for implementing the Odette message standard?
- Maintain alignment between Odette and EDIFACT versions.
- Automate message translation using PartnerLinQ mappings.
- Use structured codes and qualifiers for automation.
- Exchange acknowledgments (CONTRL/997) to validate transmissions.
- Validate with Odette implementation guidelines regularly.
Appendix: Mapping Table – Odette ↔ X12 ↔ EDIFACT ↔ SAP IDoc
| Odette | ANSI X12 | EDIFACT | SAP IDoc |
|---|---|---|---|
| ORDERS – Purchase Order | 850 – Purchase Order | ORDERS | ORDERS |
| ORDRSP – Order Response | 855 – PO Acknowledgment | ORDRSP | ORDRSP |
| DELINS – Delivery Instruction | 862 – Shipping Schedule | DELINS | DELFOR |
| DELJIT – Delivery Just-in-Time | 862 – Shipping Schedule | DELJIT | DELJIT |
| DESADV – Despatch Advice | 856 – Advance Ship Notice | DESADV | DESADV |
| INVOIC – Invoice | 810 – Invoice | INVOIC | INVOIC |
| RECADV – Receiving Advice | 861 – Receiving Advice | RECADV | RECADV |
| REMADV – Payment Advice | 820 – Payment Order | REMADV | REMADV |
| SLSRPT – Sales Report | 852 – Product Activity Data | SLSRPT | SLSRPT |
References
Explore Our Integration Solutions
PartnerLinQ Integration Solutions
Connect Everything. Integrate Intelligently.
Future-Proof Your Business with Composable, AI Powered Connectivity.