# EDI VAN Explained: What It Is and When You Need One > Learn what an EDI VAN (Value Added Network) is, how it works, what it costs, and when direct connections or API-based alternatives make more sense. An EDI VAN (Value Added Network) is a third-party mailbox service that routes EDI documents between trading partners. You connect once to the VAN; it handles delivery to your partners' mailboxes. VANs add cost per kilocharacter but simplify connectivity—most suppliers use them until volume justifies direct AS2 connections. **An EDI VAN (Value Added Network) is a managed intermediary service that routes EDI documents between trading partners, handling transport, delivery tracking, and format translation for companies that need to trade with multiple retailers without building separate point-to-point connections.** If you've been told you need a VAN to trade EDI documents with a retailer, you're probably wondering what it actually does, what it costs, and whether you really need one. This guide breaks down how EDI VANs work, what providers charge, and when alternatives like AS2, SFTP, or API connections make more sense for your business. ## What Is an EDI VAN? **An EDI VAN (Value Added Network) is a private, managed network that acts as an intermediary between trading partners, routing [X12 EDI documents](https://x12.org/products/transaction-sets) from sender to receiver, handling connectivity, translation, and delivery confirmation so you only need one connection instead of one per trading partner.** The easiest way to understand a VAN is the **mailbox analogy**. When you send an EDI purchase order through a VAN, you're dropping it into your outbound mailbox. The VAN picks it up, figures out where it needs to go, and deposits it into your trading partner's inbound mailbox. Your partner checks their mailbox, retrieves the document, and processes it. This model solved a real problem in the 1980s and 1990s. Before VANs, companies had to establish point-to-point connections with every single trading partner. If you traded with 50 retailers, you needed 50 separate communication links. A VAN reduced that to one connection: yours to the VAN. The VAN handled routing to everyone else. Standards and context for EDI VANs: - The [ASC X12 standards body](https://x12.org) defines the document formats (850, 856, 810, 997) that VANs transport, but X12 governs format only; VANs handle the delivery layer - [DISA (Data Interchange Standards Association)](https://www.disa.org) maintains the X12 secretariat and provides VAN industry context, including guidelines on interoperability between different VAN providers For a broader overview of how EDI works, check out our [essential guide to EDI](/blog/essential-guide-to-edi). ## How a VAN Works A VAN does three core things: message routing, format translation, and monitoring. ### Message Routing When you send an EDI document (say, an 810 invoice), you transmit it to the VAN using a protocol like AS2 or SFTP. The VAN reads the envelope segments (ISA/GS headers) to identify the receiver, then deposits the document into the correct trading partner's mailbox. If your partner uses a different VAN, the two VANs handle the interconnect automatically. ### Format Translation Some VANs offer translation services. If your system outputs flat files or CSV, the VAN can convert that into proper [X12 EDI format](https://x12.org/products/transaction-sets) before delivering it. This is where the "value added" part of the name comes from. Not all VANs include translation in their base pricing, and many charge extra for it. ### Monitoring and Compliance VANs track document delivery status, flag failed transmissions, and generate audit trails. If a functional acknowledgment (997) doesn't come back within the expected window, the VAN can alert you. Some VANs also validate documents against trading partner specs before delivery, catching errors early. You can also validate your EDI documents before sending them through a VAN by using our [free EDI Inspector](/edi-inspector), which parses and checks EDI files right in your browser. ## VAN Pricing and Fee Structure VAN pricing is notoriously opaque. Most providers don't publish their rates, and costs vary based on volume, document types, and contract terms. Here's what the typical fee structure looks like: ### Common VAN Fee Components - **Monthly base fee:** $150 to $500/month for basic connectivity and mailbox access - **Per-KCH (kilo-character) fees:** $0.02 to $0.15 per 1,000 characters transmitted. A typical EDI 850 purchase order runs 2 to 5 KCH, so you're paying $0.04 to $0.75 per PO just for transport - **Envelope fees:** $0.05 to $0.50 per interchange envelope (ISA/IEA wrapper) - **Interconnect fees:** Additional charges when your trading partner uses a different VAN. These can range from $0.03 to $0.10 per KCH on top of your standard rate - **Translation fees:** $0.10 to $0.50 per document if the VAN handles format conversion - **Setup and onboarding fees:** $500 to $2,500 per trading partner for initial mapping and testing ### What This Looks Like in Practice A mid-size supplier processing 500 EDI documents per month through a VAN might pay: - Monthly base: $300 - Per-KCH charges (assuming 3 KCH average): $22.50 to $225 - Envelope fees: $25 to $250 - **Total: roughly $350 to $775/month** At higher volumes (5,000+ documents/month), those per-transaction fees add up fast. According to [GS1 US](https://www.gs1us.org/upcs-barcodes-prefixes/how-to-use-your-upc-barcodes/share-information-electronically), EDI adoption continues to grow across retail supply chains, which means transaction volumes (and VAN costs) tend to increase year over year. ## Major EDI VAN Providers Several established providers dominate the EDI VAN market. Here's a brief overview of the major players: **[SPS Commerce](/ordersync-vs/sps-commerce)** operates one of the largest EDI networks, connecting over 115,000 trading partners. They offer a full-service model where they handle mapping, testing, and ongoing compliance. Pricing is subscription-based rather than pure per-transaction. **OpenText (formerly GXS)** runs one of the oldest and largest B2B networks globally. They serve large enterprises and offer extensive integration capabilities beyond basic VAN services. Their Trading Grid platform handles millions of transactions daily. **IBM Sterling** provides VAN services through its Sterling B2B Collaboration Network. It's common among Fortune 500 companies and large retailers. The platform includes supply chain visibility tools alongside basic VAN functionality. **Kleinschmidt (now part of Cleo)** has long served mid-market companies with VAN and translation services. They're known for more hands-on support compared to the larger providers. **Data Masons (now part of Epicor)** targets companies running Microsoft Dynamics and similar ERPs, offering VAN connectivity tightly integrated with those platforms. For a deeper comparison of EDI platforms and providers, see our guide to [EDI providers compared](/blog/edi-providers-compared) and [best EDI software](/blog/best-edi-software). ## When You Need a VAN vs When You Don't Not every trading relationship requires a VAN. The right connection method depends on your partner count, transaction volume, and technical capabilities. ### Connection Method Comparison | Factor | VAN | AS2 (Direct) | SFTP | API | | --- | --- | --- | --- | --- | | **Setup complexity** | Low (VAN handles routing) | Medium (certificates, firewall config) | Low (standard file transfer) | Medium to High (custom development) | | **Per-transaction cost** | $0.05 to $0.75+ per doc | Near zero after setup | Near zero after setup | Near zero after setup | | **Monthly cost** | $300 to $1,000+ | $50 to $200 (server/hosting) | $50 to $150 | Varies by platform | | **Best for** | Many trading partners, low technical resources | High-volume pairs (e.g., Walmart) | Smaller partners, batch exchange | Modern partners, real-time needs | | **Retailer support** | Nearly universal | Walmart, Target, major retailers | Some mid-market retailers | Growing but limited for EDI | | **Data speed** | Minutes to hours (mailbox polling) | Near real-time | Batch (scheduled) | Real-time | | **Scalability** | Costs scale with volume | Flat cost regardless of volume | Flat cost regardless of volume | Flat cost regardless of volume | ### When a VAN Makes Sense **VAN best fit**: A VAN is the right choice when you trade with 20 or more partners who all require EDI but use different communication methods, because a single VAN connection replaces the overhead of managing each trading partner connection individually. **AS2 best fit**: Direct AS2 connections eliminate per-document VAN fees entirely and are the better choice when your largest partners (Walmart, Target) support AS2 and your transaction volume is high enough that per-KCH fees add up to hundreds or thousands of dollars monthly. - You trade with **20+ partners** who all require EDI and use different communication methods - Your team has **limited technical resources** to manage direct connections - Your trading partners **mandate VAN connectivity** (some retailers specify this) - You need the VAN's **translation services** because your system can't generate native X12 ### When You Can Skip the VAN - Your largest partners support **AS2 direct connections** (Walmart, for example, strongly prefers AS2) - You have **fewer than 10 EDI trading partners** and can manage direct connections - You're already using a platform that handles **EDI transmission directly** without a VAN middleman - Your partners are moving toward **API-based exchange**, which doesn't need VAN infrastructure at all For more on how APIs compare to traditional EDI, read our [EDI vs API](/blog/edi-vs-api) breakdown. ## Common VAN Problems VANs solved a legitimate infrastructure problem decades ago. But the model has drawbacks that frustrate many suppliers today. ### Fees That Escalate with Growth The per-transaction pricing model means your costs grow in lockstep with your order volume. Land a new retail account that sends 1,000 POs a month? Your VAN bill jumps accordingly. With direct connections (AS2, SFTP), you pay roughly the same whether you process 100 or 10,000 documents. ### Vendor Lock-In Migrating away from a VAN is painful. Your trading partner connections, mailbox configurations, and document maps are all tied to that provider. Switching typically means re-testing with every trading partner, a process that can take months. ### Slow Onboarding Adding a new trading partner through a VAN often takes 4 to 8 weeks. The VAN needs to set up mapping, coordinate with the partner's VAN (if different), run test transactions, and validate compliance. Direct connections or API integrations can sometimes be stood up in days. ### Markup on Simple Transactions A 997 functional acknowledgment is a tiny document, often under 200 characters. But many VANs still charge per-envelope or per-KCH fees on these, effectively marking up a trivial data exchange. When you send thousands of acknowledgments per month, that markup becomes significant. ### Opacity in Billing VAN invoices can be difficult to reconcile. Between KCH charges, envelope fees, interconnect surcharges, and overage penalties, it's not always clear what you're paying for or why your bill increased 30% in a given month. If you're evaluating whether to stick with your current VAN or explore alternatives, our [EDI implementation guide](/blog/edi-implementation-guide) walks through the full decision process. For small teams especially, our guide on [EDI for small businesses](/blog/edi-for-small-business) covers cost-effective approaches that don't require heavy VAN investment. ## Modern Alternatives to Traditional VANs The VAN model was essential when point-to-point connections were the only alternative. Today, several options reduce or eliminate VAN dependency: - **AS2 direct connections** let you exchange EDI documents peer-to-peer with encryption and delivery receipts built in. No middleman, no per-transaction fees. - **SFTP-based exchange** works well for partners who don't need real-time delivery. You upload files to a shared server on a schedule. - **Cloud EDI platforms** like OrderSync handle EDI transmission, translation, and [ERP integration](/erp-integration) without routing through a traditional VAN. Documents go directly between you and your trading partner. - **API-based integrations** bypass EDI entirely for partners that support them, exchanging structured data in real-time without X12 formatting or VAN infrastructure. The right approach depends on who you're trading with and what they require. Many businesses end up with a hybrid: AS2 for high-volume retail partners, a VAN for the long tail of smaller partners, and APIs for modern platforms. ## Frequently Asked Questions ### What does VAN stand for in EDI? VAN stands for **Value Added Network**. It's a private network that routes EDI documents between trading partners, adding services like format translation, delivery tracking, and compliance validation on top of basic transport. ### How much does an EDI VAN cost per month? Most EDI VANs charge $300 to $1,000+ per month depending on your transaction volume and number of trading partners. This includes a monthly base fee ($150 to $500) plus per-document and per-KCH charges that vary with usage. High-volume senders can pay significantly more. ### Can I do EDI without a VAN? Yes. Many companies exchange EDI documents using AS2 direct connections, SFTP, or cloud-based EDI platforms that don't require a VAN. Major retailers like Walmart actively support AS2 connections. The key factor is whether your trading partners require VAN connectivity or accept alternative transport methods. ### What is the difference between a VAN and AS2? A VAN is a managed intermediary that stores and forwards your EDI documents. AS2 is a direct, point-to-point protocol that sends documents straight to your trading partner with encryption and signed receipts. AS2 has no per-transaction fees but requires more technical setup. VANs are simpler to manage but charge per document. ### Are EDI VANs becoming obsolete? Not yet, but their role is shrinking. According to [Gartner](https://www.gartner.com/en/supply-chain/topics/supply-chain-management), B2B integration is shifting toward API-first and cloud-based models. VANs still serve companies with large trading partner networks and limited IT resources, but the trend is clearly moving toward direct connections and modern integration platforms. For many mid-market suppliers, a cloud EDI platform eliminates the need for a traditional VAN entirely.