On this page
- How it works
- Store-and-forward model
- Inter-VAN interconnects
- Multi-standard, multi-protocol support
- VAN topologies
- Standard retail EDI document flow via VAN
- Retailer mandates and approved VAN lists
- Major VAN providers
- Consolidation history
- Pricing
- Core billing unit: kilocharacter (KC)
- Additional fees (legacy VAN billing)
- VAN vs. direct connection alternatives
- AS2 (direct internet EDI)
- Cloud/API-native EDI
- VAN decline vs. continued relevance
- AI integration (2025–2026)
- Key terms
- Next frontier (dangling links from this page)
Value Added Network (VAN)
Value Added Network (VAN)
A third-party managed network service that routes EDI (Electronic Data Interchange) transactions between trading partners, acting as a secure intermediary. Described by multiple sources as functioning like "a post office" or "virtual mailbox" — each business connects once to the VAN and reaches all pre-connected trading partners, regardless of the partner's preferred protocol or EDI standard. The VAN handles protocol translation, message routing, encryption, error notifications, delivery confirmation, and audit trails so individual trading partners do not need to manage direct connections with every counterparty. (Cleo, 2026; BOLD VAN, 2026-07-03; Commport, updated 2025-05-27)
VANs were first deployed in the mid-1970s. They underpin the majority of B2B retail document exchange in North America and remain in active use across retail, manufacturing, automotive, logistics, healthcare, and government. (OpenText, 2021-02-05; IBM Community, 2026-01-22)
How it works
Store-and-forward model
A VAN uses a store-and-forward messaging architecture rather than real-time point-to-point transmission. The sender deposits an EDI (Electronic Data Interchange)|EDI message into their VAN mailbox; the VAN routes it to the recipient's mailbox; the recipient polls or receives a push notification and retrieves the message. This differs from AS2 (direct internet-based EDI), which transmits synchronously in real time. (Cleo, 2026; EDI2XML, updated 2025-10-16)
Inter-VAN interconnects
VAN providers maintain bilateral interconnect agreements with competing VANs, enabling seamless routing across networks. A supplier on SPS Commerce and a retailer on OpenText Business Network can exchange documents without special configuration — the inter-VAN routing is handled transparently. SPS Commerce explicitly lists interconnects with OpenText, IBM Sterling, and Loren Data Systems among others. (SPS Commerce, 2026-05-18; BOLD VAN, 2026-07-03)
Interconnect fees apply when routing crosses network boundaries (see Pricing below).
Multi-standard, multi-protocol support
Modern VANs support multiple EDI standards simultaneously — ANSI X12 (North America), EDIFACT and EANCOM (Europe/international), GS1 XML, TRADACOMS (UK legacy) — as well as non-EDI formats (JSON, flat files, proprietary XML) and transport protocols (AS2, SFTP, HTTPS, API). Protocol translation is handled within the VAN: a supplier transmitting EDIFACT via SFTP can reach a retailer that expects ANSI X12 via AS2 without either party changing their setup. (Commport, updated 2025-05-27; SPS Commerce, 2026-05-18)
VAN topologies
Three configurations identified in sources (Cleo, 2026; Orderful, 2025-01-23):
| Topology | Structure | Typical use case |
|---|---|---|
| One-to-one | Custom bilateral connection | Two businesses with stable, long-term high-volume relationship |
| Many-to-many | Shared hub, any member to any member | Manufacturers, wholesalers, and retailers on same network |
| One-to-many | Hub-and-spoke | Retailers as hub for large supplier bases; suppliers connect to the hub |
The one-to-many (hub-and-spoke) model is the dominant retailer pattern: the retailer anchors the network and requires suppliers to connect via a VAN the retailer has approved or endorsed.
Standard retail EDI document flow via VAN
The canonical B2B retail transaction sequence in ANSI X12 (AIMS360, 2025-08-29; 3PLGuys, 2026):
| Transaction Set | Name | Direction | Typical Size |
|---|---|---|---|
| EDI 850 | Purchase Order | Retailer → Supplier | 2–5 KC (as-of 2025-10) |
| EDI 855 | PO Acknowledgment | Supplier → Retailer | ~1–2 KC |
| EDI 856 | Advance Ship Notice (ASN) | Supplier → Retailer | 5–15 KC (as-of 2025-10) |
| EDI 810 | Invoice | Supplier → Retailer | 1–3 KC (as-of 2025-10) |
| EDI 997 | Functional Acknowledgment | Both directions | <1 KC |
1 KC = 1,024 characters. KC-based pricing is the primary VAN billing unit (see Pricing below).
Late or missing ASNs (856s) trigger chargeback penalties from major retailers including Walmart, Target, Amazon Vendor Central, and Kroger. (3PLGuys, 2026; Nexus VAN, 2025-10-07)
Retailer mandates and approved VAN lists
Major US retailers require EDI-capable suppliers. Kroger maintains a published list of approved VAN providers for supplier onboarding (as-of 2026-07-28): eZcom Software, Edict, Easylink Services International, Softshare, TrueCommerce, Infocon Systems, and SPS Commerce. The page notes this is not a complete list and Kroger does not endorse these providers. [1]
Whether retailers mandate VAN specifically vs. AS2: BOLD VAN (2026-07-03) states that Walmart, Target, Costco, and Amazon "either require or strongly prefer VAN connectivity." A separate search result summary notes "retailers like Walmart have famously mandated AS2 connections from their suppliers." These are not mutually exclusive — a VAN can deliver via AS2 to a retailer endpoint — but the framing differs across vendor sources. No independent, non-vendor primary document from Walmart, Target, or Amazon confirming their specific VAN/AS2 requirements was retrieved. (BOLD VAN, 2026-07-03; Commport search summary, 2026-07-28)
Major VAN providers
Provider landscape (as-of 2026; drawn from multiple sources including Cleo search summaries and SPS Commerce primary pages):
| Provider | Notable claim | Status |
|---|---|---|
| SPS Commerce | 300,000+ trading relationships; 750M+ transactions/year; $751.5M FY2025 revenue (as-of 2026); 50,000+ customers; all NRF 2025 top-10 retailers use SPS | Publicly traded (NASDAQ: SPSC); ongoing acquisition program |
| OpenText Business Network | 1M+ partners across 175 countries (as-of 2025-08-07); IDC MarketScape Leader | Enterprise-focused; acquired GXS for $1.06B (2014), Liaison, EasyLink, Covisint |
| IBM Sterling B2B Integration SaaS | Now SaaS replatform of Sterling Commerce (acquired by IBM June 2010) | Enterprise segment |
| TrueCommerce | 30+ years; network pre-connected to Amazon, Walmart, Target, Costco, Home Depot, Wayfair; strong ERP integration focus | Private; growth through acquisition (DiCentral and others) |
| Descartes Systems | Named among top-5 by revenue concentration | Public (Nasdaq/TSX) |
| Axway | Named among top-5 by revenue concentration | Public (Euronext Paris) |
| Commport Communications | 60M+ transactions/month; 99.99% uptime claimed (as-of 2025-05-27) | Canadian market focus |
| BOLD VAN | 99.998% uptime SLA claimed (as-of 2026-07-03) | Cloud-native VAN |
| Nexus VAN | Modern all-inclusive pricing: $99–$999/month (as-of 2025-10-07) | Challenger/cloud model |
[!unverified] Market revenue concentration: "over 75% of EDI industry revenue concentrated in five companies: OpenText, SPS Commerce, Descartes, IBM Sterling, and Axway." Source: search result summary drawing on Cleo blog; original publication date unclear. Treat as directional only — no independent market-share study was directly retrieved.
Consolidation history
- December 2009: GXS + Inovis merger — major consolidation reducing the number of independent Tier 1 VANs
- June 2010: IBM acquired Sterling Commerce (was #2 EDI VAN provider at acquisition)
- 2014: OpenText acquired GXS for $1.06 billion — making OpenText the largest VAN by trading partner count
- January 2025: SPS Commerce acquired Carbon6 for $210 million (Amazon seller analytics tools — adjacent to VAN, not a VAN)
(Cleo blog search summaries, 2026; OpenText blog, 2025-08-07/2026-07-16)
Pricing
Core billing unit: kilocharacter (KC)
Standard VAN pricing is per-kilocharacter (KC), where 1 KC = 1,024 characters. Rates vary by volume tier. (Nexus VAN, 2025-10-07; BOLD VAN, 2026-07-03)
- Base KC rate: $0.10–$0.30/KC (as-of 2025-10), with tiered volume discounts
- Inter-VAN interconnect surcharge: $0.03–$0.10/KCH (as-of search result, 2026-07-28) when routing across network boundaries
Additional fees (legacy VAN billing)
Nexus VAN (Oct 2025/Apr 2026) classifies the following as fees with "no legitimate operational justification in 2026":
| Fee type | Typical range | Nexus VAN classification |
|---|---|---|
| Mailbox/ID fees | $50–$200/month per mailbox | Markup: 1,000–4,000× actual cloud storage cost |
| Setup/onboarding | $500–$5,000 per new connection | Automated in modern VANs; actual cost ~$50–$100 |
| Migration fees | $1,000–$10,000 | Unjustified with automated tooling |
| Per-message charges | $0.05–$0.50 per document | Often added on top of KC — double billing |
| Trading partner fees | $10–$50/month per partner | One-time 15-minute task |
| User seat fees | $25–$100/month per user | — |
| API access fees | $500–$2,000/month | — |
| Support fees | $200–$1,000/month | — |
The specific fee ranges above are from Nexus VAN (a cloud VAN with commercial interest in portraying legacy VAN pricing negatively); published October 2025/April 2026. Verify against a legacy VAN's current pricing documentation before using as benchmarks.
True cost impact (Nexus VAN estimates, as-of 2025-10): For a small business (10 partners, 500 docs/month), hidden fees add ~$7,700/year on top of the base rate. For a medium business (25 partners, 5,000 docs/month), hidden fees add ~$40,700/year — potentially 3–5× the advertised annual rate, turning a $12,000/year quote into $50,000+.
Contract risk flags: 2–3 year commitments with auto-renewal; early termination penalties of $5,000–$25,000; automatic 5–10% annual price increases; 90–180 day cancellation notice required. (Nexus VAN, 2025-10-07)
Modern cloud VAN pricing: $99–$999/month flat (unlimited mailboxes, unlimited partners, unlimited users, $0 setup, $0 migration). (Nexus VAN, 2025-10-07)
VAN vs. direct connection alternatives
AS2 (direct internet EDI)
AS2 transmits EDI documents directly between trading partners over the internet using HTTPS with digital signatures and encryption. It is the primary alternative to a VAN for high-volume bilateral relationships. (EDI2XML, updated 2025-10-16; BOLD VAN, 2026-07-03)
| Factor | VAN | Direct AS2 |
|---|---|---|
| IT overhead | One connection to VAN; VAN manages partner routing | Certificate management + server maintenance + monitoring per partner |
| Cost at high volume | Higher per-transaction; predictable | Lower per-transaction; IT overhead unpredictable |
| Scalability | Scales automatically as partner count grows | Each new partner = new IT project |
| Uptime responsibility | VAN provider (e.g. 99.998% SLA) | In-house IT |
| Protocol translation | Handled by VAN | Must match partner's protocol exactly |
| When to choose | 5+ trading partners; no dedicated IT; major retailer compliance required; regulated industry | 1–2 high-volume partners; dedicated IT available |
Most manufacturers use a hybrid model: VAN for the majority of trading partners, direct AS2 for one or two very high-volume relationships where per-transaction cost savings exceed IT management overhead. (BOLD VAN, 2026-07-03; EDI2XML, updated 2025-10-16)
Cloud/API-native EDI
Newer platforms (Orderful, Stedi, Cleo, Boomi, MuleSoft) position themselves as alternatives or complements to VANs with flat pricing, real-time (not batch) processing, API-first architecture, and faster partner onboarding (days vs weeks). Stedi raised $70M Series B co-led by Stripe and Addition (August 2025), primarily healthcare-focused but active in retail B2B. (Orderful blog search summaries, 2026; A3Logics, 2026)
IBM Community (2026-01-22) positions the future as a "hybrid integration model" where EDI VANs, APIs, and SaaS apps coexist — "organizations need EDI for partner communication, APIs for internal data access, and SaaS apps for workflows."
VAN decline vs. continued relevance
Whether VANs are declining: EDI2XML (updated 2025-10-16) states that VAN use is in "constant decline" and that "most major players in the retail industry have switched to point-to-point communication using sFTP, HTTPS, AS2, or AS3." Commport (updated 2025-05-27), itself a VAN provider, states "the majority of EDI still occurs through VANs." IBM Community (2026-01-22), promoting IBM Sterling, argues VANs remain "more relevant than ever" in a cloud-and-API era. Cleo (2026), an iPaaS competitor to VANs, states "the use of EDI VAN services is declining." No independent, non-vendor market-share study was retrieved to adjudicate. All sources have a commercial stake in one framing or the other.
EDI overall continues to grow: the EDI/B2B integration market was valued at $36.52 billion in 2023, with a projected 12% CAGR through 2032. (as-of search result summary drawing on A3Logics, 2026-07-28 — original source not directly fetched; treat as directional)
EDI market size figures: A3Logics-derived summary reports $36.52B (2023) for the broader EDI/B2B integration market. A separate source reports $2.08B (2024) for the EDI software market specifically. These measure different things (services + transmission revenue vs. software-only) but are not reconciled in any directly retrieved source.
AI integration (2025–2026)
Major VAN providers are embedding AI into their platforms (as-of 2026):
- SPS Commerce MAX (launched Feb 2026, beta): Three AI components — MAX Chat (network-intelligence chatbot drawing on 300K trading connections and billions of transactions), MAX Monitor (continuous background transaction monitoring), MAX Connect (MCP-compatible integration layer). (SPS Commerce, 2026-05-18; Digital Commerce 360, 2026-02-10)
- TrueCommerce agentic AI (announced Apr 2026): "Truedi" support agent resolved 91% of issues autonomously in 2025, reducing total support cases by 12% (as-of 2025 full year). AI-Assisted Trading Partner Onboarding claims 50% faster setup vs. traditional VAN onboarding. Agentic AI Mapping auto-builds trading partner maps from specifications. (TrueCommerce press release, 2026-04-07)
- OpenText (updated Jul 2026): AI error flagging, workflow suggestions, auto-correction of data issues before they stall operations; a named retail case study reports transaction accuracy lifted from 55% to 98%. (OpenText blog, 2026-07-16)
Key terms
| Term | Meaning |
|---|---|
| KC (kilocharacter) | 1,024 characters; primary VAN billing unit |
| Mailbox | The VAN account identifier for a trading partner — sender deposits, recipient retrieves |
| Inter-VAN interconnect | Agreement between two VAN operators to route messages across each other's networks |
| Store-and-forward | Messaging model where VAN queues and delivers messages asynchronously (vs. AS2 real-time) |
| AS2 | Applicability Statement 2 — direct internet-based EDI protocol; primary VAN alternative |
| Chargeback (EDI context) | Financial penalty applied by retailer to supplier for non-compliant or late EDI documents (e.g. missing ASN) |
| VAN consolidation | Practice of reducing multiple VAN relationships to one provider; sold as a managed service by OpenText and others |
Next frontier (dangling links from this page)
- AS2 (Applicability Statement 2) — direct EDI protocol; primary VAN alternative; no standalone concept page
- EDIFACT — European dominant EDI standard; referenced throughout but no full concept page
- ANSI X12 — North American EDI standards body and format family; no standalone concept page
- GDSN (Global Data Synchronization Network) — GS1's product master data network; related infrastructure; no standalone page if not yet written
References
- Kroger EDI Portal, fetched 2026-07-28 — edi.kroger.com/EDIPortal/VansAndProviders.html