1. What EDI is and why it matters
EDI stands for Electronic Data Interchange, the structured exchange of documents between computer systems. Instead of an email with an attachment or a file copied by hand, two companies exchange messages with an agreed structure: orders, confirmations, transport documents, shipping notices. Each field has a precise meaning, and the receiving system can process the message without a person reading it.
The practical benefit is fewer retyping errors and shorter waiting times, because the data enters the system once and in the expected format. The drawback is that the channel requires agreements, configuration and controls, and that a format error can block all of a partner's messages. It is not a shortcut: it is a channel that must be designed and maintained like any other critical business process.
2. What to prepare before you start
Before touching any configuration, it helps to have a clear picture of partners, documents and responsibilities. Many projects slow down not for technical reasons but because these elements were never defined at the outset. If you clarify them first, the technical part becomes a consequence of decisions already taken, rather than the place where everything is decided in a hurry. Once the picture is clear, choosing the format becomes almost automatic.
Gather these elements and bring them to the first meeting with the partner. If the partner does not yet have a format, ask them to propose one and compare it with the one you already use. Every missing element should be recorded as an open point, with an owner and a date, so the meeting produces decisions rather than impressions. Also ask who, on the partner's side, will handle rejected messages.
- List of partners to connect, with their role: customer, carrier, service provider.
- Documents to exchange with each partner, with the direction of the flow.
- Message format and structure that the partner already uses or is willing to use.
- An internal technical contact and a process contact for each connection.
- A written agreement with each partner on exchange rules, timing and error handling.
3. Steps to set up the exchange
Setup follows a sequence. Skipping a step usually forces you to go back, and the step most often skipped is testing. Each phase should close with a verified outcome before moving on, because an error discovered in production costs far more than one found during a test agreed with the partner. Record the outcome of each phase in the project log.
The EDI or software provider should guide you through this sequence. If they do not, ask for the plan to be written down, with dates, owners and acceptance criteria for each phase. A written plan lets you check progress without depending on one person's memory, and see straight away whether the project is slipping. Also ask who will support you during testing.
- Define, for each partner, the documents, the format and the direction of exchange.
- Agree with the partner on the message layout and the list of mandatory fields.
- Configure the transmission channel and credentials, with personal, non-shared access.
- Map the message fields to the data in your management system, checking every correspondence.
- Run tests with trial messages, first with a few documents and then with real cases.
- Enable acknowledgement of receipt and error handling, so every message has an outcome.
- Start production with a period of parallel running and a contact person available.
4. Common mistakes to avoid
The first mistake is mapping fields in a hurry, assuming a code means the same thing to everyone. Units of measure, location codes and item codes change from partner to partner, and a wrong match produces documents that look correct but are wrong. Every mapping should be confirmed with the people who use the data every day, and preferably with a real partner document in front of you.
The second mistake is failing to handle rejected messages. If a document is discarded and nobody notices, the partner waits for a reply that never arrives. You need an error queue with an owner who checks it and a channel for reporting errors to the partner. A third common mistake is sharing the same credentials between several people, which makes it impossible to know who sent what.
5. How to check it works
Verification goes beyond confirming that the message was sent. Check that it arrived, that it was read correctly and that the data is consistent with the original order. A well-designed test includes at least one normal document, one with missing data and one with an unrecognised code, to see how the system reacts. Record the result of each case, so the test can be repeated after every change.
Also set up a periodic reconciliation: compare the orders sent with the confirmations received and flag the differences. This check is often neglected, yet it is what brings hidden problems to light before they become disputes with customers or carriers. Assign a specific person to do it, with a fixed deadline and a simple form for the differences found.
6. What to do after go-live
The exchange changes over time. Partners update their formats, add fields and change processes. Ask that every change goes through an agreed communication channel and is tested before it reaches production. A format changed without notice is one of the most common causes of sudden blockages, and it often only comes to light when a document is no longer accepted.
Keep a register of active connections, with the contact for each, the format version and the date of the last check. Review it at least once a year, and every time someone on the team changes, because without this register the knowledge is lost. A simple, up-to-date, shared register is worth more than long documentation nobody opens. Include it in the team's work plan.
7. How to start
The first step this week is a list of the partners and documents exchanged today, even if it happens by email or by file. For each document, write who sends it, who receives it and how many times it is handled by hand. This list immediately shows where EDI would add the most value, and it often reveals documents that nobody any longer knows why they are sent.
Then ask your most important partner which formats they use and whether they are willing to run a trial. With that answer you can decide whether to proceed and with which provider. If the partner does not yet have a solution, work together on a simple, agreed format rather than imposing a one-sided layout. Also ask how long they need to respond to test runs, so that you can plan the project realistically.
Frequently Asked Questions
Is EDI only for large companies?
No. The channel can be useful for small businesses too, if they have a few partners but many repetitive documents. Volume and repetitiveness of flows matter more than size. For smaller businesses there are managed services, which reduce the initial technical investment. Check with your partners which format they use before choosing.
Do I have to use the same format with every partner?
Usually not. Each partner may have a different layout or variant, even if the base format is the same. This is why mapping is done per partner and per document. Ask every partner for their specification and keep it in a shared archive that is up to date and easy to consult.
What happens if a message does not arrive?
It depends on how the channel was set up. A good system provides an acknowledgement of receipt and an error queue with an owner. Without these mechanisms a message can be lost without anyone noticing. Check with the provider how undelivered messages are handled and who receives the alert.
Is EDI exchange secure?
Security depends on the channel, the access controls and the checks in place. You need personal credentials, access logging, encryption of the transmission and a check on message integrity. If messages contain personal data, such as recipients' contact details, the exchange must be recorded in the register of processing activities. Ask the provider how they document these aspects.
Who is liable if a document contains incorrect data?
Liability should be defined in the agreement with the partner, before go-live. In practice the data is generated by your system, so the initial check rests with you. Mapping checks and periodic reconciliations reduce the risk. For contractual and legal aspects, seek advice from an adviser.