EDI integration that every partner understands .
Retailers require EDIFACT, a carrier wants AS2, the government asks for PEPPOL and your ERP speaks none of the three. We build one EDI layer that translates between all those formats and your systems. New partner on board? Connect instead of rebuild.
EDI is old, our approach is not .
EDI has existed longer than most webshops, and it is not going anywhere for now. Large retailers, carriers and manufacturers run their entire chain on it. Whoever wants to take part has to be able to send and receive their messages flawlessly.
Since 2008 we have been building the layer in between: an EDI integration that translates ORDERS, DESADV and INVOIC to and from the format that your ERP does understand. Set it up well once, then every new partner is a configuration instead of a project.
What changes with an EDI integration ?
From per-partner panic to a chain that simply keeps running.
- A separate piece of custom work for every retailer that nobody dares to touch anymore.
- Retyping orders from partner portals into your own ERP.
- Packing slips and DESADV messages too late, with retailer fines as a result.
- A rejected message is only noticed when the customer calls asking where their delivery is.
- Connecting a new trading partner takes months and a lot of nerves.
- One EDI layer with just a mapping and a small agreement about transport per partner.
- Incoming ORDERS automatically appear as sales orders in your ERP.
- DESADV and INVOIC go out on time and in the right format.
- Rejected messages trigger an instant alert, with the reason included.
- You connect a new partner in days to weeks, not months.
What's inside our EDI layer .
Four building blocks that together make the difference between loose connections and a chain you can build on.
Message translation
ORDERS, ORDRSP, DESADV and INVOIC translated between EDIFACT, X12, XML, JSON or CSV. Your ERP doesn't even notice the partner speaks a different dialect.
Transport & protocols
AS2, OFTP2, SFTP or a VAN mailbox, whatever is standard for each partner. We handle certificates, signatures and acknowledgements.
PEPPOL e-invoicing
Invoices via the PEPPOL network to governments and companies that require e-invoicing. Straight from your existing invoicing flow.
Monitoring & error handling
Every message tracked from source to confirmation. If something gets stuck, we see it first, with retries, alerts and an audit trail to fall back on.
Systems we connect through EDI .
A selection of the ERPs and standards we've hooked into an EDI chain before. Don't see your package? As long as there's an interface, we'll get it EDI-ready.
SAP
IDoc and API integrations between SAP and your partners' EDI messages.
Oracle
Order flows between Oracle environments and EDIFACT or X12 partners.
Exact
Making Exact speak full EDI without its own EDI module.
AFAS
Retailer orders coming in as EDIFACT, neatly into Profit via connectors.
GS1
GTINs, GLN addressing and GS1 guidelines applied correctly in every message.
Excel
Partners without EDI? They deliver Excel, we translate it into the chain.
From first call to running EDI integration .
A fixed rhythm so you know where we stand, and why.
Process Scan
One hour, free. We map your partners, message types and current bottlenecks. Including the requirements retailers or carriers have imposed on you.
Scope & fixed-fee quote
For each partner we document which messages, standards and protocols are involved. That results in a fixed-fee quote, with an onboarding order that works.
Build & test
We set up the EDI layer, build the mappings and test with real messages against your partner's test environment, until both sides sign off.
Go-live
Live partner by partner, starting where the pressure is highest. The rest then connects to the same layer.
Management & monitoring
Message monitoring, certificate management and error handling under SLA. Adding a partner or message type is configuration, not a new project.
One EDI layer for a complete logistics chain .
A logistics service provider exchanged orders, shipping messages and status updates daily with dozens of shippers and carriers. Every relationship had its own format and its own agreements, and every change meant digging through old scripts.
We replaced that tangle with one central EDI layer. Messages come in via AS2, SFTP or mailbox, are translated to the internal format and tracked until the confirmation is back. New chain partners now connect without adding any code.
- Dozens of chain partners on one EDI layer.
- Every message traceable from receipt to confirmation.
- New partners connected in days instead of months.
Frequently asked questions.
Werken jullie samen met onze IT-partner of leverancier?
Graag. Wij bouwen de koppeling of het portaal en de integratielaag eromheen; jouw partner of interne afdeling regelt waar nodig de inrichting en autorisaties aan hun kant. We documenteren elke interface, zodat het voor iedereen navolgbaar blijft.
Wat kost een koppeling of portaal?
Dat hangt af van de stromen, systemen en schermen die meedoen. Na de gratis proces-scan krijg je een fixed-fee offerte: één vast bedrag voor een afgesproken scope. Geen uurtje-factuurtje met open eind en geen meerwerk-discussies achteraf.
Hoe lang duurt het voordat het live staat?
Een gangbare koppeling tussen twee systemen staat in 4 tot 6 weken op productie. Zwaardere trajecten, bijvoorbeeld met SAP, meerdere administraties of een datamigratie, lopen tot 8 weken of langer. Wat voor jou geldt, zie je vooraf terug in de planning.
Welke systemen kunnen jullie koppelen?
In de praktijk vrijwel alles met een API, EDI-bericht, database of bestandsexport. Denk aan ERP's als Exact, AFAS, SAP, Dynamics en Oracle, webshops als Shopify, WooCommerce en Magento, WMS-pakketten als Boltrics, en betaalproviders, PIM- en CRM-systemen. Staat jouw pakket er niet bij? Dan kijken we in de proces-scan of het kan.
Wat gebeurt er als een systeem of API even uitvalt?
Elke koppeling heeft retry-logica met exponential backoff. Berichten die niet doorkomen, landen in een wachtrij en gaan alsnog door zodra het systeem weer reageert. Er gaat niets verloren, en je ziet in de monitoring wat er speelt.
Which EDI standards and message types do you support?
The common standards: EDIFACT, ANSI X12, GS1 variants and PEPPOL BIS, alongside XML, JSON and CSV for partners that don't run classic EDI. In terms of messages it's usually ORDERS, ORDRSP, DESADV and INVOIC, but we also cover inventory and status messages.
Do we need a VAN mailbox or can it go directly via AS2?
Both work, and often it's a mix. Direct AS2 or OFTP2 connections are cheaper to run and faster, a VAN is sometimes mandatory because the partner requires it. We advise per partner what makes sense and manage both options.
Our ERP has no EDI module. Is that a problem?
No, that's exactly our job. The EDI layer translates your partners' messages into what your ERP can actually receive: an API call, an import or a database connection. We even bring legacy packages without a modern interface into the chain this way.
How do we see whether a message arrived correctly?
Every message is tracked from dispatch to the partner's functional acknowledgement. If an acknowledgement fails to arrive or a message is rejected, a retry follows automatically, and persistent errors trigger an alert with the cause. You stay informed through reports and the audit trail.
Is it GDPR-proof?
Ja. Encryptie at rest en in transit, EU-hosting en een verwerkersovereenkomst horen er standaard bij. We verwerken alleen de gegevens die functioneel nodig zijn en hanteren heldere bewaartermijnen.
Also interesting .
Other integrations and solutions that often sit alongside this one.
Book a free process scan .
In one hour we map your partners, messages and bottlenecks. Then a fixed-fee quote. No surprises afterwards.