The call came at 7:20 am on a Tuesday. A co-packer had shipped 4,000 cases of a snack bar with the old recipe printed on the box and the new recipe inside. The new version contained a tree nut oil the old one didn’t. Retailers pulled it, and the recall, freight, credits, and overtime came to $260,000.
Here’s the part that stings. The ingredient change was approved two months earlier, by the right people, in writing. The decision was fine. The follow-through wasn’t.
Everything was approved and nothing was updated
When we walked the change backward, it had passed through five pairs of hands and stopped in three places.
- The recipe was updated in the kitchen binder but not in the packaged product’s component list.
- Packaging artwork was revised on a shared drive. The printer still had version six.
- The line supervisor knew about the change. The second-shift supervisor, who started the following Monday, did not.
Five people each knew one piece. Nobody knew the whole thing, and that gap is where the $260,000 lives.
When ERP Consulting was asked to look at the recall cost afterward, the finding was uncomfortable. The company had a documented approval process and no documented handoff process. Approvals were covered. Handoffs weren’t.
The change process they built afterward
They kept it deliberately boring. One form, one owner, one effective date, and a physical check at the first production run.
- One owner per change. The product manager signs their name and is responsible for every downstream step, including the printer.
- A single effective date with a countdown. That date is reviewed at the daily production meeting for the two weeks before it lands.
- First-run verification by someone outside production. Quality stands at the end of the line for the first 200 units and signs off with a photo.
- Old versions get destroyed, not shelved. If the old packaging is still in the building, someone will use it at 11 pm during a rush.
The number that got the board’s attention
The company runs about 40 product changes a year. At the old error rate, roughly one in ten caused a problem worth chasing. The new process caught 11 issues in its first year before the trucks left the yard.
The general manager put it better than any policy document could: a change isn’t done when it’s approved, it’s done when the first good case ships. That sentence, written on a card and taped above the line, did more than any dashboard.
If you make anything with a recipe or a drawing, grab the last five changes your team made. Ask one question about each: who signed off that the packaging or documentation matched the product? If the answer is “the same person who made the change,” you have a hole worth fixing this month.