EDI Standards and Protocols
EDIFACT.hu is a practical portal for understanding EDI standards, message types, transport protocols and enterprise integration workflows in one clear, business-friendly experience.
- Focus
- EDIFACT, X12, XML, VDA
- Use cases
- Retail, manufacturing and logistics integrations
- Outcome
- Faster orientation for decision-makers and technical teams
The EDI process in five business steps
The stepper below shows the typical path from source application to partner-side processing. Click any stage to expand its details.
Source applications and business data
Most EDI flows begin in an ERP, billing tool, WMS or custom backend. The outgoing business object can be an order, invoice, despatch advice or master data update.
- Internal formats include XML, CSV, IDoc and database records
- Typical business messages include ORDERS, INVOIC and DESADV
- The goal is to prepare reliable source data before mapping starts
Mapping and standardisation
This is where internal structures are translated into standard EDI payloads. Mapping includes business rules, mandatory segments and partner-specific conventions.
- XML / IDoc / CSV transformed into EDIFACT, X12 or XML-based B2B formats
- Segment-level and field-level validation
- Support for partner guidelines and version management
Secure transport and delivery
Once standardised, the message is delivered through the agreed partner channel. The transport layer is chosen based on partner requirements, security expectations and operational maturity.
- AS2, SFTP, OFTP2 and HTTPS APIs are common options
- Encryption, signing and tracking can be enforced
- Transport reliability and business SLA can be monitored centrally
Validation and exception handling
The gateway and receiving side validate structure, mandatory elements and trading-partner rules. Errors can trigger acknowledgements, alerts or reprocessing workflows.
- Syntax validation, business rule checks and audit trail support
- CONTRL or functional acknowledgement handling
- Error control and monitoring for stable operations
Partner-side processing
After conversion on the receiving side, the message enters the partner ERP or backend landscape and continues as part of standard business execution.
- ERP import, accounting, order handling and inventory updates
- Automatic workflows and internal approvals
- Visibility across customer and supplier collaboration
Core EDI standards at a glance
These cards summarise where each standard typically appears and where to continue reading in the detailed documentation.
UN/EDIFACT
The leading standard for European and global EDI projects with a broad catalogue of reusable business messages.
View DocumentationANSI ASC X12
The dominant North American EDI standard across retail, healthcare, logistics and manufacturing networks.
View DocumentationVDA
A German automotive standard family widely referenced in OEM and supplier communication scenarios.
View DocumentationEANCOM
A commercial EDIFACT profile used heavily in retail and consumer goods supply chains.
View DocumentationXML-based B2B
A common intermediary or target format in modern integration programmes, especially around APIs and platform interoperability.
View DocumentationRosettaNet
A structured high-tech B2B framework designed for electronics and semiconductor supply chain collaboration.
View DocumentationA developer-focused transport layer
Business standards define the message. Delivery depends on the technical protocol selected to provide authentication, traceability and operational reliability.
AS2
Widely adopted HTTP-based B2B protocol with digital signatures, encryption and MDN acknowledgements.
SFTP
Practical and secure file-based transport over SSH with broad infrastructure support.
OFTP2
The preferred automotive transport option for many European manufacturing partner ecosystems.
HTTPS / API
Ideal for service-driven, real-time integrations where APIs complement or extend traditional EDI.