Case Study
A 400-SKU CPG brand reordered Revision 1 of a label. The current spec was Revision 2. Here's what happened next.

One of our customers manages a label program with 400+ active SKUs across multiple retail channels. Revisions happen constantly — formula changes, regulatory updates, packaging refreshes. Their team is sharp. But when you've got 400 line items moving in parallel, a slip is statistically inevitable.
Last quarter, their purchasing agent placed a routine reorder for a label. The PO referenced "[SKU] — Cherry Almond Bar — 10,000 labels." The artwork was their previous version: Revision 1.
The current approved spec was Revision 2, which had been finalized three months earlier. The revision had updated the ingredient panel after a supplier change. Reprinting Revision 1 would have meant labels with outdated ingredient information — a regulatory issue and a recall risk.
Our pre-press team noticed the version mismatch during artwork review. They flagged it before the job hit the press. A 5-minute call to the customer's purchasing agent resolved the discrepancy: yes, they wanted Revision 2.
The customer estimated the cost of catching this on the back end — after labels were printed, applied, and shipped — at roughly $10,000 in scrap, rework, and recall risk. We caught it on the front end for the cost of one phone call.
This isn't a technology story. It's a tribal-knowledge story. Our team has been working with this customer's program for years. We knew what version was current. A label vendor that churns its team every 18 months wouldn't have caught it — they'd have printed exactly what the PO requested.
That's what independence and tenure buy you.
// READY TO PRINT
Quotes in 4 hours or less. Decision-makers in 2 minutes or less. Independent since 1991.