The New Federal Food Traceability Rule is Just Three Months Away

The FDA’s strict, new food traceability rule is due to become official November 7. Are you ready?

The new rule covers the following Food Traceability List; a list of “high risk foods” implicated in food-born illnesses:

• Cheeses other than hard cheese
• Crustaceans
• Cucumbers
• Fin fish
• Fresh herbs
• Fresh-cut fruits and vegetables
• Leafy greens
• Melons
• Mollusks
• Nut butters
• Peppers
• Ready-to-eat deli salads
• Shell eggs from domesticated hens
• Sprouts
• Tomatoes
• Tropical tree fruits

To make these foods safer, the rule requires a detailed account of food origins and movements throughout production, processing and shipping, even as these foods are transformed into other food products, or as other foods are added to them.

This poses special challenges, as many foods trace back through multiple processing stages, each adding to traceability challenges.

Keeping records this extensive is often nearly impossible with pencil and paper, or even with ordinary spreadsheets, so barcoding has never been more important. Barcode data systems offer affordable, robust, user-friendly solutions that trace product origins and destinations from end to end.

SIMBA, from Dynamic Systems, integrates user-friendly plant floor labeling and processing devices to real-time tracking and ERP systems in the office, tracing each product lot through every production stage. When a whole salmon becomes filets, then they become salmon cakes, each part of the process automatically traces back to the fish and the boat it came from. Similarly, when fresh fruit is sold to a company that makes fruit salad, the salads trace back to the grower, with every transfer recorded.

In the new FDA rule, these required data points are called Key Data Elements, or KDEs. The stages in the production process are referred to as Critical Tracking Events, or CTEs.

Here are the Critical Tracking Events and their required KDEs:

• Growing:For produce, the grower initiates a lot code for the food grown.
• Receiving: When any listed food is received, the lot code must link to the following information.
  • Location identifier and location description for the immediate previous source (other than a transporter) of the food
  • Entry number assigned to the food (if imported)
  • Location identifier and location description of where the food was received, and the date and time the food was received
  • The quantity and unit of measure of the food (e.g., 6 cases, 25 returnable plastic containers, 100 tanks, 200 pounds)
  • Traceability product identifier and traceability product description for the food
  • Location identifier, location description, and point of contact for the traceability lot code generator
  • Reference record type(s) and reference record number(s) (e.g., “Invoice 750A,” “BOL 042520 XYX”) for the records relating to receipt of the food
  • The name of the transporter who transported the food to the receiver
  • The proposed rule will introduce the first receiver designation, which carries additional information needs. Afirst receiver is the first person (other than a farm) who purchases and takes physical possession of a listed food. Only foods that are originated (i.e., grown, raised, caught, or, in the case of a non-produce commodity such as eggs, harvested) can have a first receiver. Listed foods that are created (such as a ready-to-eat deli salad that is not made from any listed ingredients) do not have a first receiver.
    • The purpose of the first receiver rule is to track movements of products within or between organizations before sale.
    • First receivers are required to maintain different KDEs depending on whether the food was obtained from a fishing vessel or not.
    • The proposed rule would require each first receiver of a food on the FTL to establish and maintain records, in addition to the records of receipt of food (receiver KDEs), containing and linking the traceability lot code of the food received to the following information:
      • First Receiver (except for seafood obtained from a fishing vessel)
        • Traceability lot code (if not previously established, the first receiver would be required to establish the traceability lot code and maintain records linking the traceability lot code to the other KDEs)
        • Location identifier and location description of the originator of the food
        • Business name/phone number/ point of contact of harvester of the food and the date(s) and time(s) of harvesting
        • Location identifier and location description of the place the food was cooled, and the date and time of cooling (if applicable)
        • Location identifier and location description of the place where the food was packed, and the date and time of packing
      • First Receiver of Seafood Obtained from a Fishing Vessel
        • Traceability lot code (if not previously established, the first receiver would be required to establish the traceability lot code and maintain records linking the traceability lot code to the other KDEs).
        • Harvest date range and locations (National Marine Fisheries Service Ocean Geographic Code or geographical coordinates) for the trip during which the seafood was caught.
• Transformation: Changing a food on the Food Traceability List, its package and/or its label (regarding the traceability lot code or traceability product identifier), such as by combining ingredients or processing a food (e.g., by cutting, cooking, commingling, repacking, or repackaging). The transformer of the food would be required to establish and maintain records containing and linking the new traceability lot code of the food to the following information:
• Transformation KDEs
  • Traceability product identifier and traceability product description for the foods used in transformation
  • The quantity of each traceability lot of the food used in transformation
  • Location identifier and location description for where the food was transformed and the date the transformation was completed
  • The new traceability product identifier and traceability product description for the food produced through transformation
  • The quantity and unit of measure of the food produced through transformation (e.g., 6 cases, 25 returnable plastic containers, 100 tanks, 200 pounds)
  • Reference record type(s) and number(s) for records relating to transformation
• Creation: Creating a product on the high-risk list, such as peanut butter, from items not on the list, such as peanuts. Whoever creates a listed food this way would be required to establish and maintain records containing and linking the traceability lot code of the food created to the following information:

• Location identifier and location description of where the food was created, and the date creation was completed
• The traceability product identifier and traceability product description for the food
• The quantity and unit of measure of the food
• Reference record type(s) and reference record number(s) for records relating to creation
• Shipping: When food is transported from a defined location to another defined location at a different farm, a first receiver, or a subsequent receiver. The proposed rule would require persons who ship a listed food to establish and maintain records containing and linking the traceability lot code(s) for the food to the following information:

• Entry number(s) assigned to the food (if imported)
• The quantity and unit of measure of the food
• Traceability product identifier and traceability product description for the food
• Location identifier, location description, and point of contact for the traceability lot code generator
• Location identifier and description of the immediate subsequent recipient of the food (other than a transporter)
• Location identifier and location description for the location from which the food was shipped, and the date and time the food was shipped
• Reference record type(s) and reference record number(s) for documents relating to shipment
• Transporter’s name who transported the food from the shipper

In addition to keeping all of the above records, the shipper would need to send all of these records, with the exception of the reference record type and number and the transporter’s name, to the immediate subsequent recipient. If the shipper is a farm, they would also be required to send the following information (if applicable) to the immediate subsequent recipient:

• A statement that the shipper is a farm
• Location identifier and location description of the originator of the food (if not the shipper)
• The business name, point of contact, and phone number of the harvester of the food (if not the shipper), and the date(s) and time(s) of harvesting
• Location identifier and location description of the place where the food was cooled (if not by the shipper), and the date and time of cooling
• Location identifier and location description of the place where the food was packed (if not by the shipper), and the date and time of packing

At each of these events, KDE’s must include lot codes for traceability. Full details are at the FDA site. And, while the FDA acknowledges this will force changes away from old fashioned paper-and-pencil record keeping, financial benefits will far outweigh costs as traceback time is reduced by up to 84 percent.

SIMBA handles all of this, assigning lot codes up front, when meat or seafood is received at the processor, or when produce is grown. From that point onward the lot code follows the food, even as it is divided, transformed and shipped. Tracing origins is then merely a matter of a few clicks.

About SIMBA Solutions

SIMBA Solutions provides the fresh seafood, meat and produce industry proven, reliable systems for labeling, tracking and tracing inventory. It is a division of barcode systems software developer and solutions provider Dynamic Systems, Inc., a privately held company founded in 1981 and still led by founder CEO Alison Falco.