Your Supplier Won't Do EDI? Let Them Answer From Email

Every small supplier knows the letter. "As part of our ongoing digital transformation, all trading partners will be required to transact via EDI by Q4. Please contact our onboarding team to begin certification." To the buyer who sent it, it's process improvement. To the 15-person machine shop that received it, it's a demand to buy software, hire a consultant, and pay monthly fees — to keep a customer they already serve perfectly well over email.

So they stall. They ask for extensions. They quietly fail certification and keep faxing. And your team keeps re-keying their confirmations by hand while the EDI project's "supplier onboarding" milestone slips another quarter.

Here's the uncomfortable part: the supplier is being rational.

Why Small Suppliers Refuse: The Math Doesn't Work for Them

Traditional EDI was designed for enterprises trading with enterprises, and its cost structure shows it. Published EDI pricing guides commonly cite per-partner setup fees in the hundreds to low thousands of dollars, monthly VAN fees from tens to hundreds of dollars, and per-document charges on top — plus the mapping and testing work to certify against each trading partner's spec. Treat the exact figures as industry-reported ranges rather than a quote, but the shape of the cost is not in dispute: it's a fixed tax per customer relationship.

Now run that math from the machine shop's side. They have one customer demanding EDI. That customer sends them maybe a dozen POs a month. The setup fee, the monthly fees, the per-document charges, and the time to learn yet another system — all of it to automate a workflow that currently costs them one email reply. For a business that size, EDI for one customer isn't an investment. It's a fee for continuing to be your supplier.

The pressure flows downhill because it flows onto the buyer first. Retail and large-enterprise compliance programs commonly deduct a percentage of invoice value as chargebacks for EDI non-compliance — which is exactly why mid-market buyers who've felt that pain turn around and mandate EDI to their own supply base. The mandate letter isn't malice; it's pass-through pressure. But pass-through pressure doesn't change the small supplier's arithmetic. It just makes the relationship adversarial.

The Industry's Standard Answer Is Another Login

EDI vendors know small suppliers won't buy full EDI, so the standard fallback is "web EDI": a browser portal where the supplier logs in, views your PO, and manually keys in an 855-shaped response. No integration on their side, no VAN subscription — problem solved, supposedly.

Except web EDI is just a supplier portal wearing an EDI badge. The supplier still has to create an account, remember a password, learn your screens, and re-key data by hand into a system that benefits you, not them. We've written about how that story ends — suppliers juggling eight-plus customer systems, portals decaying into stale data with a login page — in Why Supplier Portals Fail. Web EDI inherits every one of those failure modes. It removes the supplier's software cost and keeps the supplier's adoption cost, which was the binding constraint all along.

So the buyer is left with a false choice: force full EDI and lose small suppliers (or poison the relationship), or accept web-EDI portals and get the same low adoption portals always get.

The Both/And Answer: One Rail, Two On-Ramps

The mistake in the mandate letter is treating EDI as the goal. EDI is a transport. The goal is structured, machine-readable supplier responses landing in your ERP without anyone re-keying them. Once you frame it that way, there's no reason every supplier has to arrive over the same transport.

That's how ERPlisity is built:

• Big suppliers transact EDI — included in the price. Inbound 855/856/865/810, outbound 850/860. No per-document fees, no per-partner setup fees, no VAN fees. Your distributors and contract manufacturers who already run EDI keep running EDI.
• Small suppliers click a magic link in email. The PO arrives as an email; one click opens a response page — no login, no account, no password, free forever for the supplier. From there they confirm, propose date or price changes, split lines, or attach ship notices.
• Both land in your ERP the same way. A magic-link confirmation is written back to your ERP just like an 855 would be — and then read back to verify it actually landed. Your buyers see one unified stream of responses; they don't know or care which on-ramp the supplier used.

The mandate letter becomes unnecessary. You're no longer asking the machine shop to spend money to keep your business — you're sending them an email that's easier to answer than the free-form reply they'd have written anyway. And when a supplier doesn't answer at all, AI order agents chase the unacknowledged PO, read the reply, and recommend the next action instead of leaving it to a buyer's memory.

Pricing follows the same logic: by active suppliers, never per seat or per document. There is no fee structure that punishes you for onboarding your long tail, because the long tail is the point.

Stop Writing the Letter

If a supplier is big enough that EDI is already how they work, meet them there — without paying per document for the privilege. If a supplier is a 15-person shop for whom EDI will never pencil out, meet them in the inbox they already live in. Demanding that everyone use the enterprise transport was only ever necessary because the tooling couldn't handle both. Now it can.

See the full confirmation loop on our PO acknowledgment automation page, check how it connects to your ERP — for example the NetSuite integration — or read the published pricing, EDI included.