What Is the Transformation CTE?

The Transformation CTE is the Critical Tracking Event triggered when food is manufactured, processed, or changed -- by commingling, repacking, or relabeling -- and the output is a food on the Food Traceability List (FTL). It requires recording 3 KDEs per input lot and 6 KDEs for the output, and it is the only CTE that requires linking input Traceability Lot Codes to new output TLCs (Source: 21 CFR 1.1350).

This is the most data-intensive CTE in FSMA 204.

What are the required Input KDEs?

For each FTL food used in the transformation, record:

| # | Key Data Element | Example | |---|-----------------|---------| | 1 | Traceability Lot Code for input food | "LOT-A-001" | | 2 | Product description for input food | "Romaine hearts, 3-pack" | | 3 | Quantity from each input lot utilized | "4 cases" |

If a transformation uses 15 lots of romaine from 8 farms, each lot's TLC must be recorded individually with the quantity used.

What are the required Output KDEs?

For the transformed food produced, record:

| # | Key Data Element | Example | |---|-----------------|---------| | 4 | New Traceability Lot Code assigned | "MIX-B-002" | | 5 | Transformation location (= TLC source) | Processing facility name, address | | 6 | Date transformation completed | "2028-03-16" | | 7 | Product description of transformed food | "Spring mix salad, 5oz bag" | | 8 | Quantity and unit of measure of output | "200 bags" | | 9 | Reference document type and number | "Production record #PR-123" |

The transformation location becomes the TLC source for the new output TLC.

When does transformation apply?

| Activity | Transformation CTE? | |----------|---------------------| | Washing and bagging loose spinach into retail bags | Yes -- commingling + repacking | | Cutting whole melons into fresh-cut fruit | Yes -- processing | | Smoking fresh salmon into smoked salmon | Yes -- processing | | Combining multiple lots of romaine into a spring mix | Yes -- commingling | | Relabeling cases of produce with store brand | Yes -- relabeling | | Simply storing and reshipping produce | No -- receiving and shipping only | | Cooking produce into a frozen meal (non-FTL output) | No -- output is not on the FTL |

The key question: is the output a food on the Food Traceability List? If the transformation produces something that is not on the FTL, the Transformation CTE does not apply.

Why does linking input TLCs to output TLCs matter?

The input-to-output TLC link is the critical traceback mechanism in FSMA 204. Without it, the FDA cannot trace a contaminated product back to its source ingredients.

Here is how traceback works through a transformation:

FDA identifies contaminated "Spring Mix Salad" at a retailer
  --> Output TLC "MIX-B-002" on the package
    --> Transformation record links to input TLCs:
        Input TLC "LOT-A-001" (Romaine, 4 cases from Farm A)
        Input TLC "LOT-C-003" (Spinach, 2 cases from Farm C)
        Input TLC "LOT-D-004" (Kale, 1 case from Farm D)
    --> Each input TLC traces back through shipping/receiving records
        --> To initial packing records
            --> To harvest records with specific farm and field

Without the transformation link, the FDA would know the spring mix is contaminated but could not determine which farm, which field, or which harvest date was responsible.

Are restaurants exempt from the Transformation CTE?

Yes -- with one critical exception.

Restaurants and retail food establishments are exempt from the Transformation CTE for foods they do not ship (Source: 21 CFR 1.1350(c)). Cooking fresh salmon into a dish, chopping romaine for a salad, or combining FTL ingredients into a menu item are not tracked transformations because the food is sold directly to consumers.

The exception: commissaries and central kitchens.

If a restaurant operates a commissary or central kitchen that transforms food and ships it to satellite locations, the commissary is treated as a food processor under FSMA 204. It must:

Record input KDEs for every FTL ingredient used
Assign new TLCs to transformed products
Record output KDEs for each batch produced
Maintain Shipping KDEs for each delivery to satellite locations
Link input TLCs to output TLCs

This is the key compliance escalation for multi-unit restaurant operators with central production.

What about kill steps?

If a processor applies a lethality treatment (kill step) that removes the food from its FTL form, the Transformation CTE still applies to the kill step event itself. However, downstream handlers of the post-kill-step food are exempt from further FSMA 204 traceability.

Example: Canning fresh tomatoes removes them from the FTL (the canned product is no longer "fresh tomatoes"). The canning processor records the transformation, but the distributor shipping canned tomatoes does not need Shipping CTE records for that product.

What other CTEs do processors perform?

Food processors typically perform multiple CTEs, not just Transformation:

| CTE | When It Applies | |-----|-----------------| | Receiving | For every FTL food received from suppliers | | Transformation | When manufacturing, processing, or commingling | | Shipping | For every FTL food shipped to distributors, retailers, or restaurants | | Initial Packing | If the processor is the first to pack a RAC | | Cooling | If the processor cools RACs before packing |

This makes processors the most compliance-burdened entities under FSMA 204.

How long must Transformation CTE records be kept?

All Transformation CTE records must be retained for 2 years (24 months) from the date created (Source: 21 CFR 1.1455). Given the complexity of input-to-output linking and the potential for dozens of input lots per transformation, electronic record systems are effectively required for processors of any meaningful scale.