Why does each partner need its own mapping?

Because each uses different codes (GLN, products), mandatory fields and standard versions. Mapping translates these quirks into your ERP's single format, without changing internal logic.

How long does creating a mapping take?

For a retailer in the native library (already mapped), days. For a brand-new partner, from a few days to a few weeks, depending on message complexity and required testing.

Do I have to maintain mappings?

Yes. Retailers periodically change codes, locations and requirements. A good EDI module centralises mapping maintenance so updates don't break the flow.

← Back to glossary

Category: Tehnologie

EDI mapping

Quick answer: Translating between the standard EDI message structure and your ERP's data format, for automatic processing.

Key takeaways

Field-to-field correspondence (message ↔ ERP)
Transformations (units of measure, date formats)
Validation rules (mandatory fields, allowed codes)
Exception handling

What EDI mapping is

EDI mapping is the translation between the EDI message structure (EDIFACT/X12) and your ERP's internal format. Each segment and element in the message is linked to the correct field in your system (and vice versa, at generation).

Why it is complex

Each partner has its own quirks: location codes (GLN), product codes, mandatory fields, standard versions. Good mapping covers all these variations without rewriting the core logic.

What a mapping includes

Field-to-field correspondence (message ↔ ERP)

Transformations (units of measure, date formats)

Validation rules (mandatory fields, allowed codes)

Exception handling

How Azuvio helps

Azuvio ships pre-built mappings for retailers in the native library (Carrefour, Kaufland, Lidl etc.) and mapping tools for new partners — cutting onboarding time from months to days.

Frequently asked

Why does each partner need its own mapping?: Because each uses different codes (GLN, products), mandatory fields and standard versions. Mapping translates these quirks into your ERP's single format, without changing internal logic.
How long does creating a mapping take?: For a retailer in the native library (already mapped), days. For a brand-new partner, from a few days to a few weeks, depending on message complexity and required testing.
Do I have to maintain mappings?: Yes. Retailers periodically change codes, locations and requirements. A good EDI module centralises mapping maintenance so updates don't break the flow.

Where Azuvio fits

Related terms

EDI (Electronic Data Interchange) — Structured exchange of commercial documents between B2B partners, without emails or manual data entry.
EDIFACT (UN/EDIFACT) — The UN international standard for EDI messages, dominant in Europe for B2B commercial document exchange.
ANSI X12 — The dominant EDI standard in North America, used for commercial document exchange between B2B partners.
EDI partner onboarding — The process of connecting EDI with a new trading partner: mapping, transport setup and end-to-end testing.

Last updated: 2026-07-06