· 2 min read · FoodChainAPI editorial
FSMA 204 Transformation Records: Link Inputs to Output Lots
Transformation traceability requires a connection between the food used in an operation and the food produced by it. A final batch number without its input relationships cannot support a useful backward trace.
Decide which activity occurred
Compare your operation with FDA's transformation definition and examples before mapping records. Processing, commingling, repacking, and relabeling can raise transformation questions. Moving sealed cases between storage positions is not the same operation as turning ingredients into a new product.
Document the activity, the product before and after it, and the applicable FTL forms and exemptions. FDA's guidance explains when a new TLC is assigned. Do not infer the event solely because your ERP created a new inventory ID.
Represent a many-to-many relationship
A production run may use two lots of leafy greens and produce several output lots. Model a transformation event with input allocations and output allocations. Retain original input TLCs and source identities alongside the output TLC and assigning location.
Include rework explicitly. If material from an earlier batch enters a later run, preserve that relationship rather than describing it as an anonymous ingredient. Your software should be able to follow the chain across several production steps without losing the source lots.
event: transformation-042
inputs: greens-lot-A, greens-lot-B
outputs: salad-lot-C, salad-lot-D
reference: production-record-042Test both directions
Start with one supplier lot and identify all output lots that consumed it. Then start with one finished lot and identify all input lots. Include a split run, mixed lots, and rework in your test data. Missing edges are a more serious problem than an unattractive batch screen.
FoodChainAPI can support the product-category review before you design this workflow. It does not infer manufacturing genealogy from a recipe. Obtain the actual lot allocations from production records and verify the applicability of each event against FDA's current requirements.
Put the product review into practice
Start with a candidate category in the free FTL lookup. Check product form and exemptions against FDA sources, then save the evidence behind your decision.
API referenceUse in Chrome, ChatGPT, or ClaudeProduct review walkthrough
Sources and scope
FDA sources checked October 4, 2026. Workflow suggestions are implementation guidance; category matches do not establish exemption or compliance status. Check the current FDA requirements for your product and activities.