Supplier portals failed. Email won

Your brackets come from one machine shop, and that shop serves about forty other customers. A portal asks it to treat you differently from the other thirty-nine: another login, another format, another screen where its sales desk re-keys what its own system already knows. But every one of the forty has had the same idea, and no shop maintains forty portals. It maintains the one channel that reaches all forty at once. It answers email.

That is the entire mechanism. Portals don't fail on software quality; they fail on incentive. The party asked to do the extra work (sign up, log in, re-key) captures none of the value, which lands in your dashboard, not theirs. A supplier can comply once, as a favor to a customer it can't afford to lose. Adoption dies at the second customer, because the asks scale with the number of customers making them, and the favors do not. Twenty years of supplier portals, supplier networks, and collaboration platforms are the same bet under different names: that a thousand small businesses will change how they work for one customer. The bet keeps losing.

Why the demo keeps winning

From your chair, a portal is consolidation: one system, all four hundred suppliers inside it. From the supplier's chair it is fragmentation: one more system, stacked on every other customer's. The demo is always given from your chair. The numbers that decide the outcome live in the other one.

The tell is printed on the vendor's own proposal: the "supplier enablement program": months of onboarding, mail campaigns, and escalation lists to persuade your suppliers to use the thing. Tools that fit a workflow do not ship with a persuasion budget. And enablement is not a launch cost; it is a subscription. The trained contact changes jobs, the login lapses, and the urgent exception goes wherever answers come fastest, which is email. Coverage starts rotting the week the campaign stops.

The exception that proves it

Portals do hold in one configuration: when you are most of the supplier's business. Walmart's Retail Link and the automotive OEMs' EDI mandates work because those suppliers cannot afford to say no. Losing that customer ends them, so the mandate is credible and the compliance gets staffed. Run the same test on your own base: what share of your key suppliers' revenue are you? For a mid-market manufacturer the honest answer is usually a single-digit percent. At that share the mandate isn't credible, and compliance follows dependence: the handful of suppliers who need you most will log in, for a while. The long tail, where your single-source shops usually sit, never will.

Partial adoption is worse than none

Suppose the enablement campaign lands anyway and the head of your supplier base complies. What you have bought is a second source of truth. The compliant suppliers' acknowledgments now live in the portal; everyone else's still arrive by email; and your buyers now reconcile two systems against the ERP instead of one. The work you meant to retire is still there, plus a login. You have also become tech support for your suppliers' sales desks (password resets, retraining, escalations), a standing tax on exactly the relationships you most need goodwill from.

The equilibrium is measurable. At the manufacturing sites we've measured, ~95% of supplier communication still flows over email, two decades into the portal era. That number is not a discipline problem. It is what the incentives produce, and it is stable.