A brand sent updated specifications to their co-manufacturer four months prior, including revised protein levels, new allergen language, and updated shelf-life claims. The co-man confirmed receipt via email. During a routine quality check, the brand discovered production was still running on the outdated specification. The updated version had been received by one person, forwarded to another, but never reached the production floor. Four months of finished product was technically out of spec.
The version control problem nobody thinks they have
Most brands assume their co-manufacturer operates with the current specification. However, “most of the time” is insufficient in food manufacturing. The consequences of specification mismatches extend beyond poor reports to potential recalls, failed audits, or months of non-compliant product.
The structural issue is straightforward: when a brand updates a spec, communication travels via email to one co-man contact. That person should forward it to QA, update production records, and confirm receipt. In practice, steps get skipped. Discovery only happens when batches look different, customers complain, or auditors question the records.
A former Chief Procurement Officer at a major supplement company observed: “The fastest way to lose money in CPG is to assume your co-man has the most current spec.” Version control issues have disrupted more launches and created more operational firefighting than raw material shortages.
Why this is a three-team problem
Specification ownership is distributed across multiple parties. R&D creates it. QA validates against it. Procurement sources to it. The co-man produces to it. Three brand teams and multiple co-man teams require the same version, yet it circulates through email attachments, PDF forwards, and reply chains.
Email lacks version control infrastructure. When someone sends “Updated Spec v3.pdf” while the production floor retains “Spec v2.pdf,” no system identifies the mismatch. The assumption persists that “we sent it, so they have it.”
The actual problem isn’t the specification itself — it’s distribution. The spec exists but isn’t reaching every necessary location, and email provides no verification mechanism.
What resolves this
When communications operate through a shared, structured system, every spec update becomes captured, versioned, and simultaneously visible to all teams. Certificates of Analysis arriving with deliveries get compared against the current specification rather than outdated filed versions. Mismatches trigger system flags before production commences.
