You’ve heard the horror stories of product recalls: The Peanut Corporation of America in 2009, Blue Bell ice cream in 2015, and Darwin’s Raw Pet Foods this year. Beyond the nightmare scenario, the truth is that food recalls are common—even for companies that take food safety seriously, train effectively and keep excellent records. Yet all of these things, when done properly and efficiently, go a long way to reduce the impact and severity of a recall.
Unfortunately, many food manufacturers, although required to have a written recall plan, aren’t ready for the challenge. Without the proper systems in place, businesses needlessly risk their customers, reputation, revenue and future.
Risks Of Inadequate Recall Strategies
Resolving a recall can take years and potentially millions of dollars in fines, product shipping and disposal cost, production line downtime, lawsuits, and lost market share as consumers lose trust in the company. But there are two strategic errors that can amplify these consequences—and they both have to deal with traceability.
The first problem we frequently see is lot codes not being specific enough. Rather than breaking up production into discrete lot codes so the scope of recalls can be as limited as possible, some facilities just run the same lot code for many production runs. The record we have seen so far is three years! When a recall occurs,this results in a recall of massive scope that can easily bankrupt a company.
The second problem that is even more common is a lack of dynamic documentation. Assembling transactions using disconnected records from different departments can be time-consuming and error-prone. When you’re under pressure from regulators or auditors to connect the dots between an ingredient and customers through complex, multi-stage production processes using such a record system, it can cause stress and potential audit failures.
These two missing pieces make recalls larger, more time-consuming, and more expensive than necessary due to a lack of precise traceability. Let’s take a look at the two ways you can fill these gaps in your system and mitigate the consequences of recalls.
See link above for the full text