Why Your VAN Contract Is Quietly Overcharging You, And When AS2 Actually Pays Off
Let’s start with an uncomfortable question: when’s the last time you actually read your VAN invoice line by line? Not skimmed it — read it. Because most companies don’t, and that’s exactly how a billing model built for the 1980s is still quietly draining budgets in 2026.
How VAN pricing actually works (and why it’s built to grow)
Traditional VAN billing runs on two levers: kilocharacters (KC) and transactions. A KC is 1,000 characters, so a 250,000-character transmission works out to 250 KCs — at $0.20 per KC, that’s a $50 fee for one file. Multiply that across purchase orders, ASNs, invoices, and 997s, every day, across every partner, and you start to see the shape of the problem.
The standard VAN billing structure is a monthly fee based on transaction volume plus kilocharacters transmitted per transaction, which means the more detailed your EDI documents get (and they have gotten more detailed, with fuller carton/pallet hierarchies in ASNs and richer line-item data in invoices), the more you pay, simply because KC pricing was designed in an era when bandwidth and storage were genuinely expensive. It’s not tied to business value. It’s tied to file size.
Then there’s the part nobody puts in the sales deck. Many traditional providers charge $2,000–$5,000 annually per trading partner on top of transaction fees, regardless of how much volume actually moves through that connection, so onboarding five new retail partners can mean $10,000–$25,000 in costs before a single document changes hands. Add five new retailers this year? Congrats, you’ve just paid a five-figure “membership fee” for the privilege of trading with them.
The line items that should make you raise an eyebrow
Here’s where it gets murkier. Beyond the base KC rate, common add-ons include mailbox fees ($50–$200/month per mailbox), setup fees ($500–$5,000), trading partner fees ($10–$50/month each), per-message charges, and user seat fees ($25–$100/month each), and industry estimates put the cumulative cost of these hidden fees at $10,000–$50,000+ a year depending on company size. Overage fees, when your volume crosses a contracted cap, are typically priced at 2–3x your base rate.
To be fair, not every one of these fees is a scam, some reflect genuine infrastructure and support costs. But layered charges for things like mailbox access, archived data retrieval, and after-hours support on top of usage fees mean the advertised per-KC rate often understates the true per-transaction cost by the time everything’s added up. That’s the quiet part. The rate on the contract’s first page is rarely the rate you actually pay.
One honest caveat: a lot of the pricing data above comes from companies that sell alternatives to legacy VANs — Orderful, Nexus VAN, BOLD VAN, Commport. That doesn’t make the numbers wrong (the fee categories and ranges are consistent across multiple independent write-ups), but it’s worth knowing who’s telling you this and why, before you take any single vendor’s audit at face value.
Where AS2 actually changes the math
AS2 isn’t new, it’s decades old at this point, but it earned its place the hard way. Walmart announced its move away from VANs to the AS2 protocol in September 2002, requiring all suppliers to adopt it too, and set a hard deadline of September 30, 2003 for trading partners to comply. That single mandate is arguably the reason AS2 became the retail industry’s default rather than a niche option.
Forrester’s take on why mandates like this spread is blunt and, honestly, kind of refreshing in its cynicism: senior analyst Joe Cicman describes it as a power map — buyers like Walmart and Ford hold the leverage in the supply chain, and EDI (and by extension AS2) spreads because they mandate it, not because suppliers volunteer. Worth remembering next time someone frames a protocol choice as purely technical.
The economics behind AS2 are structurally different from VAN billing. Instead of a subscription that scales with volume, AS2 is mostly a fixed, upfront cost — hardware (or none, if you’re in the cloud), the OS, the AS2 application, plus modest ongoing maintenance — after which there’s no per-document ceiling, so the more data you move, the bigger the gap between what you’d pay a VAN and what you’re actually paying. That’s the whole pitch, and it’s a legitimate one: AS2 rewards volume instead of penalizing it.
A real-world example, for what it’s worth: Matisse Footwear, a footwear distributor, deployed an AS2/SFTP managed file transfer setup in about a week and reported recurring monthly savings in the thousands after eliminating per-message VAN fees. That’s a vendor case study, so treat the exact figures with the usual grain of salt — but the pattern (fast payback once volume is meaningful) shows up consistently across sources, not just this one.
Where AS2 stops being an obvious win
None of this means “rip out your VAN tomorrow.” AS2 has real costs that don’t show up in the marketing copy: certificate lifecycle management, firewall configuration, per-partner connection setup, and (critically) the fact that an AS2 server only supports AS2, so if your partner mix requires multiple protocols, you may end up managing several servers instead of one VAN relationship, which adds its own operational overhead. For a company with a handful of high-volume partners, that trade is usually worth it. For a company with dozens of low-volume, protocol-mixed partners, a VAN’s flat convenience might genuinely be cheaper — just say that out loud instead of pretending AS2 is free.
There’s also the compliance layer: interoperability isn’t guaranteed by default, which is why software providers submit their AS2 implementations for Drummond certification, an independent test suite that verifies conformance to the standard. Non-certified AS2 tools can and do break in production. If you’re going the AS2 route, that certification isn’t a nice-to-have — it’s the difference between “it works” and “it works until it doesn’t, at 2am, during a Walmart PO surge.”
The actual audit worth running
Before switching anything, pull 6–12 months of VAN invoices and separate real usage charges from the padding — trading partner fees, mailbox fees, archive access, “overage” line items. Then map that against your actual partner count and volume trend. If your volume is growing and concentrated across a few high-traffic partners (retail, especially, where Walmart alone requires eight core transaction sets from 810 to 997 moving constantly), AS2’s fixed-cost model tends to win. If your partner base is fragmented and low-volume, don’t assume the grass is greener — run the numbers per partner, not as one blended guess.
Getting this right — reading a VAN contract properly, knowing which AS2 tradeoffs are real versus sales talk, is exactly the kind of practical, no-spin skill.