The Lie at the Center of Procurement Software
Procurement in food, beverage and broader CPG runs on email because that is the only coordination layer that survives fragmentation, exceptions, and shared accountability.
This isn’t legacy behavior. It’s rational behavior.
The industry fails not because teams resist software, but because most software assumes you can standardize behavior before you deliver value. In food & beverage, that assumption is fatal. Suppliers won’t adopt portals, workflows aren’t linear, and one missing document can stop production.
Procurement in CPG is not “buying.” It is running the product across R&D, QA, sourcing, co-manufacturers, and distributors — all with asymmetric power and zero shared system. Failure costs dwarf negotiated savings.
Email and documents contain the highest-fidelity data in the system — quotes, specs, COAs, certifications, lot traceability — but historically required humans to structure them. AI changes this single constraint: it makes unstructured reality computable without changing how people work.
The winning systems will not replace email or force adoption. They will capture truth where work already happens, turn it into a system of record, and only then create leverage.
Portals don’t fail because teams didn’t try hard enough.
They fail because they violate the laws of the industry.
Supplier portals don’t work.
Ever.
Not “we haven’t found the right UX yet.”
Not “suppliers are behind.”
Not “procurement is slow to adopt tech.”
They don’t work because the model is wrong.
Portals assume you can change behavior first, and get value later.
In CPG procurement, behavior change is the product’s death.
Email is the only protocol everyone actually uses. It’s the universal adapter. It’s the last shared interface across suppliers, co-mans, QA teams, R&D, freight brokers, and distributors. You can hate it. You can try to replace it. You will lose.
For the last decade-plus, technology companies have tried anyway. Supplier networks. Vendor onboarding platforms. Marketplaces. “SRM.” “Supplier collaboration.” Different brand names. Same bet: drag the supply base into a new system.
It’s been tried at least 15 times since 2000. It keeps failing for the same reasons.
Suppliers don’t want another login. They don’t want another form. They don’t want another “mandatory workflow.”
They already have a workflow. It’s called: inbox.
And suppliers are rational.
If you sell cinnamon, citric acid, pouches, or caps, you are not going to run your business across 37 buyer portals. Every buyer thinks they’re the center of the universe. They aren’t. You won’t staff a team just to copy-paste your COA into someone’s dropdown menu.
So you do what works. You email. You attach PDFs. You say “see attached.” You forward a thread from six months ago. You send a screenshot.
It’s messy. It’s also how the industry moves.
Here’s the part most people miss.
Procurement tech has historically tried to eliminate unstructured communication.
AI lets us use it.
That’s the shift.
CPG procurement isn’t “buying.” It’s running the product.
In food & beverage, direct procurement isn’t a back-office function. It is the product.
Unless you’re a smaller company doing turnkey with a co-man, you are almost never buying a finished good and putting a label on it.
You’re orchestrating ingredients and packaging through a web of partners, with shared responsibility and zero shared visibility. Brands. Co-manufacturers. 3PLs. Distributors. Suppliers. Auditors. Retail requirements.
A single missing document can stop a line. A single wrong spec can waste a run. A single late shipment can kill a launch.
And none of it is linear.
If you think procurement is “get three quotes, pick the cheapest, place a PO,” you’ve never watched a mid-market brand try to ship product.
In reality, every purchase sits inside a triangle:
- R&D decides if it works. Taste. Texture. Behavior on the line. Samples. Bench tests. Consistency across lots.
- QA decides if you can defend it. Specs. COAs. HACCP. Traceability plans. Signed questionnaires. “Cover your ass” documentation.
- Procurement decides if it’s viable. Price, yes. But also Incoterms, lead time, MOQ, capacity, safety stock, and reliability.
Any corner of that triangle can restart the process at any time.
R&D finds a new ingredient and triggers an RFP. QA sees a quality issue and forces a re-approval. Sourcing sees margin pressure and re-bids the category.
This is not a clean workflow. It’s a living system.
Portals are built for clean workflows.
That’s why they break on contact.
Email used to be procurement’s liability. Now it’s the asset.
For years, supplier email was treated like a problem to be solved.
“Can we get them into our system?”
Good luck.
Here’s the contrarian truth: suppliers emailing abundant unstructured information is not a bug. It’s the richest data feed in the industry.
Quotes. Incoterms. Lead times. MOQ changes. Spec sheets. Certifications. Allergen statements. Organic certificates. Kosher letters. COAs tied to lot numbers. Traceability docs. Recall plans. HACCP plans.
It’s all there.
It’s just not structured.
In the old world, the only way to turn that into a system was humans. Coordinators. Analysts. Procurement ops. Endless follow-up. Endless copy/paste.
In the new world, software can read it.
LLMs don’t need suppliers to behave like APIs. They can interpret how suppliers already communicate. They can extract structure from the mess at scale. They can turn “see attached” into fields, status, approvals, and alerts.
This is the breakthrough: you stop trying to standardize the world. You start standardizing your understanding of it.
That’s how you get day-one value without a change management crusade.
No supplier login.
No onboarding circus.
No “please update your profile.”
Just: send the email like you always do. The system does the rest.
Why smart people still get this wrong
Two common misunderstandings lead teams to build the wrong thing.
Mistake #1: “Food & beverage is too small.”
This is what people say when they don’t understand fragmentation.
They see small teams and miss the system.
There are tens of thousands of brands. Spend is massive (often 40-50% of revenue). Buying is constant. Failure tolerance is near zero. And the workflows still run on email and spreadsheets.
So outsiders build “horizontal” tools that work across industries.
Which means they miss what’s unique here.
They ignore the documents, the non-linear QA/R&D/sourcing workflow, the shared responsibility across brands and co-mans, and the fact that one missing certificate can stop production.
Food & beverage isn’t too small. It’s too specific.
Generic software doesn’t survive specificity.
Buying cinnamon is not the same as a car company buying windshield wipers or a pharma company buying activity ingredients. The stakeholders, data, process, and risk are unique to their vertical.
Mistake #2: “Start with supplier discovery.”
Discovery demos well. It feels like progress. It produces lists.
It also disappoints customers over and over. Don’t believe me? Ask a current customer of a platform that promises supplier discovery. I’ve talked to hundreds.
Because supplier discovery is not a simple search problem.
It requires a deep, constantly updated knowledge graph of the industry. It’s prone to disintermediation if it becomes transaction-based. And for many teams, it’s not the most severe or consistent pain.
The consistent pain is validation and execution.
Can this supplier actually ship?
Are the documents actually in place?
Do we have the COA for this lot?
Are we going to pass an audit?
Can we run production Monday?
Discovery is “nice.” Validation is existential.
The tradeoff we choose: meet reality where it is
Here’s the line in the sand.
We are not building software that demands people become different.
We are building software that makes the current system finally work.
That means:
-We do not require supplier adoption first.
-We do not make email the enemy.
-We do not pretend procurement is linear.
-We do not optimize for pretty dashboards while teams chase certificates at midnight.
We take the mess. We turn it into a system of record. We turn the record into leverage.
Because once you have the truth captured—every quote, spec, cert, and thread—everything else becomes possible.
Benchmarks become real. Supplier performance becomes measurable. Reliability stops being a vibe. Switching costs stop being folklore.Category strategy becomes data-driven, not anecdotal.
And the punchline is simple:
The product is the supply chain.
So build the system that actually runs it.
The future is not “portals, but better.” It’s intelligence, where the work already happens.
Portals don’t fail because teams didn’t try hard enough.
They fail because they fight the laws of the industry.
Email is the substrate. Documents are the currency. Exceptions are the norm.
AI changes one thing: it makes that reality computable.
That’s the whole game.
Stop trying to move suppliers into your world.
Start using a system that can understand theirs.