← All Posts
Guide April 16, 2026 · Guidance Team

FSMA 204: Key Data Elements You Must Capture

The FDA's FSMA 204 rule isn't optional for many food brands. If you're running a co-packed organic food brand, especially with international sourcing, you know the data demands are real. This post cuts through the noise. We'll outline the exact Key Data Elements (KDEs) required at each Critical Tracking Event (CTE), so you can prepare your systems. By the end, you'll have a concrete checklist for compliance, moving beyond guesswork.

Key Takeaways

Receiving Ingredients: Your First Data Point

When your co-packer or facility takes possession of raw materials, that's a 'Receiving' CTE. This event kicks off your traceability chain. You must capture the Traceability Lot Code (TLC) for the received product, its product description (e.g., 'Organic Frozen Blueberries'), the quantity and unit of measure (e.g., '1,000 lbs'), and the date it was received. Critically, you also need the name of the entity that shipped it to you, and their TLC for that specific shipment. For example, if you get a pallet of organic sugar, lot #SUG-20240115, from 'Sweet Farms Inc.', on February 1, 2024, those are your core data points. Don't just rely on a bill of lading; verify and record these details as a distinct traceability event. This foundational data ensures you can connect the raw material back to its origin quickly if needed.

Manufacturing Transformation: New Lot, New Data

A 'Transformation' CTE occurs whenever a food product changes its form or combines with other ingredients to create a new product, or even a new lot of an existing product. Think of blending multiple ingredient lots to make a sauce, or repacking a bulk ingredient into smaller bags. For this, you need the new TLC of the transformed product, its description, quantity, and unit of measure, plus the date of transformation. You also need the TLCs of *all* the ingredients that went into this new lot. If you combine Lot A of blueberries and Lot B of apples to make a fruit blend Lot C, you must record A and B's TLCs as inputs for C. This is where many brands fall short with spreadsheets, as accurately linking multiple input lots to a single output lot becomes complex and error-prone very fast.

Finished Goods Creation: The Product's Birth Certificate

This is often the final 'Transformation' event where your finished product receives its unique lot code, ready for sale. The KDEs here are similar to a general transformation, but specifically for your final consumer-facing product. You need the finished product's TLC, its full product description (e.g., 'Organic Blueberry Apple Sauce, 16oz'), the total quantity produced (e.g., '5,000 units'), and the date of production. You must also record the TLCs of all the immediate ingredients or intermediate products that went into making this finished good lot. For example, if your sauce lot #SAUCE-20240210 was made using fruit blend Lot C and sugar lot #SUG-20240115, both C and #SUG-20240115 become KDEs associated with #SAUCE-20240210. This is the critical juncture for connecting your raw material traceability to your outbound shipments.

Shipping Your Product: Hand-off Documentation

When your finished goods leave your co-packer's dock or your warehouse, that's a 'Shipping' CTE. You need to document this meticulously. The required KDEs include the TLCs of the shipped product (your finished goods), the quantity and unit of measure (e.g., '200 cases'), and the date shipped. You also need the name of the entity who *received* the product (e.g., 'Whole Foods Distribution Center'), and their specific TLC for that product if they assign one at receipt. Additionally, capture the location description of the shipping entity (your co-packer's address) and the location description of the receiving entity (the DC's address). This establishes a clear chain of custody, proving where your product went and when it arrived at the next control point.

Receiving by the Next Step: Closing the Loop

While you are the 'shipper' in the previous CTE, your product will be 'received' by another entity in the supply chain – typically a distribution center, retailer, or direct customer. Although you aren't directly performing this 'Receiving' CTE, you are responsible for ensuring the *data* associated with it is captured and made available. This includes the TLC of the received product, its description, quantity, unit of measure, and the date received by the next entity. You also need the name of the entity that *shipped* it to them (which is you or your co-packer), and the TLC they used for that shipment. This data helps close the gap in the supply chain, providing a complete picture of your product's journey from ingredient to consumer shelf. Many brands use EDI or direct data exchanges to get this back from partners.

Guidance for Data Management: Beyond Spreadsheets

Capturing these KDEs accurately and consistently across multiple CTEs requires more than just spreadsheets. When you're managing co-packers, multiple ingredient suppliers, and various finished goods SKUs, manual data entry becomes a compliance risk. A system like Guidance automates the capture of these KDEs at each stage. For example, when a PO for organic fruit is received, the system logs the supplier's lot code and quantity. When that fruit goes into a production run, Guidance automatically links the ingredient lot codes to the new finished goods lot codes, generating the necessary transformation data. This ensures your lot traceability is end-to-end and FSMA 204 compliant, without manual reconciliation. It's about having a single source of truth that updates in real-time, giving you control and audit readiness.

See How Guidance Handles This

Guidance is a CPG operations platform built by the CEO of Claros Farm. Apply to join the design partner program.

Apply as a Design Partner →

Frequently Asked Questions

What if my co-packer doesn't currently capture all required KDEs?

You are ultimately responsible for FSMA 204 compliance, even if you use a co-packer. You need to work with your co-packer to ensure they understand and capture all required KDEs for your products. This might involve updating your co-packing agreement, providing them with training, or implementing a system that facilitates their data capture and transfer to you. Treat them as an extension of your operations for traceability purposes.

Do I need to track *all* ingredients for FSMA 204?

No, FSMA 204 applies to specific foods on the Food Traceability List (FTL). You must track ingredients on the FTL, as well as any foods that contain an FTL food as an ingredient. For example, if your fruit smoothie contains organic mango (which is on the FTL), then your smoothie product itself falls under the rule, and you must track the mango ingredient and the finished smoothie. Non-FTL ingredients do not require full FSMA 204 tracking.

How long do I need to keep this traceability data?

You must maintain all required FSMA 204 records for two years after the date of creation of the record. This applies to all Key Data Elements and Critical Tracking Event information. These records must be readily available to the FDA upon request. Having a digital system that securely stores and archives this data automatically is far more reliable than managing physical files or fragmented spreadsheets.

What's the biggest mistake food brands make with FSMA 204 compliance?

The biggest mistake is underestimating the granular data requirements and delaying implementation. Many brands try to adapt existing, often manual, systems like spreadsheets or basic ERPs, which are not designed for lot-level, end-to-end traceability. This leads to incomplete data, inconsistent formats, and an inability to respond quickly during an audit or recall. The complexity of linking multiple input lots to output lots, especially with co-packers, is consistently a bottleneck.