Start with the bill, not the protocol. AS2, SFTP and a VAN can all move the same purchase order from your system to your trading partner's system. What differs is where the money comes out, how much comes out, and who pays when something breaks. This piece skips the protocol theory and works through the money, line by line, so you can decide with numbers in front of you.

Where the money actually goes: the four bills inside AS2

Plenty of teams assume a direct connection is free because nobody charges per message. That is half true. AS2 carries no per-character toll, which removes the VAN usage bill, but it leaves four other bills on the table.

The first is software or a managed service. Published industry material puts commercial AS2 platforms at $10,000 to more than $100,000 a year, priced by partner count and message volume. Open-source options cost nothing for the software itself, yet setup, maintenance and troubleshooting still consume staff hours, and staff hours are a cost even when no invoice shows them.

The second is certificates. AS2 uses certificates for encryption and signing, and certificates expire on a schedule. Published material puts renewal at $100 to $300 per certificate per year. A certificate that lapses for one day stops the channel for one day, and orders, ship notices and invoices all wait at the door.

The third is labor. Every new partner needs its own configuration, testing and joint debugging, and published material puts that onboarding cost at $500 to $2,000 per partner. With 10 partners, labor plus certificates commonly runs $5,000 to $15,000 a year. That figure appears on no vendor quote, and it is the most honest number on the page.

The fourth is the cost of failure. An expired certificate, a partner key rotation nobody told you about, a receipt that fails verification, and someone has to get up in the middle of the night to fix it. Without a named owner for the channel, that cost arrives all at once, as downtime.

What an AS2 receipt is really worth

The most valuable part of the protocol is not the encryption. It is the receipt. When you send a document, the partner's system returns a signed Message Disposition Notification, an MDN, proving the message arrived and was not altered. Without that receipt, a lost document turns into an argument: you say you sent it, the partner says it never arrived, and neither side can prove anything.

Walmart requires suppliers to use AS2 for all EDI traffic, and other large retailers such as Target and Home Depot require or prefer it. That is the published industry position. When a partner mandates the channel, the choice stops being a choice and becomes an entry ticket.

The receipt earns its keep when chargebacks appear. Illustrative example: a 3PL sent 400 advance ship notices (EDI 856) to a retailer in November 2025. After a peak-season system upgrade on the retailer's side, 30 of them went unread, and the retailer applied a $200 short-shipment chargeback per document, $6,000 in total. Reconciling document by document against the signed AS2 receipts proved all 30 had been delivered and acknowledged, and the full $6,000 was reversed. A receipt generates no revenue. It generates evidence that prevents a loss.

Here is the counterintuitive part: the most expensive AS2 line item is never the software license. It is the night a certificate expires. Certificates typically run one to two years, and someone should be watching the 30-day, 60-day and 90-day marks. In many companies the certificate was requested by a colleague who has since left, the reminders go to an inbox nobody reads, and the channel dies on the last day of the quarter, with losses measured by the hour.

SFTP is cheap, and the cheapness is honest

SFTP has the most transparent bill of the three. Published material prices a managed SFTP endpoint at about $0.30 per hour, roughly $216 a month, plus $0.04 per gigabyte transferred. A commercial SFTP server bought outright runs $500 to $5,000 as a one-time license. There is no per-character charge and no mailbox fee, so doubling the partner count barely moves the bill.

The price shows up somewhere else: SFTP has no built-in receipt mechanism. You drop a file on the server, and whether the partner picked it up, read it, or hit an error is something you have to monitor and reconcile yourself. If the partner rotates a host key without telling you, the transfer keeps failing silently.

SFTP fits a narrow shape: a fixed set of partners, steady volume, and someone on each side watching the transfer logs. Illustrative example: a small supplier sending 20,000 documents a year to three partners can run entirely on SFTP for under $3,000 a year, cheaper than any VAN quote it will receive. Grow that to 12 partners and the monitoring and reconciliation workload roughly triples, and every dollar saved on the channel goes straight back into labor. That is the ceiling on SFTP.

Why the VAN invoice is always higher than the quote

A VAN sells peace of mind: one mailbox serves every partner, and the provider handles protocol conversion, routing and partner onboarding. The invoice looks bad because of how it is metered.

Legacy VANs bill per kilo-character. Published material puts the rate at $0.05 to $0.50 per kilo-character, and a detailed 856 ship notice runs 5 to 10 kilo-characters, so one document costs $0.25 to $5.00. Per-document pricing runs $0.30 to $3.00 per document, and the mailbox alone costs $500 to $2,000 a month. The more detailed the document and the more line items it carries, the higher the bill. Business improves, and the bill climbs with it.

Provider pricing structures split two ways. SPS Commerce publishes no price list; its fiscal 2025 annual filing implies average revenue of about $14,350 per recurring customer. TrueCommerce is listed in public comparison material at around $20 a month to start, with final pricing quoted by partner count and volume, so treat any figure as subject to the provider's latest quote. The shared truth is that the starting price is never the total price. The total depends on partner count, document volume and add-on fees.

A VAN fits a clear profile: many partners, no dedicated EDI staff, and no appetite for managing certificates and servers. You pay to stop worrying. The counterintuitive part is that the billing structure matters more than the headline number. A usage-metered VAN suits a company with stable volume, because a volume spike lifts the bill with it. A flat per-partner monthly model suits a company with seasonal swings, because peak-season documents cost nothing extra.

Cost item Direct AS2 Direct SFTP Managed VAN
Software and certificates $100–$300 per certificate per year; commercial platforms $10,000–$100,000+ per year $500–$5,000 one-time, or about $216 per month hosted Included in the subscription
Annual subscription No fixed annual fee No fixed annual fee Mailbox $500–$2,000 per month
Usage charges None $0.04 per GB $0.05–$0.50 per kilo-character, or $0.30–$3.00 per document
Labor and operations $500–$2,000 onboarding per partner; $5,000–$15,000 a year for 10 partners Monitoring and reconciliation grow with partner count Close to zero
Total (illustrative example: 10 partners, 120,000 documents a year) $8,000–$18,000 $3,000–$6,000 $12,000–$30,000

Before you sign anything, calculate three numbers: partner count multiplied by onboarding cost per partner, annual document volume multiplied by cost per document, and dedicated staff hours multiplied by the hourly cost. Add the three together and pick the lowest total. With three or fewer partners and no mandated channel, use SFTP. With a mandate from a retailer such as Walmart, use AS2. With more than 10 partners and no dedicated staff, use a VAN or a managed AS2 service. Picking the wrong channel is fixable, but remapping and retesting is the real sunk cost, so price the switch before you price the channel.

By Lao Zhou, Logistics Cost Analyst