All insights

EDI vs order automation: which does a wholesaler need?

Pull up a typical UK wholesaler’s customer list and sort it by how orders arrive. A handful of large accounts may send orders electronically, straight from their system to yours. Everyone else, often hundreds of independent shops, trade buyers and site managers, sends an email with a PDF, a spreadsheet or a few lines typed into the message.

That split decides the EDI vs order automation question. EDI is the right tool when a large customer requires it and sends enough volume to justify setting it up. Email order automation is the right tool for the long tail of customers who will never use EDI, and for most small and mid-sized wholesalers that long tail is where the manual work sits.

What is EDI, in plain English?

EDI stands for electronic data interchange. It’s an agreed way for two businesses’ computer systems to send each other documents such as purchase orders, order acknowledgements, despatch notes and invoices, without anyone typing them.

Both sides agree the message format in advance, so your system knows exactly which part of the message is the product code and which is the quantity. Several standards exist. EDIFACT is widely used internationally, ANSI X12 is common in North America, and parts of UK retail have historically used TRADACOMS, though which standard a given customer uses is something to confirm with them directly. Many retailers also publish their own implementation guide setting out how they use the standard.

Messages usually travel through an EDI provider or network, or over a direct connection between the two businesses. Most wholesalers don’t build this themselves. They use a provider who handles the connection to each trading partner and translates messages into something their ERP can import.

When is EDI the right choice?

EDI is a good fit when:

  • A customer mandates it. Large retailers and some big distributors make EDI a condition of supply. If they require it, there isn’t really a choice.
  • Volume from one partner is high. Setting up and testing a link with each trading partner takes effort. That effort pays back when one customer sends a lot of orders.
  • You need more than orders. EDI typically covers the whole cycle: acknowledgements, advance shipping notices and invoices. Big customers often expect all of them.
  • Both sides want zero interpretation. A well-formed EDI message has no ambiguity, so no reading or checking of the order’s layout is needed.

If you supply a national retailer, EDI is likely to be part of the relationship, and it would be wrong to suggest email automation as a substitute for it.

Do I need EDI if my customers email their orders?

Usually not for those customers. EDI only works when the sender has it too, and most small trade customers don’t. A builders’ merchant with three branches, an independent garden centre or a café group isn’t going to buy EDI to place a weekly order with you. They’ll keep emailing a PDF from their accounting software, or a spreadsheet, or a list in the body of the email.

You can’t switch them to EDI, and asking them to use a portal or web shop works for some and not for others. Many buyers prefer to order the way they order from every other supplier. Making them change risks the account.

That’s the gap email order automation is designed for. It reads what customers already send.

How email order automation covers the long tail

Email order automation monitors your order inbox and reads each email together with its attachments: typed or scanned PDFs, Excel and CSV files, Word documents. AI extracts the customer, PO number, delivery details and order lines, and gives every field a confidence score. Anything below 7 out of 10 is flagged, and missing details are left blank rather than guessed. There’s a fuller explanation in how AI reads a purchase order.

Each order then goes into a review queue where every line is checked against your ERP for product code, stock and price, and the customer is matched to the right account. A person approves the order, and it’s created in the ERP as a sales order with the customer’s PO number as the reference.

The difference from EDI is that nothing is agreed in advance with the customer. A new customer with a new layout can send an order tomorrow and it will be read. The trade-off is that AI reading is interpretation rather than a fixed format, which is why a person reviews each order before it reaches the ERP. You can see how capture works on our order capture page.

EDI vs order automation compared

EDI Email order automation
Who sends it Large customers with EDI capability Any customer with an email address
Customer has to change anything Yes, both sides set up and test the link No, they keep sending what they send now
Format Fixed, agreed standard Whatever arrives: PDF, scan, spreadsheet, Word, email text
Set-up per customer A link to set up and test for each trading partner None per customer
Accuracy Exact, if the message is well formed High, with confidence scores and human review
Documents covered Orders, acknowledgements, despatch notices, invoices Incoming orders
Best for A few high-volume accounts that require it The long tail of smaller accounts
Where it ends up Your ERP Your ERP

Can EDI and order automation work together?

Yes, and for many wholesalers that’s the realistic end state. Both feed the same ERP, which stays the system of record. EDI orders arrive from the large accounts through the EDI provider’s import. Emailed orders arrive through the review queue. Your warehouse and accounts team see one set of sales orders, whichever route they came in by.

A sensible way to plan it:

  1. List your customers by how they order. Note who sends EDI, who emails, who uses your web shop and who phones.
  2. Count orders per route. Use a normal month. The number of emailed orders is often larger than expected once you add up all the small accounts.
  3. Keep EDI where it’s required. If a retailer mandates it, stay on it or set it up with a provider.
  4. Automate the email route. That’s usually where the typing time and keying mistakes sit.
  5. Bring the other routes into the same queue. Web shop orders and phone orders can be added to the review queue too, so the office works from one list.

If you only have one or two large customers asking about EDI, ask whether they’ll accept orders by email in the meantime. Some will, some won’t, and the answer decides your timetable.

Which should you do first?

If a customer is mandating EDI as a condition of keeping the account, that comes first. Otherwise, start with whichever route carries most of your manual work. For a wholesaler with a long tail of smaller accounts, that’s usually email, because it’s where the variety is. Our guide to email order processing automation covers that route in more detail.

Your integration connects the email route to the same ERP your EDI feeds, so the two run side by side without either getting in the other’s way. If you’d like to map out your own order routes, talk to us on a free discovery call and we’ll tell you whether email automation would make a difference.