The old EDI model was designed for enterprises — and priced accordingly
Cast your mind back to how EDI worked for a typical UK SMB trying to supply a major retailer ten years ago. You'd contact a VAN provider, receive a quote for setup that started in the low five figures and climbed from there depending on how many trading partners you needed. The onboarding process took three to six weeks. You'd pay per-transaction fees on top of the setup, and if you wanted to add a new retailer relationship, the entire process started again.
None of this was unreasonable given the technology of the time. EDI translation required specialist infrastructure. VAN routing required network agreements. Testing against a retailer's EDI specification was a manual, iterative process. The costs reflected the genuine complexity of what was being done.
The problem is that the pricing model never really changed, even as the underlying technology did. For years, the EDI industry continued charging enterprise rates to businesses for whom those rates represented a significant portion of the margin they were trying to protect in the first place.
Typical legacy EDI setup cost for a UK SMB
Setup fees, VAN account charges, and first-year integration costs before a single order has been processed. Per-transaction fees and annual maintenance apply on top.
What's changed — and why it matters now
Three shifts have happened simultaneously, and their combined effect is that the cost and complexity of EDI for UK SMBs has dropped dramatically.
API-native integration has replaced proprietary translation layers
The core function of an EDI translation layer — converting your business data into a structured format your trading partner can process — is now achievable through modern API infrastructure at a fraction of the cost of proprietary middleware. Where setup once required weeks of specialist configuration, API-driven EDI connections can be established and tested in days. The translation logic that used to live in expensive, inflexible software now lives in configurable, maintainable integration platforms.
Subscription pricing has replaced per-connection fees
The economic model that made EDI prohibitive for SMBs was one where every new trading partner was a new cost event. Adding a fourth retail relationship meant a fourth setup fee, a fourth VAN account, a fourth annual maintenance charge. Growth was financially penalised. Modern integration platforms charge a predictable monthly subscription that covers the platform itself — not one that scales per trading partner. The tenth retailer costs no more to connect than the first.
Managed platforms have absorbed the operational expertise requirement
Understanding EDI specifications, managing VAN connectivity, handling retailer-specific implementation quirks — this used to require in-house expertise that most SMBs couldn't justify employing full-time. Managed integration platforms have absorbed that expertise into the service itself. The knowledge of how Tesco's ORDHDR implementation differs from Sainsbury's, how Ocado's CFC model affects DESADV timing, how to handle mixed Tradacoms/EDIFACT syntax on the same AS2 connection — that's embedded in the platform, not billed by the hour.
The operations cost that doesn't show up on any invoice
The setup fees were visible. The more significant cost for most SMBs was the operational overhead that EDI processes generated when they weren't properly automated — and that overhead is harder to measure because it shows up as staff time rather than a line item.
Multiply those hours across a week of orders from multiple retail relationships, and the picture becomes clear: the actual cost of under-automated EDI for a growing SMB isn't primarily the setup fee. It's the ongoing staff time consumed by tasks that should be invisible. That time has an opportunity cost — it's time not spent on the commercial, creative, and strategic work that actually differentiates the business.
What modern EDI integration actually connects
The shift from legacy EDI to modern integration isn't just a cost story — it's a connectivity story. Legacy EDI solutions typically handled the document exchange layer in isolation. Modern integration platforms connect that layer to the rest of the operation.
A retailer purchase order that arrives via EDI should automatically become a sales order in the ERP. The despatch event in the warehouse management system should automatically trigger the ASN. The invoice should pull from confirmed shipment data in the finance system. When all of these connections are in place, EDI stops being a separate process that requires human coordination and becomes part of the automatic flow of operational data.
The systems most UK SMBs are already running all support this kind of connected operation — the platform sitting between them handles the translation, routing, and compliance layer that makes it work reliably. In practice this looks like:
- ERP and inventory systems — Unleashed, Enterpryze, CIN7 Core, CIN7 Omni, Linnworks, SAP Business One. Retailer POs become sales orders automatically; stock levels flow back to inform fulfilment decisions.
- Finance systems — Xero is a common destination where confirmed shipments push through as draft invoices, ready for review and approval without manual creation. Sales order data, line items, and quantities arrive pre-mapped.
- 3PL and warehouse systems — Mintsoft, Zendbox, Logiwa and others receive fulfilment instructions from the ERP and return despatch confirmations that trigger the outbound ASN automatically. The 3PL and the retailer EDI layer stay in sync without anyone managing the handoff manually.
The practical result for an operations team is that a retailer order arriving at 6pm on a Friday is processed, routed to the 3PL, acknowledged, and — once despatched — triggers the ASN and draft invoice without anyone touching it. The team picks it up Monday morning as a completed flow, not a weekend backlog.
"The businesses winning in retail right now aren't the ones with the largest EDI budgets. They're the ones whose EDI runs quietly in the background while everyone else is focused on selling."
The practical questions worth asking before switching
If you're currently on a legacy EDI setup, or considering EDI for the first time, the questions that actually matter are:
- Are your specific trading partners already supported? The difference between a platform that can theoretically support a retailer and one that has active, maintained connections with operational knowledge of their actual requirements is significant. Ask specifically about the retailers you need, not "EDI in general".
- Does it connect to your ERP and finance system? An EDI layer that isn't integrated with your operational systems isn't automation — it's a different kind of manual process. The integration question matters as much as the EDI question.
- What happens when a retailer updates their specification? Major UK retailers update their EDI requirements periodically. Understanding who is responsible for maintaining those updates — you or the platform — is a critical due diligence question.
- How are errors surfaced? If something goes wrong with an EDI message at 11pm on a Saturday, when do you find out? Real-time monitoring and alerting is not a premium feature — it's a baseline requirement for any EDI integration that needs to be reliable.
- What does the total cost of ownership actually look like? Don't compare setup fees in isolation. Compare the subscription cost, the one-off connection build costs, and the operational overhead across a full year. The total picture is usually more compelling for modern platforms than the individual line items suggest.
Retail EDI trading partners supported by Supply Lens
Including Tesco, Sainsbury's, Ocado, Waitrose, Musgrave and major wholesale networks — with pre-built knowledge of their actual implementation requirements, not just the published specifications.
The bottom line for UK SMBs in 2026
The access barrier to professional, reliable EDI has fallen considerably. The technical infrastructure that once required enterprise budgets to operate is now accessible via monthly subscription pricing that a business at almost any scale can justify.
What hasn't changed is the underlying requirement: if you're supplying major UK retailers, correct and timely EDI is not optional. The risk of getting it wrong — chargebacks, failed compliance tests, damaged trading relationships — is real and financial. The difference in 2026 is that getting it right no longer requires spending a significant sum before you've shipped your first order.
The SMBs that are gaining ground in retail aren't doing so because they've found a way to avoid EDI. They're doing so because they've found a way to make it cost-effective, reliable, and invisible — freeing their operations teams to focus on the things that actually drive growth.
See what modern EDI looks like for your operation
Tell us which retailers you're trading with or targeting, and we'll show you exactly what the connection covers, how long it takes, and what it costs. No obligation.