How Does an EDI VAN Work? Mailboxes, AS2, and Trading Partner Pricing

By
BOLD VAN Marketing
April 16, 2026
5 min read
Share this post

Quick Answer

An EDI VAN (Value-Added Network) is a centralized hub that routes electronic business documents between trading partners. Instead of connecting directly to each partner, companies send and receive EDI transactions through a shared VAN mailbox that handles protocols, validation, security, and delivery tracking. Key things to know:

  • VANs eliminate the need for direct point-to-point connections with every trading partner
  • Costs range from a few hundred to several thousand dollars monthly depending on pricing model
  • AS2 provides secure, receipt-confirmed delivery; FTP handles batch transfers; HTTPS enables web-based integration
  • Per-trading-partner fees compound as you add retailers, 3PLs, and marketplaces
  • Companies often reduce EDI spend by 30–80% when switching from layered pricing to simplified models

Understanding how an EDI VAN works — especially how mailboxes, protocols, and trading-partner pricing affect cost — gives you control over your EDI spend. This guide breaks down the mechanics of EDI VANs through the lens of cost-conscious, risk-averse finance and operations teams.

How an EDI VAN Works: Step-by-Step

Every EDI transaction follows a predictable flow:

  1. A business system generates an EDI document such as an 850 purchase order
  2. The document is delivered to the company's VAN mailbox
  3. The VAN validates, secures, and routes the document to the trading partner
  4. The trading partner retrieves the document using their preferred protocol
  5. A confirmation — such as a 997 functional acknowledgment — verifies successful delivery

What an EDI VAN actually does

An EDI VAN acts as the communication layer between trading partners. Core functions include routing EDI documents between trading partners, managing secure protocols such as AS2, FTP, and HTTPS, validating and formatting EDI data in standards like X12 and EDIFACT, providing mailbox storage for sending and receiving documents, archiving transactions for audit and compliance, and monitoring delivery while flagging transmission errors.

These functions allow companies to scale EDI operations without managing individual connections for each trading partner.

Real-world example: how a purchase order moves through an EDI VAN

  1. Retailer generates an EDI 850 purchase order in their system
  2. Document is transmitted to your VAN mailbox via AS2
  3. Your ERP system retrieves and processes the order
  4. Your system sends a 997 functional acknowledgment confirming receipt
  5. The VAN archives the transaction for compliance

Because the VAN manages routing and protocol differences, you maintain one connection instead of separate integrations with every trading partner.

EDI Mailboxes Explained

The VAN mailbox is the central hub where all EDI documents are sent, received, and stored. Every transaction flows through this single touchpoint.

How mailboxes work

  1. You send an EDI document to your mailbox using a protocol that suits your tech stack: AS2, FTP, HTTPS, or others
  2. The EDI VAN processes the document by validating, translating if needed, and routing it to your partner's mailbox
  3. Your partner retrieves the document on their end, often using a different EDI system or protocol
  4. The process repeats for incoming documents, creating a traceable, auditable, and secure record of all activity

Mailbox pricing models

Traditional VANs often charge monthly mailbox fees per company, separate mailboxes per trading partner, separate mailboxes per connection type, and storage or maintenance fees. As partner counts grow, mailbox charges can quietly increase recurring costs — even if document volume stays steady.

EDI Protocols: AS2, FTP, and HTTPS

EDI VANs support multiple protocols so trading partners can communicate without changing their systems.

Protocol Best For Key Features Typical Use Case
AS2 Retail, supply chain partners Encryption, delivery receipts, real-time Walmart, Target, major retailers
FTP/FTPS High-volume batch transfers Simple, reliable, scheduled transfers Daily inventory updates, bulk orders
HTTPS Cloud-based, modern systems API integration, web-based SaaS ERPs, e-commerce platforms

Document standards supported

Modern VANs support all major formats without upcharges or special setup fees: X12 (the North American standard covering 850, 810, 856, 997, and more), EDIFACT (the international standard), ODETTE (automotive industry), and custom XML/JSON for modern integration formats.

Trading-Partner Pricing: The Hidden Cost Driver

Many traditional VANs charge in layers: a base monthly platform fee, a mailbox fee, a per-document or data fee, and a recurring charge per trading partner. That last component is where long-term cost creep most often begins. Per-partner pricing feels manageable initially — 10 partners at a fixed rate seems predictable. But as organizations grow and onboard new retailers, 3PLs, marketplaces, or transportation providers, those fees compound.

Per-partner models create three specific challenges. First, growth becomes a cost event — adding a new retailer or logistics partner increases recurring expense immediately, even before transaction volume ramps up. Second, budgeting gets complicated when divisions manage separate partner networks. Third, hidden complexity fees can appear when providers differentiate pricing based on partner complexity, document types, or required protocols.

What Does an EDI VAN Cost?

Primary cost drivers

Pricing Model Monthly Cost Range Best For Watch Out For
Per-document $200–$5,000+ Low, stable volume Seasonal spikes, growth penalties
Per-partner $500–$3,000+ Fixed partner count Expansion costs, division complexity
Character-based $300–$2,000 High document volume Rounding policies, large documents
Flat-rate bundles $500–$2,500 Predictable budgets Volume caps, overage fees

Beyond transmission, some providers charge for initial onboarding ($500–$5,000), trading partner setup ($100–$500 per partner), mapping updates ($200–$1,000 per change), certificate renewals ($100–$300 annually), and urgent change requests ($200–$500 per request). These fees can influence total cost of ownership more than the base monthly rate.

What to review in your current VAN bill

When evaluating cost, look specifically for what triggers increases — volume, partners, data size, or all three — whether document sizes are rounded, whether mailbox counts are expanding, whether setup and change fees are recurring, and whether there are hidden partner complexity charges.

When to Consider Migration

Consider switching VAN providers when monthly costs have increased 20% or more year-over-year without volume increases, per-partner fees exceed $100 monthly, setup and change fees consume more than 15% of your annual EDI budget, contract lock-ins prevent switching despite better options available, or support response times exceed 24 hours for critical issues.

EDI veterans know what happens when a VAN can't support required protocols — migration turns into a multi-week fire drill. With broad protocol support including AS2, X12, FTP, HTTPS, ODETTE, and EDIFACT, and no added cost for special trading partner connections, those headaches disappear.

How Trading-Partner Pricing Affects Real Businesses

Manufacturers and distributors frequently reduce EDI spend by 30–80% when moving from layered per-document and mailbox models to simplified pricing structures.

Torani, a global beverage syrup manufacturer with over 100 flavors sold worldwide, achieved a 54% reduction in EDI costs while maintaining zero service downtime during migration. With BOLD VAN's trading partner pricing model, EDI transformed from a significant monthly expense into a predictable operational cost.

Spanx reduced monthly EDI costs by 83% after switching from per-kilocharacter billing to trading partner pricing. The company also eliminated fees for accessing archived EDI data and experienced zero business interruptions during migration.

Endust, a furniture care product manufacturer with distribution through Walmart, Target, and Home Depot, cut monthly EDI expenses by 50%. The company gained instant visibility into EDI operations and 12 months of free archived document access, with no service delays or outages during transition.

Actionable Steps for Your EDI Roadmap

  • Audit every line of your EDI bill — especially mailbox, message, and partner fees. Challenge hidden costs.
  • Ask about real migration support: the right partner provides white-glove onboarding without forcing weekend cutovers or manual partner changes.
  • Demand full access and transparency: search, access, export, and archiving capabilities should be standard, never a premium feature.
  • Protect yourself with fair contracts: look for month-to-month flexibility and a meaningful trial period.

Ready to see what simplified, transparent EDI pricing looks like for your operation? Upload your current VAN bill for a guaranteed price beat, or start with a free three-month trial — no hidden fees, no mailbox surprises.

Schedule a Demo

Frequently Asked Questions

What is an EDI VAN?

An EDI VAN (Value-Added Network) is a service that routes electronic business documents between trading partners. It acts as a centralized hub, managing protocols, security, validation, and delivery tracking so companies don't need direct connections to each partner.

How much does an EDI VAN cost?

EDI VAN costs typically range from a few hundred to several thousand dollars monthly. Pricing depends on the model used: per-document ($0.05–$0.50 each), per-trading-partner ($25–$200 monthly per partner), character-based ($100–$2,000 monthly), or flat-rate bundles ($500–$2,500 monthly).

What is the difference between AS2 and FTP for EDI?

AS2 provides secure, encrypted transmission with delivery receipts and is preferred by major retailers like Walmart and Target. FTP is simpler and handles batch file transfers, commonly used for high-volume scheduled transmissions. AS2 is real-time and receipt-confirmed; FTP is batch-oriented and scheduled.

Why do EDI VANs charge per trading partner?

Per-trading-partner pricing historically reflected the setup, maintenance, and routing complexity for each connection. However, modern VAN architectures have reduced this complexity, leading many providers to offer flat-rate or unlimited-partner pricing tiers instead.

How long does EDI VAN migration take?

With proper planning and support, EDI VAN migration typically takes two to six weeks. The timeline depends on trading partner count, document complexity, and whether migrations happen in phases or all at once. White-glove migration services can reduce this to under two weeks.

Can I use multiple protocols with one VAN?

Yes. Modern VANs support multiple protocols simultaneously, allowing different trading partners to connect using their preferred method — AS2, FTP, HTTPS, and others — without requiring you to maintain separate systems.

What EDI document types do VANs support?

VANs typically support all standard EDI document types including 850 (purchase order), 810 (invoice), 856 (advance ship notice), 997 (functional acknowledgment), 855 (purchase order acknowledgment), 860 (purchase order change), and hundreds of other X12, EDIFACT, and custom formats.


Glossary of Key EDI Terms

AS2 (Applicability Statement 2)
Secure protocol for transmitting EDI documents with encryption and delivery receipts
EDI (Electronic Data Interchange)
Structured electronic exchange of business documents between companies
850
EDI transaction set for purchase orders
856
EDI transaction set for advance ship notice (ASN)
810
EDI transaction set for invoices
997
EDI transaction set for functional acknowledgment (receipt confirmation)
X12
North American EDI standard maintained by ANSI
EDIFACT
International EDI standard used primarily outside North America
VAN Mailbox
Storage location where EDI documents are sent, received, and archived
Trading Partner
Business entity you exchange EDI documents with — retailer, supplier, 3PL, and so on
BOLD VAN Marketing
Content Manager

Latest articles

Solutions
April 9, 2026

Do You Need a VAN for EDI? When AS2 Is Enough and When It Isn’t

Direct AS2 suits few EDI partners; for growing networks, a VAN or hybrid solution cuts costs, enhances compliance, and streamlines operations.

Compliance
March 31, 2026

FSMA 204 Compliance Checklist: 90-Day Action Plan Before the July 2028 Deadline

Complete FSMA 204 compliance checklist for food companies. Download our 90-day action plan to prepare for the July 2028 deadline with step-by-step tasks, timelines and team responsibilities.

Solutions
March 23, 2026

Why Manual Order Processing Costs More Than You Think: Calculate Your Real Annual Spend (and Save Instantly)

Estimate what non-EDI orders are really costing your business—from chargebacks to labor. Use our calculator to uncover hidden annual costs.

Achieve more from your EDI VAN provider.