Four months later, during a routine check, the brand discovered the co-man was still running production on the old spec. The updated version had been received by one person at the co-man, forwarded to another, and never made it to the production floor. Four months of finished product — technically out of spec.
The version control problem nobody thinks they have
Every brand we talk to believes their co-manufacturer has the current spec. Most of the time, they’re right. But “most of the time” in food manufacturing is not good enough. The consequences of a spec mismatch aren’t a bad report — they’re a potential recall, a failed audit, or months of product that doesn’t meet quality standards.
The root cause is structural. When a brand updates a spec, the update travels by email. It goes to one person at the co-man. That person is supposed to forward it to QA, update production records, and confirm. In practice, one step gets skipped. Nobody catches it until a batch looks different, a customer complains, or an auditor asks.
A former CPO at a top-10 supplement company put it this way: “The fastest way to lose money in CPG is to assume your co-man has the most current spec. Version control issues have derailed more launches and created more firefighting than any raw material shortage I’ve ever seen.”
Why this is a three-team problem
Spec ownership is shared. R&D creates it. QA validates against it. Procurement sources against it. The co-man produces to it. Three teams at the brand and multiple teams at the co-man all need the same version — and it travels via email attachments, PDF forwards, and reply chains.
Email has no version control. When someone sends “Updated Spec v3.pdf” and the co-man’s production floor still has “Spec v2.pdf,” there’s no system that catches the mismatch. Just the assumption that “we sent it, so they have it.”
You don’t have a spec problem. You have a distribution problem. The spec exists. It’s just not in every place it needs to be — and email provides no way to verify that it is.
What resolves this
When communications flow through a shared, structured system, every spec update is captured, versioned, and visible to all teams simultaneously. The CoA that arrives with the next delivery gets compared against the current spec — not the one someone filed six months ago. When there’s a mismatch, the system flags it before production starts.
Related
Waystation captures every spec, every version, every supplier response — so your co-man always has what your R&D team approved.
Book a Demo