AS2, FTP, and VAN Connections: A Practical Roadmap to Right-Sized EDI Connectivity
In this article
If your team is weighing the merits of AS2, FTP, or VAN for EDI, you want a choice that delivers the right protocol to every partner without rebuilding your infrastructure or overspending. The right decision comes down to centralizing data mapping while supporting AS2, FTP, SFTP, APIs, and VAN mailboxes—meeting each partner where they are without forcing your IT team or finance department into complexity and runaway costs. This guide explains how to select and combine these protocols smartly, adopt best practices for protocol management, and leverage BOLD VAN for predictable pricing and seamless migrations.
Making Protocol Choices That Fit Your Business
For CFOs, IT directors, and EDI coordinators at manufacturing and supply chain organizations, the protocol question usually surfaces when:
- A major retailer mandates AS2 and digital receipts on a tight deadline
- A legacy distributor only supports FTP/SFTP file drops
- Rising VAN costs and unpredictable bills force a review of the model
The key is to avoid “rip and replace” thinking. Rather than picking a single protocol, modern organizations map data once and use a platform like BOLD VAN that routes transactions using the channel and protocol preferred by each trading partner. This prevents redundant development and allows your business to onboard new partners with minimal rework.
The real decision is not choosing AS2 versus FTP or VAN—it is selecting an EDI solution that covers them all from a single integration, controls costs, and eliminates protocol lock-in or costly rebuilds every time a new partner enters your ecosystem.
Clear Definitions: AS2, FTP, and VAN
AS2
Applicability Statement 2 (AS2) is a secure transport protocol commonly required by large retailers and regulated industries. It supports encrypted, signed document transfer over HTTP/HTTPS and returns Message Disposition Notifications (MDNs) as formal receipts. AS2 is favored for transactions that need non-repudiation, traceability, and highly auditable delivery.
- Best for: Retailers or partners requiring acknowledgment receipts, digital signatures, and secure communication
- Operational impact: Requires certificate management and 24/7 monitoring for failed or time-sensitive transactions
- Cost pattern: Avoids per-character VAN fees, often involves fixed service or support fees
FTP/SFTP
File Transfer Protocol (FTP) and its secure variants (SFTP, FTPS) enable batch transfers between internal systems or with legacy trading partners. Plain FTP is not encrypted, while SFTP/FTPS add needed security but lack formal, auditable receipts like AS2.
- Best for: Internal system integrations, partners with batch file-based workflows, or where encryption suffices but formal acknowledgments are not required
- Operational impact: Simple, but lacks MDNs. Directory permissions, network firewalls, and job automation must be managed.
- Cost pattern: Minimal direct cost, but still subject to VAN fees if a mailbox is involved
VAN
A Value Added Network (VAN) acts as a secure, third-party communication hub between you and your trading partners. VANs often provide mailboxing, protocol translation, message routing, and compliance monitoring. Most modern VANs handle multiple protocols—including AS2, FTP, and SFTP—without requiring your team to manage those connections individually.
- Best for: Environments with many disparate trading partners, mixed protocol needs, or where scaling up is a priority
- Operational impact: Reduces day-to-day protocol management, but traditional VANs may introduce rigid fees and slow onboarding
- Cost pattern: Can include mailbox fees, per-document/character charges, and occasional protocol surcharges; modern approaches offer trading partner pricing or unlimited transaction plans
| Option | Ideal Scenarios | Risks/Pitfalls |
|---|---|---|
| AS2 | Retailers and partners needing digital receipts and regulatory compliance | Certificate management, technical complexity, monitoring load |
| FTP/SFTP | Legacy partners, batch file workflows, secure internal transfers | Lack of formal receipts/audit trail, security risks if FTP (not SFTP) |
| VAN | Scaling with many partners, protocol/translation needs | Opaque fees, vendor lock-in, delays in onboarding |
BOLD VAN recommends mapping your data once, keeping EDI logic inside your ERP or platform, and letting the VAN handle protocol translation and routing without per-protocol penalties.
A Step-by-Step Framework to Avoid Overbuilding
Step 1: Audit Actual Partner Requirements
- Document every trading partner's protocol (AS2, SFTP, FTP, VAN, or API)
- List documents by type and volume (POs, invoices, ASNs)
- Note any compliance or audit trail requirements
For most SMB manufacturers, this tally is manageable—major retailers often demand AS2, while smaller distributors and 3PLs may stick with FTP or SFTP.
Step 2: Default to AS2 When Mandated
- Adopt AS2 for any partner requiring MDNs or formal compliance traceability
- Give priority to top revenue customers and those whose EDI guidelines mandate AS2
- Elsewhere, use SFTP or VAN mailbox connections for simplicity
Step 3: Use FTP/SFTP When Batch-Only or Receipts are Unnecessary
- Batch orders, planned nightly or weekly exchanges, and low-risk relationships are good candidates
- Encryption provides security, but you do not get delivery receipts
Step 4: Rely on a VAN for Scale, Onboarding, and Mixed Protocols
- When onboarding numerous or global partners, or if internal resources are limited
- Protect your business from mounting complexity, especially for message retries and partner format validation
With BOLD VAN, your team can centralize EDI mapping and allow the VAN to convert and deliver messages via AS2, FTP, SFTP, or even API—eliminating the need to rebuild workflows as new connections arise.
Cost Structures, Traps, and When Each Option Fits
Typical EDI Cost Models
| Connection Type | What You Pay For | Potential Risks |
|---|---|---|
| AS2/FTP Direct | Software or managed service fees, IT labor, infrastructure | Underestimating internal support as connections scale, risk of dropped messages if not well monitored |
| Traditional VAN | Mailbox/setup fees, per-character or document billing, sometimes protocol surcharges | Cost growth with usage, opaque pricing, delayed onboarding for new protocols, long contract lock-in |
| Modern VAN (like BOLD VAN) | Predictable monthly subscription, unlimited transactions, no protocol surcharges | Vendor selection focus shifts to support, reliability, and migration—not protocol limits |
Many businesses find AS2 or secure FTP minimize per-transaction costs, but push more monitoring and troubleshooting onto internal teams. Conversely, VANs bundle protocol management and onboarding, but traditional providers can introduce unpredictable bills—unless you use a plan with unlimited or trading partner pricing. BOLD VAN publishes transparent pricing with unlimited transactions, no AS2 surcharges, and offers bill upload for a guaranteed price beat.
When a VAN Model Makes Sense
- You must onboard or connect with many partners quickly, especially after a merger or new channel launch
- Your internal IT or EDI resources are stretched thin or lack protocol expertise
- You want archival, monitoring, and compliance features without additional software modules
The key to controlling costs is demanding visible, transparent pricing with no per-protocol upcharges or mailbox fees. BOLD VAN addresses this by offering trading partner-based pricing, predictable subscriptions, and flexible protocol support.
How BOLD VAN Enables Flexible, Managed EDI Connections
Single Mapping, Multi-Protocol Execution
- Map EDI documents to your ERP once (NetSuite, SAP, Infor, Dynamics, and more)
- BOLD VAN translates and routes over AS2, FTP, SFTP, HTTP/HTTPS, or API as partners require
- No new builds for each protocol—just one core configuration, updated as your business grows
Transparent, Predictable Pricing
- No mailbox or setup fees
- Unlimited EDI transactions per plan—growth does not mean runaway bills
- No extra charges for AS2, certificates, or specific partner connections
Seamless, Fast Migrations
- Typical migrations complete in a day with zero downtime, as reported by Razor and Torani in BOLD VAN’s case studies
- You do not need to contact or re-configure existing trading partners—BOLD VAN manages all outreach and cutover
- Access 90 days of EDI data online for daily monitoring, with 7 years archived for compliance
Practical Impact for Manufacturers
- Major retailers can be connected via AS2, fully managed by BOLD VAN
- Distributors, 3PLs, or legacy partners stay on FTP/SFTP if preferred, without disrupting your ERP integration
- All monitoring happens in the BOLD Manager portal, streamlined for EDI coordinators and IT
In practice, this unified approach reduces risk, controls spend, and saves valuable IT hours otherwise wasted on chasing protocol-specific issues. If you want to dive deeper into multi-protocol EDI and integration, see AS2, FTP, or Web Services? Decoding EDI Communication Protocols for Fast, Secure Manufacturing Operations.
Frequently asked questions
Should I pick a single protocol for all my EDI partners?
No. Most manufacturers benefit from supporting multiple protocols simultaneously. The recommended approach is to map once to your internal system and let your EDI provider—such as BOLD VAN—handle delivery and translation for AS2, FTP/SFTP, or API at the protocol layer, without rebuilding every time requirements change.
When is AS2 absolutely required?
AS2 is necessary when your partner mandates MDNs, secure signatures, and non-repudiation—a common requirement for large retailers and regulated industries. Always check your trading partner’s EDI documentation.
Do businesses still use FTP for EDI?
Yes—many legacy and smaller partners still rely on FTP or SFTP for batch file movements. Plain FTP is not secure and is not recommended for external partners, but SFTP remains a common choice where formal receipts or real-time acknowledgments are not needed.
Is it really possible to switch to BOLD VAN without downtime or contacting all our trading partners?
BOLD VAN reports that migrations are virtually disruption-free, typically completing in one day once connectivity is ready. Customers such as Razor, Spanx, and Torani have made the switch without contacting partners or experiencing downtime, thanks to BOLD VAN’s managed onboarding process and migration support.
How is BOLD VAN pricing different from traditional VANs?
BOLD VAN offers transparent, predictable plans with no mailbox or protocol surcharges, unlimited transactions, and trading partner-based pricing. You can even upload your current VAN bill for a guaranteed price beat and see case studies with documented cost reductions of 50% or more.
