The central lie of procurement software is that if you build a better portal, suppliers will come. They won’t — and twenty years of evidence shows it.
Food and beverage procurement has survived at least 15 attempts since 2000 to fix supplier coordination with a portal. Every wave had better UX than the last. Every wave promised this would finally be the one. Every wave produced the same outcome: suppliers kept using email, portals filled with stale data, and consultants got paid to “enable” a system the market was already rejecting.
The software wasn’t broken. The premise was.
Email is not a legacy. It’s the coordination layer.
Procurement runs on email because email is the only coordination layer that survives the real conditions of the market — fragmentation, exceptions, shared accountability across departments, and a long tail of small suppliers with no incentive to standardize.
A cinnamon vendor supplying 37 bakeries is not going to maintain 37 portal logins. Not because they’re stubborn. Because the economics don’t work. Email is the universal adapter that works for every buyer, every format, every urgency level.
Every serious attempt to replace email has collided with this reality and lost.
What procurement actually is
The deeper error is calling the work “procurement” as if it were purchasing. It isn’t.
CPG procurement is the orchestration of ingredients and packaging through a web of partners — R&D approving specs, QA validating documentation, sourcing negotiating price and availability, operations absorbing lead times, finance managing working capital. Every decision crosses three or four functions.
Portals were built for a fantasy where a buyer sends a structured RFQ and gets a structured response. The actual workflow looks like:
- R&D loops in a new flavor house mid-cycle.
- QA asks the supplier for an updated HACCP plan.
- Procurement negotiates against a second vendor whose CoA hasn’t come through.
- Operations pushes back because lead times shifted.
- Finance flags that the MOQ doesn’t match cash planning.
No portal captures this. Email does, messily but completely.
AI didn’t make portals better. It made them unnecessary.
For twenty years, the only way to get structured supplier data was to force structure at the entry point. That’s what portals did, and in a pre-AI world, it was the only path.
Large language models inverted the assumption. You no longer need suppliers to enter structured data. You can let them email quotes, specs, CoAs, certifications, and shipping notes in whatever format they use — and extract the structure on your side of the wire, automatically.
The portal’s reason for existing disappeared. What remains is muscle memory in procurement software vendors still selling the old architecture.
What the right model looks like
Meet work where it already happens. Supplier communications flow through email exactly as they always have. Structured data — pricing, specs, CoAs, certifications, lot codes, lead times — gets extracted automatically and organized into a shared, searchable workspace.
- Suppliers don’t adopt anything.
- Procurement doesn’t re-key anything.
- QA, R&D, and sourcing see the same record.
- Institutional knowledge compounds instead of evaporating.
The intelligence layers onto the existing workflow. The workflow doesn’t bend to the software.
Why this matters for CPG
Food, beverage, supplement, and pet food procurement is the category most damaged by the portal lie because it’s the most document-heavy. Every ingredient carries specs, certifications, CoAs, and allergen declarations. Twenty years of trying to cram that reality into portal-shaped software produced hours of re-keying and chronic documentation gaps.
The shift to AI-native, email-first procurement isn’t a marginal improvement. It’s a correction.
The Waystation position
Waystation was built on this premise. We don’t ship a supplier portal. We don’t run enablement programs. We don’t ask suppliers to change anything — because we don’t need them to.
We connect to your team’s inbox and turn the email you already get into structured, shared, audit-ready data. The work stays where it lives. The intelligence appears underneath it.
That’s the future. The portal era is over.
