Block [1·0·1] · Foundation Integration block · available

EDI Integration: ORDERS, DESADV & INVOIC Directly in Your ERP.

Retail chains, wholesalers, and industrial buyers expect electronic document exchange without manual PDF re-typing. We connect EDI messages via EDIFACT, AS2, SFTP, clearing providers, or Peppol to Odoo, weclapp, or Zoho so your ERP remains the single source of truth.

4 Core DocumentsORDERS · ORDRSP · DESADV · INVOIC
Clean MappingGLN, GTIN, SSCC/NVE & batches
Visible Review QueueValidation prior to every posting
EDI Document Monitor · Supply Chain & Validation EDIFACT / Peppol
01 · INBOUND ORDERS Customer Order 02 · RESPONSE ORDRSP Order Confirm. 03 · SHIPPING DESADV Despatch · SSCC 04 · INVOICE INVOIC EDIFACT / EN 16931 MASTER DATA MAPPING GLN / ILN → Ship-To Site HQ & branch assignment GTIN / EAN → Item Master Incl. partner item code SSCC / NVE → Handling Unit Batch, expiry & serial no. ISO UoM → Tax Rule PCE/KGM & price check MESSAGE & REVIEW QUEUE ORDERS #4821 · Wholesale South 12 lines · GLN & GTIN verified · SO-2026-1042 Posted DESADV #1194 · Central Hub North 4 pallets · SSCC + batches from WMS Sent ORDERS #4822 · Retail Partner West Line 3: GTIN missing · No partial post Review Transports: AS2 · SFTP · Peppol Access Point · EDI Clearinghouse Connectors
EDI Block Odoo, weclapp & Zoho · Clear Validation Paths

Electronic document flow across the entire supply chain.

Instead of re-typing orders from partner portals and updating despatch advices by hand, we connect your trading partners' message formats directly to your ERP document lifecycle.

ORDERS & ORDRSP without manual re-entry

Incoming orders are validated against customer master data, price lists, and product GTINs and created as structured ERP sales orders. Confirmed quantities, delivery dates, or adjustments flow cleanly back to the trading partner via ORDRSP.

DESADV straight from picking & warehouse

As soon as outbound goods are packed in the warehouse, the ERP generates the electronic despatch advice (DESADV) including handling-unit hierarchy (SSCC/NVE), batch numbers, best-before dates, or serial numbers with zero double entry.

INVOIC, XRechnung, ZUGFeRD & Peppol

Outgoing invoices are dispatched as structured EDIFACT INVOIC or in the European EN 16931 standard (XRechnung / ZUGFeRD) via Peppol or clearing providers — 100% consistent with the tax and revenue postings booked in your ERP.

Flexible transport & clearing topology

Whether direct AS2 or SFTP for individual key accounts or a cleanly coupled EDI clearing provider (VAN) for many retail chains with differing subsets: we design the most economical topology upfront without duplicating mappings.

Strict validation & visible review queue

Mismatched prices, unknown GTINs, missing GLNs, or invalid delivery dates pause cleanly inside a clear review queue. Operations staff see the exact missing field and re-trigger processing immediately after fixing the record.

Acceptance against real partner test messages

Every partner profile (e.g., EANCOM, OpenTRANS, or VDA subset) is tested and documented before go-live against real partner test files, partial shipments, cancellations, and credit notes.

When EDI pays off — and which groundwork makes it succeed.

In practice, EDI almost never fails on file syntax — it fails on inconsistent master data and undefined edge cases. That is why we always start with an explicit mapping blueprint.

When it fits & prerequisites

Built for manufacturers, wholesalers, and brands regularly fulfilling orders from retail chains, buying groups, industrial OEMs, or public-sector entities with EDI or Peppol mandates.

  • Documented partner specification: Current Message Implementation Guideline (MIG) from your trading partner, plus test credentials and a technical contact on the partner side.
  • Maintained ERP master data: Unambiguous GLN/ILN assignments for billing and delivery locations, GTIN/EAN per packaging level, and cleanly defined ISO units of measure.
  • Structured warehouse & packing workflow: For DESADV with SSCC/NVE, handling units, batches, or serial numbers must already be captured during normal warehouse operations.
  • Named review-queue owner: Clear internal ownership to resolve validation alerts (such as price variances or unknown products) promptly.

Limits & deliberate boundaries

EDI is a dependable standard for structured trading relationships — not an end in itself for occasional one-off orders.

  • No single plug for every retail chain: Even under EDIFACT, every major buyer maintains custom subsets and mandatory segments; each new trading partner requires targeted sign-off testing.
  • Uneconomical for one-off buyers: For very low annual document volumes with a single partner, a web-EDI portal or structured e-invoice exchange is often smarter than a full integration.
  • Factor clearing fees transparently: When an external EDI clearing provider is connected for many retail partners, their ongoing transaction or partner fees apply separately.
  • No automatic cure for missing item hygiene: Unmaintained packaging units or duplicate EANs in the ERP cause runtime stops — master-data discipline always comes before automation.

Frequently asked questions about EDI Integration.

What trading, manufacturing, and logistics teams clarify before onboarding their first partner.

Which EDI message types and formats does Mate iT connect to the ERP?

Our focus is on the core operational supply-chain documents: ORDERS (purchase orders), ORDRSP (order confirmations), DESADV (despatch advice including SSCC/NVE and batches), and INVOIC (electronic invoices). Depending on partner requirements, we support EDIFACT/EANCOM, OpenTRANS, VDA profiles, and EN 16931 formats such as XRechnung and ZUGFeRD via Peppol.

Do we need an external EDI clearing provider or is a direct connection sufficient?

That depends on the number of trading partners and their technical requirements. For one or two large partners with clean SFTP, AS2, or Peppol endpoints, a lean direct connection is often cost-effective. As soon as multiple retail chains with custom subsets or VAN mandates enter the picture, we integrate a specialized EDI clearing partner cleanly into your ERP instead of duplicating every partner mapping.

How are GTIN, GLN, and partner-specific item numbers mapped?

Mapping runs directly off maintained ERP master data: customer billing and delivery sites are identified via GLN/ILN, products are matched by GTIN/EAN or partner SKU codes, and units of measure translate to ISO codes. In the blueprint phase, we specify upfront which mandatory fields must be maintained in product and partner records.

What happens when an incoming ORDERS message contains an error or unknown item?

Invalid or incomplete messages are never silently dropped or posted with wrong prices. They land with a clear error reason in a visible review queue, can be reprocessed selectively once master data is corrected, and remain fully logged.

How does classic EDI differ from e-invoicing (XRechnung and ZUGFeRD)?

Statutory e-invoicing under EN 16931 (XRechnung, ZUGFeRD, Peppol) covers structured invoice exchange only. Classic EDI automates the entire upstream supply chain — from purchase order to confirmation and pallet despatch advice through to invoicing. Both tracks combine cleanly on the same ERP data model.

One real workflow is all it takes.

A trading partner requires ORDERS, DESADV, or INVOIC via EDI or Peppol? Briefly tell us your ERP and required message types — we will identify the cleanest path into your system.

Matthias GrdanManaging Director · Process & ERP Architecture
Architecture & Integration TeamDedicated Project Lead · Villingen-Schwenningen

The introductory call is free of charge. Your inquiry is delivered directly via our Google Workspace mail service — or alternatively as a pre-filled email draft or one-click clipboard copy.

When an endpoint is configured, submissions are sent via our Google Workspace mail service; in local preview mode, a pre-filled email draft opens in your browser. Privacy Policy

Book a call