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

By
BOLD VAN Marketing
March 23, 2026
5 min read
Share this post

What Is an EDI VAN?

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 Takeaways

  • EDI VANs route documents between trading partners through centralized mailboxes, eliminating the need for direct connections
  • Typical costs range from a few hundred to several thousand dollars monthly, depending on pricing model and transaction volume
  • AS2 provides secure, receipt-confirmed delivery; FTP handles batch transfers; HTTPS enables web-based integration
  • Per-trading-partner pricing compounds as companies 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 teams.


How an EDI VAN Works: Step-by-Step Process

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 (X12, EDIFACT, etc.)
  • Providing mailbox storage for sending and receiving documents
  • Archiving transactions for audit and compliance
  • Monitoring delivery and 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

Here's what happens when a retailer sends a purchase order:

  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. 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

  • You send an EDI document (for example, an 850 purchase order) to your mailbox using a protocol that suits your tech stack: AS2, FTP, HTTPS, or others
  • The EDI VAN processes the document by validating, translating if needed, and routing it to your partner's mailbox
  • Your partner retrieves the document on their end, often using a different EDI system or protocol
  • 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
  • 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 Comparison

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

  • X12: North American standard (850, 810, 856, 997, etc.)
  • EDIFACT: International standard
  • ODETTE: Automotive industry
  • Custom XML/JSON: Modern integration formats

Modern VANs support all major formats without upcharges or special setup fees.

Trading-Partner Pricing: The Hidden Cost Driver

Many traditional VANs charge in layers:

  • Base monthly platform fee
  • Mailbox fee
  • Per-document or data fee
  • Recurring charge per trading partner

That last component is where long-term cost creep often begins. Per-partner pricing feels manageable initially — 10 partners at a fixed rate seems predictable. But as organizations grow, onboarding new retailers, 3PLs, marketplaces, or transportation providers, those fees compound.

For manufacturers and distributors with dozens or hundreds of partners, the cost structure shifts from predictable to restrictive. Each new integration becomes not just an operational task, but a budget conversation.

Why Trading-Partner Fees Add Up

Per-partner models create three challenges:

  1. Growth becomes a cost event: Adding a new retailer or logistics partner increases recurring expense immediately, even before transaction volume ramps up
  2. Budgeting gets complicated: If divisions manage separate partner networks, forecasting EDI spend becomes harder
  3. Hidden complexity fees appear: Some providers differentiate pricing based on partner "complexity," document types, or required protocols

Alternative Pricing Approaches

Modern EDI VAN providers have moved toward simplified structures:

  • Flat trading-partner tiers (unlimited partners up to certain volume)
  • Data-volume (character-based) billing
  • Bundled pricing without mailbox or protocol add-ons

These models align cost more directly with usage or scale, rather than charging separately for each relationship.

What Does an EDI VAN Cost?

EDI VAN costs typically range from a few hundred to several thousand dollars per month, depending on pricing model, transaction volume, and number of trading partners.

There isn't a single answer because EDI VAN pricing depends entirely on how the provider structures billing. Two companies with identical transaction volumes can pay dramatically different amounts based on their contract model.

Primary Cost Drivers

1. Per-Document Pricing

Some VANs charge per document sent or received (for example, $0.05-$0.50 per 850, 810, or 856).

Cost range: $200-$5,000+ monthly depending on volume

Works well for: Low, stable volume (under 1,000 documents monthly)

Becomes expensive when:

  • Order volume scales
  • Seasonal spikes occur
  • Retail promotions increase shipment frequency
  • E-commerce channels expand

Small per-document charges compound quickly at high transaction counts.

2. Mailbox Fees

Cost range: $50-$500 per mailbox monthly

Traditional VANs often charge monthly fees for mailboxes. Depending on the provider, you may see:

  • One mailbox per company
  • Separate mailboxes per trading partner
  • Separate mailboxes per connection type
  • Maintenance or storage fees

3. Trading-Partner Fees

Cost range: $25-$200 per partner monthly

Many VAN contracts include a recurring charge per trading partner. At small scale, this feels predictable. At larger scale, it becomes a structural cost driver.

If your organization:

  • Frequently onboards new retailers
  • Works with multiple 3PLs
  • Operates across divisions
  • Expands into new marketplaces

Per-partner fees can materially affect long-term ROI.

4. Data or Character-Based Pricing

Cost range: $100-$2,000 monthly for typical mid-market volume

Some modern VANs price based on the amount of data transmitted — often measured in characters or kilocharacters.

Instead of charging per document, billing reflects the actual size of data exchanged.

This can offer:

  • More precise alignment with usage
  • Greater predictability at high document counts
  • Scalability without penalizing document volume

However, understand whether document sizes are rounded up or billed strictly based on actual transmitted data. Rounding policies can meaningfully impact cost at scale.

5. Setup, Testing, and Change Fees

Beyond transmission itself, 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)
  • Urgent change requests ($200-$500 per request)

These are often contract-dependent and can influence total cost of ownership more than the base monthly fee.

VAN Pricing Models Compared

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

Why VAN Bills Often Feel Unpredictable

The complexity of EDI billing usually comes from stacking multiple pricing components together:

  • Per-document fees
  • Mailbox fees
  • Per-partner fees
  • Data volume fees
  • Support or change charges

When those layers interact, monthly invoices can fluctuate in ways that feel disconnected from operational reality. The issue is rarely technical — it's structural.

For a deeper breakdown of how these fees show up in real invoices, see our guide to EDI pricing and hidden VAN fees.

What to Review in Your Current VAN Bill

If you're 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
  • Hidden partner "complexity" charges

Protocol Support and Migration Considerations

EDI veterans know what happens when a VAN can't support required protocols. Migration turns into a multi-week fire drill and, worst of all, you're forced to make partner announcements that disrupt business and strain relationships.

With broad protocol support — AS2, X12, FTP, HTTPS, ODETTE, EDIFACT — and no added cost for special trading partner connections, those headaches disappear.

If you haven't yet, take a look at BOLD VAN's FAQ for a sense of how inbound and outbound protocols work together, and how data access is managed across large partner lists.

If you're evaluating switching providers, our EDI VAN migration guide outlines how companies transition without downtime or trading partner disruption.

When to Consider Migration

Consider switching VAN providers when:

  • Monthly costs have increased 20%+ year-over-year without volume increases
  • Per-partner fees exceed $100 monthly
  • Setup and change fees consume more than 15% of annual EDI budget
  • Contract lock-ins prevent switching despite better options
  • Support response times exceed 24 hours for critical issues

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.

BOLD VAN customers have achieved substantial savings by switching to transparent, predictable pricing models:

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. As a business operating across multiple international markets, Torani previously faced massive monthly EDI bills due to high data volume. With BOLD VAN's trading partner pricing model, EDI transformed from a significant expense into a reliable, predictable operational cost.

Spanx, the global shapewear brand available in retail stores across over 50 countries, 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. The savings enabled Spanx to reinvest in streamlining other internal operations.

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


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's the difference between AS2 and FTP?

AS2 provides secure, encrypted transmission with delivery receipts and is preferred by major retailers. 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 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 2-6 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, etc.) 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.


Actionable Steps for Your EDI Roadmap

  • Review your EDI bills: Audit every line, especially mailbox, message, and partner fees. Challenge hidden costs
  • Ask about real migration support: The right partner will provide white-glove onboarding without forcing you or your partners into weekend cutovers or manual changes
  • Demand access and transparency: Full search, access, export, and archiving capabilities should be table stakes — never a premium feature
  • Protect yourself with fair contracts: Look for month-to-month flexibility and a meaningful trial period to ensure the fit is right for your business

If you're reviewing your current VAN structure, compare how your provider charges for documents, mailboxes, partners, and data volume. Clarity around those drivers often reveals immediate opportunities for cost control.

Next Steps

Some modern VAN providers, including BOLD VAN, offer simplified pricing models and rapid migrations designed to eliminate the hidden fees and rigid contracts common in legacy VAN agreements.

You can schedule a free demo, upload your VAN bill for a guaranteed price beat, or start with a three-month free trial. No hidden fees, no mailbox surprises — just EDI made easy, with support from a team that puts you first.


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, etc.)

BOLD VAN Marketing
Content Manager

Latest articles

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.

Compliance
March 10, 2026

FSMA 204 Key Data Elements (KDEs): What Food Companies Must Track

Learn what FSMA 204 Key Data Elements (KDEs) are and how food companies must track traceability data during receiving, processing, and shipping events.

Achieve more from your EDI VAN provider.