Waystation

Procurement emails the supplier for pricing. QA emails the same supplier for a certificate. R&D emails them for a spec. Nobody knows the other two reached out. This is the structural problem nobody talks about.

The Collision Nobody Sees

Here’s what happened at a $200M supplement company last quarter:

On Monday, procurement emailed Supplier X requesting updated pricing for three ingredients. On Tuesday, QA emailed the same supplier requesting a renewed GFSI certificate. On Wednesday, R&D emailed them asking for a spec sheet update on one of those same ingredients.

Three emails. Same supplier. Same week. None of the teams knew the others had reached out.

The supplier responded to each team separately. Procurement got pricing but not the cert. QA got the cert but not the spec. R&D got the spec but didn’t know procurement was running a pricing comparison. The information existed — it was just trapped in three different inboxes.

Three teams. Same supplier. No shared record of what came back. This isn’t a communication failure. It’s an architectural one. And it’s costing mid-market CPG companies a couple of percentage points of their largest cost line, every quarter.

Why CPG Has This Problem (And Other Industries Don’t)

In most industries, a company buys finished goods. One team places the order. The relationship is transactional.

In CPG, companies buy raw ingredients — each with its own specs, certifications, safety requirements, and pricing. This means the supplier relationship spans three distinct functions:

  • R&D evaluates ingredients, requests specs and samples, owns the formulation relationship.
  • QA collects compliance documents — CoAs, allergen statements, GFSI certs, HACCP plans — for every ingredient, every supplier, every batch.
  • Procurement negotiates pricing, manages lead times, runs RFPs, keeps the factory supplied.

Each team has a legitimate, independent reason to contact the same supplier. The problem isn’t that they’re doing their jobs. It’s that there’s no shared system connecting their conversations.

Email was always the system of record. But email is, by design, private. Your inbox is your inbox. Nobody else sees it.

What It Looks Like in Practice

Supplier confusion. The supplier gets three separate requests from the same company. They don’t know who to prioritize. Sometimes they send the same document to two teams. Sometimes they don’t respond to one because they assume another team already got it.

Duplicated work. QA requests a CoA. Procurement already has it in their inbox from a different thread. QA doesn’t know. The supplier sends it again. Multiply across 50–200 suppliers and this duplication is constant.

Decisions made on partial data. Procurement runs an RFP without knowing that QA flagged a quality issue with one of the bidding suppliers last month. R&D approves a new ingredient without realizing procurement has better pricing from an alternate. Each team optimizes locally. Nobody optimizes globally.

Institutional memory loss. When any single person leaves, everything in their inbox goes with them. The supplier history, the pricing context, the document trail — gone. The next person starts from zero.

The Margin Math

Raw material spend is typically 50%+ of revenue for CPG companies. A $200M company spends $100M+ on ingredients annually.

A couple of percentage points of that spend lost to coordination failures — overpaying because pricing data is fragmented, emergency premiums because alternatives weren’t pre-identified, write-offs because documentation failed — equals $2M–$3M per year. Not in one dramatic incident. In thousands of small, invisible ones.

This is the coordination tax. It doesn’t appear on the P&L. It hides inside raw material costs that are higher than they need to be, headcount spent on administrative work instead of strategic sourcing, and RFPs that never get run because the prep work takes too long.

The coordination tax compounds quarterly. Prices drift up. Suppliers get comfortable. Strategic work gets deferred. By the time you see it, you’ve been paying it for years.

Why Nobody Fixes This

“We already have a process.” Yes. The process is email. It technically works. It’s also the most expensive system you can run — you just can’t see the invoice.

“We tried a portal.” Of course it didn’t work. Portals ask suppliers to change behavior. Suppliers won’t. Fifteen companies have tried this approach in CPG. All fifteen failed for the same reason.

“This is just how the industry works.” It was. Email was always the system of record for CPG procurement. But “the system of record” and “usable data” used to be mutually exclusive. LLMs changed that. AI can now extract structured data from unstructured supplier emails at production-grade accuracy. The constraint that made this problem unsolvable has been removed.

The Fix: One Shared Record, Zero Behavior Change

The three-team problem disappears when every supplier email — regardless of which team received it — is captured, extracted, and made visible to everyone who needs it.

That’s what inbox-native procurement intelligence does. It connects to your team’s email and builds a shared, searchable record of every supplier interaction across procurement, QA, and R&D. Every quote. Every spec. Every CoA. Every certification.

Suppliers don’t know it exists. They keep emailing as they always have. Your teams keep working as they always have. The difference is that now, when procurement runs an RFP, they can see that QA flagged a quality concern. When QA checks a cert, they can see that R&D already has the latest version. When anyone needs anything, it’s already there.

Don’t change behavior. Capture reality.

Waystation gives procurement, QA, and R&D a shared view of every supplier interaction — captured from the emails they’re already sending. No portals. No behavior change. Same-day go-live.

Book a Demo

Frequently Asked Questions

Why do three teams email the same suppliers independently in CPG?

CPG companies buy raw ingredients, not finished goods. Each ingredient requires involvement from R&D (specs and formulation), QA (compliance and documentation), and procurement (pricing and supply). Each team has legitimate, independent reasons to contact suppliers — and no shared system connecting their conversations.

What is the coordination tax?

The coordination tax is the hidden cost of three teams managing supplier relationships through disconnected email inboxes. It shows up as margin leakage, duplicated outreach, compliance gaps, and strategic work that never gets done. For most mid-market CPG companies, it represents a few percentage points of total raw material spend.

How does the three-team problem affect margins?

When pricing data is fragmented across inboxes, companies overpay for ingredients without realizing it. When RFPs are too slow to run, incumbents keep pricing unchallenged. When documentation fails, companies pay emergency premiums or write off product. These compound to a few percent of raw material spend annually.

Why didn’t supplier portals solve this?

Portals capture documents but not the supplier relationship. Even with a portal, procurement, QA, and R&D still coordinate through email. The portal adds a document repository but doesn’t solve the visibility problem across teams. And most suppliers don’t use portals anyway.

What is inbox-native procurement intelligence?

It connects to your team’s email and uses AI to extract structured data from supplier communications. Every quote, spec, CoA, and certification is captured into a shared workspace. All three teams see the same data. Suppliers don’t change anything — they keep emailing as they always have.

How do you create a shared system of record without asking suppliers to change?

By capturing data from the emails suppliers are already sending instead of asking them to upload to a portal. LLMs can now extract structured data from unstructured supplier communications at production-grade accuracy — making email usable as a real data layer for the first time.

Leave a Reply

Discover more from Waystation

Subscribe now to keep reading and get access to the full archive.

Continue reading