Now that the Food and Drug Administration has the power to invoke mandatory recalls, as granted by the Food Safety Modernization Act (FSMA), the speed and accuracy of your recall process has never been more important. The federal watchdog’s new teeth can be expected to leave their mark on more food companies, forcing the halt of distribution of suspect products — and that could affect your own supply chain. Fortunately, software technology can help ensure your business never makes it onto the FSMA mandatory food recall list.
Lot tracking is the place to start, but it should be noted that a recall program is not just signing off on a review of the traceability process. While that’s necessary, it doesn’t determine if your company can conduct an effective product recall. An effective recall program should include:
- Notification of an incident in real-time during production or distribution.
- A thorough investigation including tracking and tracing the potentially affected product.
- Testing conducted through mock recalls.
- Assessment of the risk to health and safety, and to your company’s reputation.
- Effective communications both internally and externally to the supply chain.
- Processes in place to monitor the effectiveness of the recall.
- Response to requirements, concerns and expectations of key stakeholders.
- Reviewing and continually improving processes and systems as new conditions arise.
Inquiry Tracking gives you the ability to track concerns from customers and vendors, and it lets you organize the call information electronically for quick access and historical purposes. In some Enterprise Resource Planning (ERP) software, you can initiate an Item Trace from right within the Inquiry Tracking screen in a user’s role center, and trace the item forward and backward.
Within the Trace functionality, you can see the trace from the purchase of raw materials to the production orders that consumed them, and all the way to the shipment of the finished goods. The Item Trace can then automatically create a compilation of all the contacts that received the finished goods. There should be visibility between Inquiry Tracking and Recalls within your ERP system — so that a customer complaint can be linked to a recall.
Global food safety standards, such as BRC, require that both traceability and recall are tested. In the latter case, mock recalls can be compared to fire drills — making sure everyone knows their role, and how long it takes to fulfill those roles. A good idea is to throw in some ‘curveballs’ to your mock recall to make sure you’re prepared for the unexpected by using strong internal and external communications. The only difference between a mock recall and a real one should be that external communications are not sent externally to your supply chain in the case of the mock recall.
Sahale Snacks: “Now anyone can begin a recall”
One food manufacturer, Seattle-based Sahale Snacks, which makes nut-based bars sold at more than 4,000 locations across the U.S., has been ahead of the compliance curve. Sahale had been through the 2010 nationwide pistachio recall as a result of one of their suppliers, during which they had to make do with Excel pivot tables, says Lindsay Palmer, Sahale’s supply chain coordinator. “Although we got through that recall with flying colors, the effort to do so was tremendous,” with diverse spreadsheets and a lack of a centralized data system resulting in much labor redundancy.
Now that the FDA has the power to invoke mandatory recalls, under the Food Safety Modernization Act, the speed and accuracy of the recall process has never been more important. The federal watchdog’s new teeth can be expected to leave their mark on more food companies, halting the distribution of suspect products — and that could affect your own supply chain.