EDI mapping and EDI translator — converting between EDIFACT/X12 and your ERP
In short: EDI mapping is the process of defining how each field in your internal format (ERP export, CSV, database) corresponds to segments and elements in an EDI message (EDIFACT ORDERS, X12 850). The EDI translator is the software that executes those mappings — the core engine of every EDI platform.
Key capabilities
- Pre-built retailer maps: Kaufland, Carrefour, Lidl, Auchan, Metro, Sezamo — all mappings shipped as templates, no custom work.
- Pre-built ERP maps: SAP IDoc, Dynamics 365, NetSuite, Odoo, WinMentor, Charisma, Senior, Clarvision — all covered.
- Visual mapping designer: Drag-and-drop field mapping for custom cases. No code required for typical mappings.
- Business rule engine: Cross-reference tables (GTIN ↔ your item code), conditional logic, default values, computed fields.
- Automatic revalidation: When a retailer publishes a spec change, mappings are auto-checked and flagged before production impact.
- Full test harness: Every mapping change runs through the retailer's test cases before promotion to production.
Why EDI mapping is the hardest part of EDI
Two retailers using the same standard (EDIFACT ORDERS D96A, for example) can still require different mappings: different mandatory segments, different code lists, different partner-specific rules (Kaufland uses GLN in one place, Carrefour in another). Multiply this by dozens of retailers, dozens of document types and dozens of ERPs and you understand why a specialized EDI provider with a mature template library saves months of work per project.
The mapping work is not a one-time cost either. Retailers publish spec updates annually (or more often). A good EDI provider maintains templates continuously — customers just see mappings 'work' as retailers change specs.
Frequently asked questions
What is EDI mapping?
EDI mapping is the definition of how fields in your internal system (ERP, database, CSV) correspond to segments and elements in a standard EDI message (EDIFACT, X12, UBL). A mapping is the recipe that lets the translator convert your data into a partner-compliant EDI message and back.
What is an EDI translator?
An EDI translator is the software that executes EDI mappings — parses incoming EDI messages into internal format, and serializes internal data into outbound EDI messages. Every EDI platform has a translator engine at its core (also called mapper or converter).
How much does EDI mapping cost?
For pre-existing retailer templates (Kaufland, Carrefour, etc.) with a supported ERP: included in the monthly subscription. For custom mappings (unique ERP, unique document type): typically €300-1,500 per mapping as a one-time cost, then included in ongoing maintenance.
How long does a custom EDI mapping take?
For a supported ERP with a well-documented format: 2-5 business days per document type (mapping + testing). For a legacy or undocumented ERP: 1-3 weeks including reverse-engineering the format.
Do EDI providers handle data mapping?
Yes — this is the primary technical service EDI providers deliver. Reputable providers maintain a library of pre-built maps for popular ERPs and retailers, and offer custom mapping as a paid service for unique cases.