Request a quote
Emergency SectorsCareers About us Blog Get in touch
Warehouse worker scanning a box on a rack with a handheld scanner; a sensor and a small camera are mounted on the racking

EDI integration with your biggest customer: what IT has to handle

It usually starts with a letter from a large customer: from a given date, orders, despatch advices and invoices only by EDI. EDI integration sounds like a software choice, and partly it is. But what decides whether messages arrive every day sits underneath: certificates, the firewall, master data, and someone who notices a message is missing.

6 min read Written by the ITproposal team
Short answer

EDI integration exchanges orders, despatch advices and invoices in a fixed format between your system and your customer’s, with no email or PDF in between.

The software and the message translation come from an EDI provider or your ERP vendor; IT handles the connection, certificates, firewall and monitoring.

The hardest part is rarely technical: correct product and location codes, and someone who notices a message has not arrived.

What EDI integration is

EDI stands for Electronic Data Interchange: two businesses send each other commercial messages in a fixed, agreed format, straight from system to system. Your customer’s order no longer lands as a PDF in a mailbox but as a message your ERP reads itself. An order response, a despatch advice (often called an ASN) and an invoice go back.

Two things have to be right, and they are often confused:

  • The format. How a message is structured. In Europe that is often EDIFACT, in retail usually the GS1 subset EANCOM, and increasingly XML. In the United States, X12 is common.
  • The transport. How the message travels: over AS2 (a secured connection using certificates), over SFTP, or through the network of an EDI provider that passes messages on.

Between your ERP and that format sits a translation layer, the mapping. That is software and specialist work, and it comes from an EDI provider or your ERP vendor.

Three ways to connect

Which one fits depends mainly on the number of messages and the number of trading partners asking for EDI.

  • Through an EDI provider. They handle the connections to your customers, the mapping and passing messages on, and your ERP only talks to them. The most common choice once there is more than one partner, because each new customer becomes a connection at the provider rather than a project of its own.
  • A direct connection. Your own EDI software or your ERP’s EDI module talks to the customer over AS2 or SFTP. Fewer links in the chain, but all the management is yours: certificates, connections, updates and monitoring.
  • The customer’s web portal. You key in orders and fill in despatch advices on a website. Fine for a handful of orders a week, and it only moves the retyping to another screen.

Ask the same question of each option: who does the customer call when a message is rejected, and who fixes it?

Start with your customer’s EDI guide

Every large customer has an implementation guide: which messages they expect, in which version, which fields are mandatory, how quickly a response or despatch advice must follow, and how testing works. Read it first, together with whoever runs orders and the warehouse. Most delays are not technical but come from what that guide asks of your data.

  • Master data. Product codes (GTIN), location codes (GLN) and units in your ERP must match what the customer expects. You get those codes from GS1, not from IT.
  • Labels and despatch advices. A despatch advice often refers to an SSCC label on the pallet. The message and the label then have to come from the same source, which touches the warehouse printers and scanners. More on that in our article on scanners, Wi-Fi and the WMS in the warehouse.
  • A test phase with a date. Plan backwards from the customer’s go-live date, with time for rejected test messages.

What IT has to handle underneath

However the mapping is built, EDI integration depends on a few things that sit with IT. They are small, and any one of them can stop the flow of messages on an ordinary Tuesday.

  • Certificates with an expiry date. An AS2 connection runs on certificates at both ends. When one expires, the messages stop. Put the expiry dates in a calendar with an owner, and agree with the customer how a new certificate is exchanged.
  • The firewall. The customer or provider often connects from fixed addresses and expects you to do the same. Record which ports and addresses are open and why, so a firewall clean-up does not take the integration with it.
  • Keys and service accounts. An SFTP key or an account for the integration should not be in an employee’s name. When they leave, the integration leaves with them.
  • The machine it runs on. If the EDI software runs on your own server, that server belongs in normal management: updates, backup, monitoring. A forgotten server in a corner is a familiar cause.
  • Separate test and production. So a test message never ends up in the ERP as a real order.

A message that never arrives goes unnoticed

With an emailed order, someone sees the email. With EDI there is nothing to see when a message does not come: no order, no error, just an empty list. That is why monitoring is the part that pays off most.

  • Acknowledgements. AS2 returns a technical receipt, and EDIFACT has its own message to report that a message was received or rejected. Use them, and make a missing acknowledgement raise an alert.
  • Received is not processed. A message can arrive cleanly and then stick in the ERP on an unknown product code. Monitor both steps.
  • Alerts to a shared place, not one person’s mailbox, with an agreed person watching out of hours if the customer also orders at night.
  • A message archive. In a dispute about an order or invoice you want to show what was sent and when.

EDI and e-invoicing are two tracks

An invoice can go to your customer by EDI, and then e-invoicing looks done. That does not follow automatically. In Europe, e-invoicing increasingly runs over Peppol, a separate network with its own rules. In Belgium, structured e-invoices between businesses have been mandatory since 2026, and other countries have their own timetables.

Whether an EDI invoice meets those rules for a given customer, or whether you also need to invoice over Peppol, is a question for your finance system, your EDI provider and your accountant. For IT it means one thing: these are two integrations with two sets of rules, and both need monitoring.

Where our work stops

What we do. We handle the IT underneath EDI integration: the connection and firewall rules, management of certificates and keys with an owner and an expiry date, the server or cloud service the software runs on, service accounts not tied to an employee, backup, and monitoring that makes a stalled message flow visible before your customer calls.

What we do not do. The EDI software, the mapping and the message network belong to the EDI provider or your ERP vendor; we do not sell or build them. We are not a freight forwarder or a haulier: we do not send transport instructions on your behalf or handle customs. Product and location codes come from GS1, and whether your invoices meet tax rules is for your accountant.

Frequently asked

Questions we get about this

The five that come up most often.

What is EDI integration?

EDI integration exchanges business messages such as orders, despatch advices and invoices in a fixed format between your system and a trading partner’s, with no email or PDF in between. The format is often EDIFACT, EANCOM or XML, and messages travel over AS2, SFTP or an EDI provider’s network.

What is the difference between EDI and an API?

Both connect systems. EDI uses fixed message standards agreed across an industry and usually works with messages that are sent. An API is an interface a vendor designs itself, letting systems query each other directly. Large trading partners often require EDI because it lets them work the same way with hundreds of suppliers.

Do I need an EDI provider?

Not always, but with more than one partner it usually helps. A provider handles connections, mapping and passing messages on, so a new customer is a connection rather than a project. With a direct connection all the management is yours, including certificates and monitoring.

Why does EDI integration suddenly stop?

Often because of something small outside the software: an expired certificate, a firewall rule that was cleaned up, a key or account belonging to someone who left, or a server that dropped out of management. A message that arrives but sticks in the ERP on an unknown code also looks like a stalled integration.

Can you build our EDI mapping?

No. The EDI software, the mapping and the message network come from an EDI provider or your ERP vendor. We are not a freight forwarder and do not send transport instructions for you. We handle the IT underneath: connection, firewall, certificates, accounts, the server and monitoring.

Related services

Further reading

What the integration connects to.

Shall we check the IT under your EDI integration?

Send us your customer’s EDI guide and a sketch of how messages flow today. We will say what needs to be in place underneath; the mapping stays with your EDI provider.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call