What an EDI VAN Actually Does (in Plain Terms)
An EDI VAN is the postal service of the business world — except instead of paper mail, it routes purchase orders, invoices, and shipping notices between you and your trading partners, with a tracking receipt for every one. VAN stands for Value Added Network, and at its core it’s a secure, managed mailbox and router. Your partner drops a document into your “mailbox,” the VAN delivers it, and you both get confirmation it arrived intact.
The mailbox model has been around for decades, and newer internet-based options like AS2 and modern APIs let companies connect directly without a middleman. So why do VANs still dominate retail and manufacturing? Because big partners — think national retailers — often mandate VAN connectivity, and a single VAN gives you instant reach into thousands of pre-connected trading partners without setting up a separate direct link for each one.
Here’s what a VAN handles for you:
- Protocol translation — bridging different communication standards so your systems talk to theirs.
- Document tracking and delivery guarantees — proof that what you sent was received.
- Partner connectivity — access to an existing network instead of building connections from scratch.
One critical distinction: a VAN is not the same as EDI translation software, which maps documents into your ERP’s format. Some providers bundle both; some only do the network. Know which you’re buying.
Why Your Trading Partner Is Mandating EDI
That compliance email from your trading partner isn’t a punishment — it’s the cost of doing business with companies moving millions of transactions a year. Large retailers and manufacturers like Walmart, Target, and Amazon mandate EDI because manually keying purchase orders, invoices, and shipment notices doesn’t scale. Automating those documents cuts errors, speeds payment cycles, and keeps their warehouses synced with thousands of suppliers at once.
Your partner’s mandate will spell out exactly what they need, usually in an EDI spec or onboarding packet. Three things to look for:
- Required document types — almost always the 850 (purchase order), 810 (invoice), and 856 (advance ship notice, or ASN).
- Connection method — whether they expect a VAN interconnect, AS2, or SFTP.
- Testing and certification steps — a structured process where you send test documents until your formatting passes their checks.
Getting this wrong has real consequences. Non-compliant ASNs and mislabeled shipments are among the most common triggers for retailer chargebacks, which can run from $250 to several thousand dollars per incident. Failed certification or a missed connection method can also delay your go-live and strain the relationship before it starts.
So before you compare a single provider, read the partner’s spec closely. It tells you exactly which capabilities — document types, protocols, certification support — you actually need to buy.
The Criteria That Actually Separate VAN Providers
Once you know what your partner requires, you can evaluate providers against it. Here’s the dirty secret: their websites are nearly interchangeable, but their contracts are not. Five criteria do the real separating, and once you know them, the wall of similar names starts to organize itself.
Pricing model. This is where the surprises hide. Some providers charge a flat monthly fee ($50–$300 for low volume), others bill per kilocharacter (per chunk of data moved), and some charge per document. Per-kilocharacter pricing looks cheap until your volume climbs — then it balloons. Always ask about mailbox fees and one-time setup charges too.
Protocol and connectivity. Confirm support for AS2, SFTP, and modern APIs, plus interconnects to other VANs. Interconnects matter because your trading partner may sit on a different network, and you need the two to talk without you brokering it.
Onboarding speed. If you’re not an EDI expert, look for a managed-service option where the provider maps documents and handles testing for you. Self-service can mean weeks of trial and error against a compliance deadline.
Support quality. A dedicated rep who knows EDI beats a ticket queue every time. Ask about hours, response times, and whether support understands EDI standards versus reading a script.
Network reach and scale. Check that the provider already connects to your major partners and can absorb added trading partners and rising volume without renegotiation. The right answer here is the difference between one onboarding and ten.
Understanding VAN Pricing Models and Hidden Fees
The sticker price a VAN quotes you is almost never what you’ll actually pay. EDI VAN pricing typically follows one of three models, and the right fit depends entirely on your transaction volume.
- Per-document (or per-kilo-character) pricing: You pay for each document or block of data sent. Common ranges run $0.05–$0.25 per document or roughly $0.05–$0.10 per kilo-character. Great for low volume (a few hundred documents a month), painful as you scale.
- Tiered/bundled plans: A flat monthly fee (often $50–$300) that includes a set document allowance. Predictable until you exceed the bundle.
- Subscription/unlimited: A higher flat rate ($300–$1,000+) suited to high or growing volume where overages would otherwise hurt.
Hidden fees to flush out
- Per-document overage once you pass your bundle — this is where bills balloon.
- Setup/implementation charges, sometimes $500–$2,500 one-time.
- Mailbox-per-partner fees — a charge for each trading partner connection.
- Support tiers, where after-hours or priority help costs extra.
To forecast real monthly cost, estimate your document count per partner per month, multiply across all partners, then add fixed mailbox and support fees. Build in 20–30% growth headroom.
Before signing, ask the rep directly: What triggers an overage charge, and what does it cost? Are mailbox fees per partner or flat? What’s the all-in setup cost? Get the total cost of ownership in writing — not just the headline rate.
A Rundown of Leading EDI VAN Providers
The fastest way to narrow a wall of similar-sounding vendors is to stop comparing them all at once and instead match them to how your company operates. Most credible providers fall into three buckets, and which one fits depends on your team’s size, technical depth, and how aggressive your compliance deadline is.
Managed / Full-Service
SPS Commerce and TrueCommerce handle mapping, testing, and partner setup for you. Pricing leans toward subscription plus per-document fees, and both run massive retail partner networks. If a major retailer just handed you a mandate and you have no EDI staff, this is the fastest path to going live — often weeks, not months.
Flexible / Integration-Focused
Cleo and OpenText (Liaison) suit midsize-to-large companies that want control over how EDI connects to ERP and other systems. Pricing is platform-oriented and typically higher, but you gain protocol flexibility (AS2, API, SFTP) and room to scale across many trading partners.
Cost-Conscious / SMB
Babelway, DiCentral, and Loren Data’s ECGrid target smaller volumes and tighter budgets. ECGrid in particular is known for transparent, interconnect-focused pricing that avoids the per-kilo-character surprises that inflate bills as volume grows.
For a hard retail-mandate deadline with limited internal resources, the managed group usually wins on speed. If you have IT bandwidth and expect volume to climb, the flexible tier protects you from outgrowing your provider.
How to Choose Between Providers for Your Situation
The fastest way to narrow the field is to be honest about three things: how much time you have, how much EDI expertise lives inside your team, and what you can spend. Those three answers do most of the sorting for you.
Start with capacity. If nobody on your staff can read an 850 purchase order or troubleshoot a failed transmission, a fully managed service is worth the premium — you’ll pay more per month, often in the $300–$1,000 range depending on volume, but you skip the learning curve and hit your deadline. If you have developers and you’re integrating EDI into an ERP or custom system, lean toward a flexible, API-friendly provider that won’t box you in.
Before you fall in love with anyone, confirm one thing: the provider already connects to your mandating partner’s network. Most VANs interconnect, but verifying coverage upfront prevents a nasty surprise during go-live. Ask the vendor directly, by name, whether they currently route to that partner.
Then build a 2–3 vendor shortlist and request quotes scoped to your reality:
- Your specific document types (850s, 810s, 856s, etc.)
- Your estimated monthly transaction volume
- Setup fees, mailbox fees, and per-document or per-kilo-character charges spelled out
Apples-to-apples quotes give you something concrete to defend to your boss — and a paper trail if pricing creeps later.
Red Flags to Avoid When Signing a VAN Contract
The contract is where a friendly sales demo turns into a multi-year financial commitment, so this is where you slow down and read carefully. A few patterns tend to predict regret, and they’re easy to spot once you know what you’re looking at.
Watch for pricing you can’t forecast. If a provider quotes per-document or per-kilo-character rates with no volume estimate, no monthly cap, and no example tied to your projected transaction count, you’re signing a blank check. Ask them to model your expected volume in writing — typical mid-volume setups run roughly $50–$300 per month, and anyone unwilling to ballpark that range is hoping you won’t notice when it balloons.
Other red flags worth a hard pause:
- Multi-year lock-in with steep exit fees and no clause guaranteeing you can export your data and trading-partner setup if you leave.
- Unscoped onboarding timelines — “we’ll get you live soon” won’t survive a retailer’s compliance deadline. Get a dated implementation plan.
- Support sold as an upsell, where standard help is email-only and real assistance costs extra.
- No named go-live contact, leaving you in a ticket queue when a connection fails the week you’re supposed to launch.
If the FTC’s consumer complaint database or the Better Business Bureau shows a pattern of billing surprises for a vendor, treat that as your answer.
What to Expect During Onboarding and Go-Live
The good news: onboarding a single trading partner usually takes 2–6 weeks, not months — and most of the calendar time is waiting on testing windows, not heads-down technical work. Knowing the phases helps you spot when a project is drifting.
A typical managed onboarding moves through four stages:
- Kickoff: You hand over your trading partner’s EDI spec, transaction sets (like 850 purchase orders or 856 advance ship notices), and connection requirements. Usually a few days.
- Mapping and configuration: The provider builds the maps that translate your data into your partner’s required format. This is where a fully managed setup earns its fee — they own the technical heavy lifting.
- Partner testing and certification: You exchange test documents with your trading partner until they certify you. This is the most common bottleneck, because it depends on the partner’s availability.
- Production go-live: You flip the switch and start exchanging live transactions.
What drives delays is rarely the VAN itself — it’s slow responses on your side or your partner’s. To stay on schedule, request your partner’s testing calendar early, since large retailers often batch certifications into limited weekly windows. Confirm who owns each task in writing, and give your provider every spec document up front so mapping doesn’t stall.
One practical move: ask prospective providers for their average certification timeline with your specific trading partner. Experienced VANs have done it dozens of times and can flag the exact gotchas before they cost you the deadline.
