Waystation

Field Notes
April 2026·4 min read
The production run was staged. Ingredients were in the warehouse. Packaging was ready. The team had been preparing for days.

That morning, someone on the ops team noticed the almond butter variant was wrong. Not the wrong brand — the wrong formulation. Different roast profile, different viscosity. Close enough to look right in the warehouse. Wrong enough to ruin 10,000 units.

They caught it before it hit the line. But the production run was cancelled. The schedule had to be rearranged. Another product got bumped. Downstream delays cascaded for days.

This wasn’t a supplier failure

The supplier shipped exactly what was ordered. The purchase order matched the invoice. Everything checked out on paper.

The failure was upstream — in the gap between R&D’s formulation spec, procurement’s purchase order, and the ops team’s staging instructions. Three teams, three versions of what “the right almond butter” meant. Each version was in a different inbox, a different spreadsheet, a different Slack thread. No single source of truth.

The CEO told us: “We’re not ahead of it. And we’re not ahead of it because of all the extra work we’re doing to fix the last thing we weren’t ahead of.” That’s the coordination tax in a sentence — a self-reinforcing cycle where the chaos from the last failure consumes the bandwidth that would prevent the next one.

Three teams, one supplier, zero shared context

In CPG, procurement, QA, and R&D all touch the same suppliers for different reasons. R&D needs the spec. QA needs the CoA and certifications. Procurement needs the PO confirmed. Each team emails independently. Each maintains their own records. Nobody sees the full picture.

When the spec changes — a different roast profile, a lower sugar threshold, a new allergen requirement — the update has to flow to every team and every co-manufacturer simultaneously. In practice, it flows to whoever R&D remembers to cc. The co-man might still be running on a spec from six months ago.

The wrong ingredient in the warehouse is almost never a purchasing error. It’s a communication error that purchasing inherited.

What fixes this

Not more process discipline. Not another checklist. The fix is a shared system of record where all three teams see the same spec, the same supplier response, the same version — without anyone having to forward an email or update a spreadsheet. When supplier communication is structured automatically from email, the spec that R&D approved is the same one procurement ordered and the co-man received.

The CEO at this company estimated these cascading failures cost them 15–20 lost production days per year. At their scale, that’s seven figures in wasted capacity.

Waystation gives procurement, QA, and R&D one shared view of every supplier interaction. No portals. No behavior change.

Book a Demo

Leave a Reply

Discover more from Waystation

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

Continue reading