FSMA 204 Readiness: From Listed Foods to FDA Records Requests

Status as of October 26, 2026: FDA identifies January 20, 2026 as the original compliance date. FDA proposed extending that date by 30 months to July 20, 2028. Separately, Congress directed FDA not to enforce the Food Traceability Rule before July 20, 2028, and FDA says it intends to comply. The proposed extension and the Congressional enforcement direction are not the same legal action; do not describe the proposal as a finalized extension.

Use FDA’s rule page to recheck status before setting a project date. In the meantime, organize readiness around evidence: scope decisions, event records, partner handoffs and a records-request exercise—not a presumed final extension or a promised software capability.

Under § 1.1300, Subpart S applies, except as otherwise specified, to persons who manufacture, process, pack or hold foods on the Food Traceability List. This is not an all-food requirement. This guide addresses FDA-regulated human-food operations; it is not a universal framework for drugs, USDA-regulated operations, juice, seafood, dietary supplements or animal food.

The same-form condition matters. Section 1.1310 states: “The term ‘Food Traceability List’ includes both the foods specifically listed and foods that contain listed foods as ingredients, provided that the listed food that is used as an ingredient remains in the same form (e.g., fresh) in which it appears on the list.” Assess the actual food and ingredient form, not just an ingredient name or a purchasing category.

A kill step is defined as lethality processing that significantly minimizes pathogens in a food. Do not infer a qualifying kill step from repacking, chilling, a supplier assurance without supporting context, or this guide’s example. The exercise below stipulates listed-food scope and no exemption; it provides no safety recipe or process limits.

Keep a short scope register: product and form, activity, applicable paragraph, supporting record location, decision owner and unresolved questions. Treat this register as a practical aid to the required traceability-plan procedure for identifying listed foods, not as a substitute for reviewing the actual exemptions.

Keep these identifiers separate

• A TLC uniquely identifies a traceability lot within the records of its TLC source. It is not necessarily globally unique.
• The TLC source is the place where the code was assigned. The immediate supplier may instead be a distributor that did not assign it.
• A supplier’s printed lot code may be the TLC, but confirm its meaning. An invoice number, internal receipt ID or inventory lot is not automatically the TLC.
• A TLC-source reference is an alternative way for FDA to access the source’s location description—not an unexplained internal alias.
• A location description contains the business name, phone number, physical address or geographic coordinates, and the specified city, state and postal information, with comparable foreign-location information including country. A GLN is not a universally mandated substitute.
• Product descriptions include the product name, including brand, commodity and variety if applicable, plus packaging size and style. A SKU alone needs a resolvable description.

For the three event types above, the rule specifies receipt date, shipping date and transformation-completion date—not a universal event-time field. Keep time-of-day or a GLN when useful to your operation, but label them as additional fields rather than universal KDEs.

When to assign—and when not to replace—a TLC

Section 1.1320 requires assignment at initial packing of the specified raw agricultural commodities, first land-based receiving of food from a fishing vessel, and transformation. Except where otherwise specified, it prohibits a new TLC for other activities, such as shipping. Routine receiving, an unchanged inventory allocation or an unchanged shipment is not permission to replace the existing TLC.

One express exception is § 1.1345(b): when receiving from a person to whom Subpart S does not apply, the receiving provision requires assignment if a TLC has not already been assigned, except for retail food establishments and restaurants. Do not use that exception merely because a covered supplier’s information is missing. Repacking or relabeling can be transformation when the output is an FTL food; document what actually happened.

This fictional exercise follows Cedar Deli Works, a ready-to-eat deli-salad processor, using records dated October 20–23, 2026. Both incoming salads and all outputs are stipulated to be FTL foods; no food, person, transaction or spreadsheet-form exemption applies. The example concerns records only, not whether a formulation or handling process is safe. All business details are invented.

Cedar receives 120 kg from North Kitchen and 80 kg through Harbor Distribution. Both suppliers identify the incoming TLC as 042. North Kitchen’s code-assignment location is documented. Harbor’s delivery identifies the distributor but does not establish the place that assigned its TLC. Cedar preserves separate local receipt and inventory IDs while leaving that source gap unresolved.

The keys in these tables expand through the location and product dictionaries; they do not replace the required descriptions. UNRESOLVED and MISSING are visible issue markers, not valid substitutes for required information. RA-201 and RB-202 prevent the local records from collapsing into one row, but they do not cure RB-202’s missing TLC source. Do not manufacture the identity DB + 042 by assuming the distributor assigned the code.

Cedar’s production ledger records two transformation runs with different input contributions. T1 uses 70 kg from RA-201 and 30 kg from RB-202. T2 uses 30 kg from each receipt. T3 later repacks 48 kg of T1’s output. The remaining 48 kg of T1’s output stays in its existing packaging; allocating those unchanged tubs between shipment and hold does not create a replacement TLC.

These are the actual immediate-input contributions to each output in the exercise ledger. CD-R links to CD-A, and CD-A links to both incoming lots. That ancestry does not mean all 70 kg and 30 kg charged to T1 went into CD-R. Do not invent an exact supplier-by-supplier mass allocation to each finished tub when the records only support the documented intermediate-lot link.

Reconciliation is a useful control, not an extra universal KDE list

The input quantities used and output quantities produced above are transformation KDEs. The sample, waste, held and unused buckets below are additional site records used to explain the physical balance. They do not replace those KDEs, establish a research-use exemption, demonstrate product safety or authorize release.

The pack counts also reconcile: CD-A is eight 12 kg tubs, four of which enter repacking; three unchanged tubs ship and one is held. CD-B is twenty-nine 2 kg tubs: twenty ship and nine are held. CD-R is forty-six 1 kg tubs: thirty ship and sixteen are held. Passing these arithmetic checks does not resolve missing source information or prove that a spreadsheet joins correctly.

For these covered shipments, § 1.1340(b) requires providing the TLC, quantity and unit, product description, recipient location, ship-from location, shipping date, and TLC-source location or source reference to the immediate subsequent recipient other than a transporter. Electronic, paper or another written form can be used. Keep the shipping reference document type and number; sharing them too is a useful local join aid, although they are not included in the handoff list in (b).

Cedar’s handoff design pairs each shipment record with the expanded product and location descriptions. The shipping coordinator owns delivery of that information; the receiving partner is asked to confirm that it can preserve the TLC and source without relabeling them as its own receipt number. Retain a copy of what was sent and any correction as site evidence. A transmitted message alone does not establish that the recipient interpreted it correctly.

Section 1.1455(c)(1) requires records to be available to an authorized FDA representative on request within 24 hours, or within a reasonable time FDA agrees to, together with information needed to understand them. This is a records-availability requirement, not a universal deadline to complete a recall.

The electronic sortable spreadsheet requirement in § 1.1455(c)(3)(ii) applies to requested CTE information under §§ 1.1325–1.1350 in the public-health circumstances described in (c)(3), subject to exceptions. Those circumstances include helping prevent or mitigate an outbreak, assisting implementation of a recall, or otherwise addressing a public-health threat. It is not a requirement to submit every event automatically to FDA.

Specified small farms, retail food establishments/restaurants and other persons can provide another form under the rolling three-year, inflation-adjusted criteria in § 1.1455(c)(3)(iii). These are spreadsheet-form exceptions, not a blanket removal of recordkeeping duties. FDA also provides for withdrawing a spreadsheet request as appropriate to accommodate a religious belief under (iv). This exercise stipulates that none of those form exceptions applies.

Exercise request and candidate workbook

Continue the Cedar exercise with a simulated authorized FDA public-health records request received October 26, 2026 at 09:00 Eastern, covering the listed salad handled October 20–23. No additional response time is assumed. Cedar logs a response due time of October 27 at 09:00 Eastern. This request-log time is administrative exercise information, not a universal time-of-day KDE for receiving or shipping.

The records coordinator assembles a candidate sortable workbook with Receiving, TransformationOutputs, TransformationInputs, Shipping, Locations, Products, FieldMap and Issues sheets. The tables above are its sample business rows and dictionaries. The following mapping defines the fields; it is a local workbook design, not a prescribed FDA template or evidence that FDA has accepted a response.

The workbook’s FieldMap explains that PC expands to Cedar ready-to-eat deli salad, 12 kg lidded bulk tub, and that P expands to Cedar’s full location description. Before any actual response, resolve and include the relevant descriptions or valid source references so an external reviewer does not need access to the plant application. Keep quantities numeric, units explicit, dates consistently represented and TLCs as text so 042 retains its leading zero.

The extracted file fails even though the ledger balances

The exercise disposition is OPEN—not verified, validated or ready for an unqualified completeness statement. A 200 kg balance and a working screen inside an application do not prove the external file’s identity, completeness or interpretability. No correction in this table is treated as completed.

1. Open the candidate file outside the source application and inspect the actual rows, column types and dictionaries.
2. Check every required field against the event mapping and source documents, including completion dates, packaging descriptions, partner locations and TLC sources.
3. Test each input-to-output and event-to-location join for missing and multiple matches. Test the colliding 042 codes explicitly.
4. Record the file version, scope, reviewer, observed result and unresolved issue owner. Keep failed rows visible rather than excluding them from totals or the request scope.
5. For a real request, the designated contact manages timely provision of the requested records and explains unresolved gaps; it does not silently extend the response window while waiting for a perfect file. Only FDA-agreed additional time changes the stated alternative.

Section 1.1315 requires a covered person’s traceability plan to describe recordkeeping procedures, including record format and location; how listed foods are identified; how TLCs are assigned, if applicable; and a point of contact for plan and record questions. Update the plan as needed to reflect current practices and retain the previous plan for two years after an update.

Under § 1.1455, records may be original paper or electronic records or true copies; they must be legible and protected against deterioration or loss. Except where Subpart S specifies otherwise, retain required information for two years from creation or receipt. Existing records can be supplemented instead of duplicated, and the information can be in multiple record sets if the plan identifies their formats and locations.

Another entity may establish and maintain records for you, but you remain responsible for ensuring they can be retrieved and provided onsite within 24 hours of a request for official review. Offsite storage is allowed on that retrieval basis; electronic records accessible onsite are considered onsite. A partner portal, service contract or system connection is therefore not, by itself, evidence that retrieval works.

The role assignments and folder paths above are site-practice examples. Test access with the people who would answer a request, including when the primary contact is absent. Keep the statutory retention rule separate from any longer retention chosen for other applicable obligations or business needs.

1. Confirm each food/form and covered activity. Record the exemption basis where one is used; do not start with an all-food software flag.
2. Map receiving, transformation and shipping separately. Identify where the supplier, physical location, TLC source and internal lot are currently conflated.
3. Build the traceability plan, dictionaries and reference-document links before depending on an export.
4. Agree a written partner handoff and test it with a code collision, a repack and an incomplete location record—not just a clean demonstration lot.
5. Rehearse a scoped records request. Inspect the actual external file and keep every failed join or missing KDE assigned to an owner.
6. Repeat affected checks after corrections or material changes to products, event mapping, partners or record systems. Close an issue only when the correction evidence and retest result are retained.

Keep this project’s boundary clear. Use lot genealogy for broader relationship concepts, ingredient traceability for ingredient-level operating design, and the recall management plan guide for recall execution. This guide’s evidence gate is narrower: can the covered event records and required partner information be retrieved and understood, with unresolved deficiencies visible?