A Value Added Network, or VAN, is one of those terms that shows up in the first hour of any EDI project and never quite gets explained. Trading partners assume you have one. Vendors quote prices for one. And somewhere in the paperwork is a line item for “network charges” that nobody on your team chose.
This guide explains what a VAN actually is, how it works, what the “value added” part means, and how to think about VAN costs and alternatives.
The Short Definition
A Value Added Network (VAN) is a private, secure network that routes electronic business documents between trading partners. Instead of building and maintaining a direct connection to every customer, supplier, and carrier you do business with, you connect once to the VAN, and the VAN handles delivery to everyone else.
The most useful mental model is a post office for business documents. Every company on the network has a mailbox. You drop outbound documents, purchase orders, invoices, advance ship notices, into your mailbox, and the VAN delivers each one to the right partner’s mailbox, in the format and over the protocol that partner requires. Inbound documents from your partners arrive in your mailbox the same way.
How a VAN Works in Practice
Under the hood, a few things happen to every document that moves through a VAN:
- Addressing and routing: every EDI trading partner has a unique identifier (an ISA qualifier and ID in the X12 world). The VAN reads the envelope of each document and routes it to the mailbox that matches the receiver’s ID.
- Protocol bridging: your systems might connect to the VAN over SFTP. Your trading partner might connect over AS2, HTTPS, or an API. Neither side has to care, because the VAN speaks all of them and translates between connection methods automatically.
- Delivery tracking: the VAN logs when each document was received, delivered, and picked up. When a partner claims they never got your invoice, that audit trail settles the question in minutes instead of days. In twenty-five years of running EDI operations, this is the VAN feature that has ended more disputes than any other.
- Interconnects: not every company uses the same VAN. Established VANs maintain interconnect agreements with each other, so a document sent through your VAN can reach a partner on a different one, much like email moving between providers.
What Does “Value Added” Actually Mean?
The name is a holdover from the era when the alternative was a bare leased data line. The “value” is everything the network does beyond moving bytes: mailboxing, routing, protocol handling, delivery confirmation, retransmission of lost documents, and an audit trail for every exchange.
Modern VAN services often layer on more: document validation against trading partner specifications before transmission, translation between EDI standards and internal formats, long-term document archiving for compliance audits and chargeback disputes, alerting when an expected document does not arrive on schedule, partner onboarding and connection testing, and visibility dashboards that show traffic across all partners in one place. Which of these are included versus billed separately varies widely by provider, and it is worth asking specifically.
VAN vs. Direct Connections (Point-to-Point)
The main alternative to a VAN is connecting to each trading partner directly, usually over AS2 or SFTP. Direct connections avoid network fees, and some very large retailers require them. But each one is a separate project: certificates to exchange and renew, firewall rules to maintain, connection tests to schedule with the partner’s technical team, and a distinct point of failure to monitor.
With a handful of high-volume partners, direct connections can make sense. With dozens of partners, each with their own requirements and technical contacts, the math usually favors one managed connection to a VAN over thirty direct connections you have to babysit individually. Many companies land on a hybrid: direct AS2 with the two or three partners who demand it, and a VAN for everyone else. That hybrid is the most common arrangement we see in practice, and it is rarely something companies plan; it accumulates one partner requirement at a time, which is exactly why having one team monitor all of it under one roof matters more than which protocol any single partner uses.
How VAN Pricing Works
Traditional VAN pricing is usage-based, and the unit is usually the kilocharacter, a thousand characters of data transmitted. This surprises people used to per-document or per-transaction pricing, but it is the industry’s historical billing standard, and it has a practical upside: a short purchase order costs less to move than a thousand-line invoice, and your network cost tracks your actual data volume rather than a flat per-document toll.
When you evaluate any EDI arrangement, the question to ask is which charges are fixed and which scale with volume. Setup, mapping, and monthly service fees are typically fixed; network traffic is typically the variable piece. Our guide to EDI pricing models breaks down how providers structure these fees, and what to watch for.
Do You Still Need a VAN in 2026?
APIs and direct internet protocols have been “replacing” the VAN for twenty years, and yet VANs still carry an enormous share of B2B document traffic. The reason is simple: the VAN model solves a coordination problem that does not go away. Every new connection method adds options, but your trading partners still use different protocols, different standards, and different networks, and something still has to bridge them.
The more useful question is not whether a VAN is old technology. It is whether you want to operate the connectivity layer yourself. That includes watching for failed deliveries, chasing missing acknowledgments, renewing certificates, and picking up the phone when a partner changes requirements. The network is rarely the hard part; the ongoing operation of it is.
The Managed Alternative
This is why many mid-market manufacturers and distributors fold VAN connectivity into a managed EDI service rather than administering it in-house. In that model, one provider operates the network connection, performs the mapping and translation, monitors every document’s delivery, and handles partner changes, so the VAN becomes something that simply works in the background rather than a system your team logs into.
Foundational operates its own fully managed Value Added Network as part of its managed EDI service: one connection that reaches every trading partner over AS2, SFTP, HTTPS, or API, with routing, translation, and monitoring handled by our EDI team, and network traffic quoted upfront by data volume.
Key Takeaways
- A VAN is a secure intermediary network that routes EDI documents between trading partners, one connection instead of many.
- The “value added” services are routing, protocol bridging, delivery tracking, retransmission, and audit trails.
- VAN traffic is traditionally billed by data volume (kilocharacter), not per document.
- Direct AS2/SFTP connections make sense for a few high-volume partners; VANs win when partner counts grow.
- The real decision is not VAN vs. no VAN, it is who operates the connectivity layer and monitors it day to day.
If you are weighing connectivity options for an upcoming EDI project, talk to Foundational, we can walk through your trading partner list and map out the simplest way to reach all of them.
Ready to simplify your EDI operations?
Talk to a specialist about your trading partners, ERP, and current EDI setup. Talk to a Specialist