FSMA 204 Education Series

A free, six-module training series on the FDA Food Traceability Rule and the Produce Traceability Initiative.

The FSMA 204 Education Series is a free training program from the International Fresh Produce Association that walks the fresh produce supply chain through what the FDA Food Traceability Rule requires, who it applies to, and how to prepare. Six modules move beyond the regulation into practical implementation: identifying your covered products, traceability lot codes, labeling, and building a compliance plan.

Watch in order or jump to the module you need. Full transcripts are provided for every module. No registration required.

START MODULE 1 NOW

READINESS SELF-ASSESSMENT

THE SERIES AT A GLANCE

Six modules, free to watch, no registration required.
Full written transcripts published for every module.
Covers the FDA Food Traceability Rule (FSMA Section 204) and the Produce Traceability Initiative (PTI).
All covered entities share a single compliance date of July 20, 2028 — FDA set one date across the supply chain because traceability only works when information flows between trading partners.
Applies to foods on the Food Traceability List, including leafy greens, tomatoes, peppers, melons, herbs, and certain fresh-cut fruits and vegetables.
Taught by Erik Larsen, Director of Supply Chain, IFPA.

THE LEARNING PATH

Run time: 6 minutes 14 seconds

Module 1 — Understanding FSMA 204

What you will learn: Why FSMA 204 was created and how it shortens foodborne illness investigations; which foods appear on the Food Traceability List; how the Produce Traceability Initiative relates to the rule; and why the July 20, 2028 compliance date means preparation should begin now.

Module 1 — Understanding FSMA 204: Full Transcript

Welcome to our FSMA 204 and Produce Traceability Initiative Education Series. Over the next six modules, we'll walk through the Produce Traceability Initiative and what FSMA 204 is, who it effects, and, most importantly, what organizations need to do now to prepare for compliance. Our goal is to move beyond understanding the regulation and focus on practical implementation strategies that help you build a successful traceability program.

What this module covers

This first module sets the foundation. We are not trying to cover every implementation detail here. Instead, we are defining the rule, the foods it applies to, the role of PTI, and the compliance timeline so learners are ready for the later modules on concepts, applicability, readiness, trading partner collaboration, and implementation.

What FSMA 204 requires

FSMA 204 is a federal traceability rule that establishes additional recordkeeping requirements for certain foods. At the core of the rule are records containing Key Data Elements associated with Critical Tracking Events. In other words, the rule is focused on making sure the right data is captured at the right moments so products can be traced quicker and accurately during food safety investigations.

Why the rule exists

FSMA 204 was established to improve the speed and accuracy of food tracebacks during foodborne illness investigations. Historically, tracing a contaminated product through the supply chain could take days or weeks. During that time, companies often had little choice but to recall broad categories of product because they could not quickly identify the source. The rule is designed to make traceability records more consistent and accessible, enabling faster investigations, more targeted recalls, improved consumer protection, and reduced food waste.

The benefits of stronger traceability

Stronger traceability enables faster traceback, more precise recalls, improved consumer protection, and reduced food waste. It also helps organizations prepare internally by aligning data, systems, and trading partner expectations. The practical takeaway is that FSMA 204 is not only a compliance requirement. It is also a push toward better, more usable traceability information across the supply chain.

Which foods are covered

FSMA 204 applies to foods included on the Food Traceability List, also known as the FTL. For the produce industry, examples include leafy greens, tomatoes, peppers, melons, herbs, and certain fresh-cut fruits and vegetables. The first practical step is to understand exactly which foods your organization handles and whether those foods are covered.

Which activities are covered

The Food Traceability List is only one part of the question. Applicability also depends on the activities your organization performs. If your organization grows, packs, transforms, ships, receives, or holds covered foods, portions of the rule may apply depending on the specific activity. Later modules will help clarify applicability in more detail.

The role of the Produce Traceability Initiative (PTI)

The Produce Traceability Initiative, or PTI, is an industry effort that supports standardized traceability practices. PTI is not a regulation and does not replace FSMA 204. However, it can help organizations operationalize traceability through common labeling, identifiers, and data-sharing approaches that are already familiar across much of the produce industry.

How FSMA 204 and PTI relate

FSMA 204 and PTI serve different but related purposes. FSMA 204 defines the regulatory requirements. PTI provides practical industry tools that can help organizations implement traceability more consistently. PTI can support readiness through standardized case labels, GS1 identifiers, barcodes, and shared expectations, but each organization remains responsible for evaluating and meeting its own FSMA 204 obligations.

The compliance deadline: July 20, 2028

One of the most important things to remember is that all covered entities share the same compliance deadline: July 20, 2028. FDA intentionally established one implementation date across the supply chain because traceability only works when information flows seamlessly from one trading partner to another. While 2028 may feel far away, preparation requires process changes, technology decisions, training, and supply chain coordination.

Getting started on readiness

The practical next step after Module 1 is to begin thinking about readiness. Identify which FTL foods your organization handles, map the activities you perform, determine who owns traceability work, review where traceability data lives, engage trading partners early, and use the IFPA self-assessment to score current-state readiness with evidence.

Knowledge check

Let's pause for a quick check. Which statement best describes the first step toward FSMA 204 readiness?

The best answer is B: identify the foods you handle and the activities you perform. This is the foundation for every other traceability readiness activity. You cannot build a strong plan, map CTEs, collect KDEs, or coordinate with partners until you know which products and processes are in scope.

Module 1 summary

Before we wrap up Module 1, let's review what we covered. We introduced what FSMA 204 is, why faster traceability matters, examples of foods on the Food Traceability List, the role of the Produce Traceability Initiative, the July 20, 2028 compliance deadline, and what organizations should begin thinking about now.

What to do next

After this module, start with a short readiness conversation. Review which products you handle, map the activities your organization performs, identify the teams that need to be involved, and begin gathering evidence of the records and systems you use today.

In Module 2, we will build on this foundation by introducing TLCs, CTEs, and KDEs. We thank you for watching our Module 1, Understanding FSMA 204! Please proceed to Module 2, Core Traceability Concepts.

Run time: 4 minutes 7 seconds

Module 2 — Core Traceability Concepts

What you will learn: The core concepts that drive FSMA 204 compliance — Critical Tracking Events, Key Data Elements, and Traceability Lot Codes.

Module 2 — Core Traceability Concepts: Full Transcript

Welcome back to our FSMA 204 and Produce Traceability Initiative education series. In Module 2, we'll walk through the Core Traceability Concepts that form the foundation of the rule.

The core traceability framework

The core traceability concepts are identified as Traceability Lot Codes, Critical Tracking Events, and Key Data Elements. Understanding these three concepts is essential because they define how traceability works in practice and how information moves through the supply chain.

Together, Traceability Lot Codes, Critical Tracking Events, and Key Data Elements create a system that allows products to be traced quickly and accurately through the supply chain. You can think of this as a simple framework: the lot code identifies the product, tracking events define when data must be captured, and data elements define what information must be recorded.

Traceability Lot Codes (TLC)

A Traceability Lot Code, or TLC, is the unique identifier that follows a product through the supply chain. It connects all traceability records back to the point where the product was first packed or created. In most cases, the TLC is assigned during initial packing and may be updated if the product is transformed, such as when it is cut, mixed, or repacked. The most important thing to understand is that the TLC is what ties everything together. Without it, traceability data cannot be connected across different supply chain steps.

Take a look at this example Traceability Lot Code label used to link product movement and support traceback.

Critical Tracking Events (CTE)

Critical Tracking Events, or CTEs, are the specific points in the supply chain where traceability data must be captured. These include activities such as harvesting, cooling, packing, shipping, receiving, and transformation. Not every company performs every event—but every company is responsible for capturing data at the events they do perform. These events create the structure of traceability by defining when information must be recorded.

Key Data Elements (KDE)

Key Data Elements, or KDEs, are the actual data points that must be recorded at each Critical Tracking Event. These include information such as lot codes, product descriptions, dates, locations, quantities, and reference documents. Think of KDEs as the details that bring traceability to life.

Actually, the KDEs communicated on a typical Bill of Lading today cover about 90% of these new requirements. They provide the information needed to trace a product both forward and backward through the supply chain.

How TLCs, CTEs, and KDEs work together

Now that we've defined each concept, it's important to understand how they work together. The Traceability Lot Code identifies the product. Critical Tracking Events define when data must be captured. And Key Data Elements define what data must be recorded at those moments. Together, they form a complete traceability system that allows regulators and companies to track products quickly and accurately during an investigation.

Operational impact across your organization

Understanding these concepts is not just about compliance—it directly impacts how your organization operates. Your teams will need to consistently assign lot codes, capture data at the right moments, and ensure that information is accurate and accessible. This often involves coordination across operations, food safety, IT, and supply chain partners. Getting these fundamentals right is the first step toward building a compliant and effective traceability program.

Module 2 summary

In this module, we've introduced the three core concepts that drive FSMA 204: Traceability Lot Codes, Critical Tracking Events, and Key Data Elements. These concepts form the foundation of traceability and will be referenced throughout the rest of the modules.

What's next

In the next module, we'll explore who the rule applies to and how to determine whether your organization is covered. Thank you for watching Module 2, Core Traceability Concepts! Please proceed to Module 3, Does the Rule Apply to You

Run time: 4 minutes 22 seconds

Module 3 — Does the Rule Apply to You

What you will learn: How to determine whether FSMA 204 applies to your organization or not.

Module 3 — Does the Rule Apply to You: Full Transcript

Welcome back to our FSMA 204 and Produce Traceability Initiative education series. In module 3, we’ll focus on how to determine whether FSMA 204 applies to your organization or not. Please note, this video is not meant to help you make a final legal determination on if you are covered or not, but to help you understand the factors your team should evaluate as you prepare for compliance.

Core criteria: Foods and activities

Coverage depends on two core questions: whether your organization handles foods on the Food Traceability List, and which activities your organization performs in the supply chain.

The first, determine whether your organization handles foods on the FTL. You can find the foods on the FTL on the FDA's website. If your product is on this list, the next step is to identify which activities you perform. FSMA 204 applies across the supply chain, but responsibilities can vary depending on whether you grow, pack, ship, receive, transform, or hold covered foods. Organizations should document this review, because applicability is not just about the company as a whole. It can depend on specific products, facilities, and processes.

Supply chain traceability in practice: The tomato example

Once you've determined that you handle a food on the FTL and identified your activities, the next step is understanding where traceability requirements occur throughout the supply chain.

This example - as depicted in the Produce Traceability Initiative FSMA 204 Implementation Guidance document - follows tomatoes as they move from harvest through packing, repacking, distribution, and ultimately to retail or foodservice locations.

Notice that each organization performs different activities and is responsible for different Critical Tracking Events, or CTEs. As the product moves and changes hands, traceability information must be captured and maintained to preserve the connection to the traceability lot code.

Activity-based compliance across covered entities

This illustrates an important principle of FSMA 204: compliance is based on the activities you perform. Each entity is responsible for documenting the required information for the Critical Tracking Events under its control.

Covered entities may include many different parts of the produce supply chain, such as growers, packers, distributors, repackers, retail distribution centers, foodservice operations, commissaries, warehouses, and cold storage operations. The key point is that FSMA 204 is activity-based. Your organization may have different obligations depending on what it does with covered foods. This is why a cross-functional review is important before assuming whether the rule does or does not apply.

Exemptions and partial exemptions

Some organizations may qualify for exemptions or partial exemptions, but those should be evaluated carefully. Examples to review include retail food establishments and restaurants, kill-step exemptions for processed products, certain farm-to-consumer activities, very small farms, and partial exemptions based on activity type.

Module 3 summary

As we conclude Module 3, remember that determining applicability starts with understanding the foods your organization handles and the activities your organization performs. FSMA 204 applies to specific foods on the Food Traceability List and certain activities that occur throughout the supply chain. We also reviewed how exemptions and partial exemptions may affect requirements in some situations. The most important takeaway is that applicability should be based on documented facts and evidence, creating a clear understanding of what requirements may apply to your organization. With that foundation in place, you're ready to begin planning for implementation and traceability readiness.

Action items and readiness

Before moving forward, start applying Module 3 to your own organization. Identify which Food Traceability List foods your organization handles, map the activities your organization performs, and review whether any exemptions or partial exemptions may apply.

Then, use the IFPA FSMA 204 Self-Assessment tool available to IFPA members to document what evidence you have, where applicability is clear, and where additional review may be needed. This step helps turn applicability from a regulatory question into a practical readiness activity.

What's next

We thank you for watching Module 3, Does the Rule Apply to You. Please proceed to Module 4, Building your FSMA 204 Program.

Run time: 7 minutes 42 seconds

Module 4 — Building Your FSMA 204 Program

What you will learn: How to move from understanding the rule to building a practical readiness program.

Module 4 — Building Your FSMA 204 Program: Full Transcript

Welcome to Module 4, Building Your FSMA 204 Program, of the FSMA 204 and Produce Traceability Initiative education series. In this module, we’ll move from understanding the rule to building a practical readiness program. We’ll look at gap assessment, traceability planning, cross-functional ownership, technology readiness, and how to use the IFPA FSMA 204 Self-Assessment to identify evidence, score readiness, and prioritize remediation.

Scoring readiness with evidence

The IFPA Self-Assessment asks organizations to score each readiness area from zero to five. A zero means the work has not started. A five means the process is operationally proven. The important point is that scores should be based on actual evidence, not intent. If evidence cannot be produced, teams should score conservatively and document the gap, owner, target date, and remediation action.

Conducting an operational gap assessment

The next step is conducting a gap assessment. This means comparing your current processes against what FSMA 204 requires. Can you trace products by lot? Can you link incoming and outgoing products? Can you retrieve information quickly? Can you generate a sortable spreadsheet if FDA requests records? A gap assessment helps identify where improvements are needed and creates a roadmap for implementation.

As you work through this section, use IFPA's Self-Assessment tool, available to IFPA members, to score your current state and identify the evidence you can produce.

A useful gap assessment starts with practical operational questions. Do you capture GTIN's and lot numbers? Is your inventory actually tied to lots? Where does your traceability data live: paper logs, ERP, WMS, spreadsheets, or vendor portals? How do you exchange information with partners? And if asked by FDA, could you produce a sortable spreadsheet within 24 hours with the required fields? These questions should be answered with evidence, not assumptions.

Developing your traceability plan

Every covered organization must maintain a traceability plan. Your plan should document how records are maintained, how covered foods are identified, how Traceability Lot Codes are assigned, who serves as the point of contact, and, when applicable, information about growing areas and farm maps. A well-designed traceability plan serves as both a compliance document and an operational guide. In the self-assessment, plan-related questions help teams determine whether the plan is documented, current, and supported by evidence.

Translating CTEs and KDEs into repeatable procedures

A strong program turns Critical Tracking Events and Key Data Elements into repeatable procedures. For each event your organization performs, you need to know which data is required, where it is captured, which system holds it, and how it can be retrieved. This is also where the self-assessment becomes useful. It asks whether each process is designed to capture required KDEs and whether each field is testable in system records.

Recordkeeping and 24-hour response capability

FSMA 204 readiness includes recordkeeping and response capability. Organizations must keep records for at least two years, maintain them in a way that supports retrieval, and be able to provide requested information to FDA within 24 hours or another reasonable time agreed to by FDA. In practice, that means testing whether you can produce lot-level KDE records, shipment and receiving data, transformation data, lot genealogy, and a sortable spreadsheet. The self-assessment asks teams to verify this with evidence such as mock recall outputs and report exports.

Cross-functional ownership and governance

Successful implementation requires collaboration across multiple functions. Food safety teams often lead regulatory interpretation and program oversight. Operations teams execute processes and capture data. Information technology teams support systems and reporting. Supply chain teams coordinate with trading partners. And training teams help prepare employees for new responsibilities.

Traceability is not owned by one department. It requires organizational alignment. In the self-assessment, governance questions ask whether this ownership is documented and actively managed.

Technology evaluation and systems integration

FSMA 204 does not prescribe a specific technology solution. However, organizations must evaluate whether their systems can support compliance requirements. This includes the ability to capture data, maintain lot-level information, retrieve records efficiently, and produce requested information in a usable format. Technology should enable compliance, not complicate it. The self-assessment helps teams evaluate whether ERP, WMS, labeling, EDI, master data, and reporting systems are integrated sufficiently to reduce errors and avoid duplicate entry.

Trading partner collaboration and supplier onboarding

FSMA 204 readiness depends on trading partner readiness. Suppliers may need to provide required attributes electronically, through ASN transactions, through GS1 labels, or through other agreed processes. Receiving teams need procedures for when data is missing, incomplete, or unreadable. The self-assessment includes supplier education, EDI onboarding, audit, corrective action, and supplier performance questions so teams can prioritize partner readiness work before it becomes an operational blocker.

Testing the chain: Product journey traceback

A simple product journey can help teams test readiness. For example, the record chain for whole tomatoes may begin with harvest data from Field A, move through cooling, then initial packing where a Traceability Lot Code is assigned and PTI case labels are printed. Shipping records, ASNs, receiving logs, transformation records, and downstream distribution records should all connect. The goal is to ensure FDA or your organization can trace back from a downstream product to the relevant source data quickly and accurately.

Turning assessment into a remediation roadmap

The self-assessment becomes most valuable when it leads to action. After scoring the current state, teams should collect evidence, document gaps, assign owners, identify dependencies, set target dates, and validate remediation. This turns the assessment into a continuous improvement roadmap rather than a one-time exercise. High-risk gaps, especially items scored zero through two, should be prioritized for remediation planning.

Module 4 summary

Let’s summarize what we covered. In this module we focused on turning FSMA 204 knowledge into an implementation program. We reviewed how to conduct a gap assessment, build or update a traceability plan, translate CTEs and KDEs into procedures, define cross-functional ownership, evaluate technology and supplier readiness, and use the IFPA Self-Assessment to prioritize remediation activities.

Next steps: Complete your self-assessment

Now it is your turn to complete or revisit the IFPA FSMA 204 readiness Self-Assessment. Score each area using actual evidence, identify gaps, assign owners and target dates, and build a prioritized remediation plan. The goal is not to prove perfection. The goal is to understand your current state, gather evidence, and prioritize the work that moves your organization closer to FSMA 204 traceability readiness.

Thank you for watching Module 4, Building your FSMA 204 Program. Use IFPA's self-assessment as your next practical step. Revisit your scores, gather supporting evidence, and use the results to build a clear remediation roadmap for FSMA 204 traceability readiness.

Run time: 7 minutes 59 seconds

Module 5 — Working Across The Supply Chain

What you will learn: How traceability information moves through the supply chain, examine the role of common data standards and PTI practices, and discuss how organizations can work together to support accurate, consistent information sharing.

Module 5 — Working Across The Supply Chain: Full Transcript

Welcome to Module 5, Working Across The Supply Chain, of the FSMA 204 and Produce Traceability Initiative education series. In this module, we'll discuss how traceability information moves through the supply chain, examine the role of common data standards and PTI practices, and discuss how organizations can work together to support accurate, consistent information sharing. We'll also introduce ways to evaluate your current readiness and identify opportunities to strengthen traceability processes across your operation and supply chain partners. Let's get started.

Trading partner readiness is compliance readiness

One of the biggest implementation challenges is recognizing that your compliance depends on your trading partners’ readiness. You may have excellent internal processes, but if suppliers are unable to provide required information, or customers cannot receive it, gaps quickly emerge. Supplier onboarding, data-sharing expectations, consistent labeling practices, and exception management should become part of your implementation strategy. Use the self-assessment to evaluate supplier education, supplier policy, EDI onboarding, and audit or corrective action processes.

Product movement and data movement must stay connected. At each handoff, required data needs to remain connected to the Traceability Lot Code and relevant source information. The self-assessment can help teams test whether each receiving, transformation, shipping, and reporting process captures and retains the required data.

Tracking product and data movement: Tomato supply chain example

Let’s look at a simple example. Tomatoes are harvested from a field and moved to cooling. They are then packed into cases and assigned a Traceability Lot Code. Those cases are shipped to a distribution center and later received by a repacker. The repacker combines products and creates a new configuration, requiring a new Traceability Lot Code. At each step, Critical Tracking Events occur and Key Data Elements are recorded. This chain of information allows investigators to trace a product’s history quickly and accurately.

Common data standards: GS1 and PTI in produce

Data standards reduce ambiguity. Trading partners may use different systems, terminology, and documents, so standards create a common language for identifying products, locations, lots, logistics units, and shipment data. In the self-assessment, this connects to label design, systems integration, master data governance, and EDI readiness.

GS1 and PTI practices help provide a shared language. In produce traceability, teams often reference GTIN's for products, GLNs for locations, SSCCs for logistics units, GS1-128 or 2D barcodes for scanning, and ASN or EDI 856 for shipment data. PTI helps translate these standards into practical produce labeling and data-sharing practices. Visit produce traceability dot org for a full list of common identifiers and definitions.

The Produce Traceability Initiative is not a regulation. However, PTI standards closely align with FSMA 204 requirements and can significantly simplify implementation. PTI promotes standardized case labels, GTINs, lot identification, scanning, master data, and data-sharing practices that improve interoperability across the supply chain. Because PTI standards are widely adopted throughout the produce industry, many organizations are leveraging them as a practical pathway toward FSMA 204 readiness.

Traceability lot code sources and label integration

Traceability lot code sources are where food is assigned a traceability lot code, and that source information must be exchanged between trading partners all the way to the store or restaurant. In the self-assessment, teams should look for evidence such as lot genealogy reports, TLC source records, WMS or ERP lot master data, and shipment or receipt records.

Labels connect the physical product to digital records. Case labels help users identify product and lot-level data through human-readable and machine-readable fields. Pallet labels can use a Serialized Shipping Container Code, or SSCC, to link logistics-unit data to shipment information in the ASN. The self-assessment asks whether case and pallet labels support GS1-based scanning, human-readable fallback, and practical DC or production workflows.

EDI 856, ASNs, and receiving exception management

ASN and EDI 856 can reduce manual re-entry by delivering shipment and traceability attributes before the truck arrives. The self-assessment includes prompts for supplier ASN capability, GTIN matching, GLN usage, downstream system application before product arrival, and auditing shared ASN or barcode data against physical product.

The self-assessment includes several receiving prompts that focus on what happens when required attributes have not been provided electronically in advance of physical receipt. A strong process should notify the receiving team, support scanning or manual capture from GS1-128 or GS1 2D barcodes, and route unresolved issues through corrective action with the supplier.

Master data governance and cross-system alignment

External standards are only useful if internal systems and master data support them. Organizations should verify whether item, location, supplier, customer, lot, EDI, WMS, ERP, and reporting data are governed and aligned. The self-assessment specifically asks whether systems are integrated enough to reduce duplicate entry and whether GTIN, GLN, item, supplier, customer, facility, and lot-source data are governed with clear ownership.

Collaborative supplier onboarding and evidence-based scoring

Trading partner collaboration should operate like a readiness program. Teams should define data requirements, onboard suppliers and customers, test data exchange, audit data quality, manage exceptions through corrective action, and revisit requirements regularly. This connects directly to the self-assessment categories around supplier governance, EDI, audits, and change management.

The self-assessment is evidence based. Learners should score current readiness using actual documents, screenshots, system exports, labels, ASNs, BOL's, training records, mock recall outputs, audit results, and corrective action logs. If evidence cannot be produced, the score should be conservative and the gap should be documented.

Knowledge check

A practical way to test understanding is to ask yourself, "what evidence would prove trading partner data-sharing readiness? Supplier ASN test transactions, label samples, scan results, EDI maps, validation rules, onboarding materials, and exception logs all help prove readiness. The best answer is all of the above.

Module 5 summary

Before we wrap up, let’s summarize the key points. Your compliance depends on trading partner readiness. Product and data movement must stay connected. PTI and GS1 standards improve interoperability. Labels, ASN, EDI, and master data reduce manual gaps. Exceptions need documented corrective action and supplier follow-up. And the self-assessment turns these concepts into evidence and action.

What to do next

After completing this module, review your trading partner expectations. Confirm the KDEs and identifiers you need to send and receive, review label and ASN expectations, test data exchange with key partners, validate scan and system workflows, document exception procedures, and update your self-assessment roadmap.

Thank you for watching Module 5, Working Across The Supply Chain. Please proceed to Module 6.

Run time: 6 minutes 11 seconds

Module 6 — Getting Ready for 2028

What you will learn: How to determine a path towards compliance with four key concepts: implementation roadmap, self-assessment, 24-hour readiness testing, and final action planning.

Module 6 — Getting Ready for 2028: Full Transcript

Welcome to Module 6, getting ready for 2028, of the FSMA 204 and Produce Traceability Initiative education series. In this module, we will help you determine a path towards compliance with four key concepts: implementation roadmap, self-assessment, 24-hour readiness testing, and final action planning.

The three-phase implementation roadmap (2026–2028)

Implementation should be viewed as a journey rather than a single project. Begin by determining applicability and conducting a gap assessment. Next, update processes and systems, establish data exchange expectations, and pilot new procedures. Finally, train employees, validate your processes, and prepare your organization to demonstrate readiness before the compliance deadline.

A practical implementation roadmap can be organized into three phases. In 2026, assess and map applicability, gaps, processes, and data flows. In 2027, configure systems, establish data exchange, pilot with trading partners, and test spreadsheet reporting. In 2028, train employees, conduct mock exercises, validate reporting capabilities, and finalize implementation by July 20.

Scoring and validating readiness across six domains

IFPA's, FSMA 204 Self-Assessment is designed to score current-state readiness, identify supporting evidence, and prioritize remediation activities. Scores should be based on actual evidence, not intent. If evidence cannot be produced, the organization should score conservatively and document the gap, owner, target date, dependencies, and remediation actions.

Readiness needs to be validated across regulatory scope, traceability plan, FDA response, systems and data, trading partner readiness, and training or change management. These domains help learners connect the entire training series back to the self-assessment and their organization’s next steps.

Annual focus areas: 2026 through 2028

In 2026, the focus should be assessment and mapping. Teams should determine applicability, conduct a gap assessment, map CTEs and data flows, establish a cross-functional owner group, and prioritize gaps based on risk. Use the self-assessment to translate the current state into a structured workplan.

In 2027, the focus moves into configuration and pilots. Teams should configure systems, define trading partner data exchange, pilot CTE and KDE capture, validate exception handling, and test sortable spreadsheet output. Self-assessment evidence collection can run alongside each pilot.

In 2028, the focus should be training and validation. Employees should be trained on their roles, mock exercises should be conducted, reporting capabilities should be validated, the traceability plan should be finalized, and remaining high-risk gaps should be closed before July 20. It is important that readiness is backed up by evidence, not intentions.

The 24-hour readiness test and mock tracebacks

Testing your readiness is critical. A simple question can reveal how prepared your organization truly is. If FDA requested records today, could you provide complete traceability information for a specific lot within twenty-four hours?

To answer that question, conduct mock traceback exercises. Select a lot, retrieve the associated data, reconstruct the product history, produce a sortable report, and identify gaps that still need attention. Testing today can prevent challenges tomorrow.

The readiness test should prove that records are complete, connected, retrievable, sortable, and actionable. If a team can only describe the process but cannot produce evidence, the organization should document the gap and prioritize remediation.

Building the remediation action register

Testing should produce an action register. Each gap should have a risk level, an owner, dependency, target date, and status. This connects directly to the self-assessment remediation output and helps leadership track progress toward readiness.

FSMA 204 implementation is about much more than regulatory compliance. It requires people, processes, technology, and supply chain coordination working together. Organizations that begin planning now will be better positioned to comply, respond confidently during investigations, and strengthen traceability capabilities across their businesses.

The six commitments for learners

As learners leave this education series, they should focus on six commitments: know if they are covered, understand TLCs, CTEs, and KDEs, assess gaps with evidence, build the traceability program, prepare supply chain partners, and test readiness with trained teams.

Series summary and final call to action

Before we close, let’s summarize this final module. Implementation should be managed as a journey. The roadmap moves from assessment to building to validation. The self-assessment helps score readiness and prioritize remediation. Mock traceback exercises reveal real operational gaps. Twenty-four-hour retrieval capability must be tested, not assumed. And final readiness requires people, process, technology, and partner alignment.

The final call to action is to begin evaluating readiness today. Complete or revisit the self-assessment, run a lot-level readiness test, update your remediation register, train the roles involved, and continue retesting until you can demonstrate readiness with evidence.

Sources and contact

Information presented in these modules was sourced from and adapted from the Produce Traceability Initiative FSMA 204 Implementation Guidance document. For additional resources, visit the Produce Traceability Initiative, as well as the IFPA FSMA 204 Resources page. Inquiries can also be sent to FoodSafety@freshproduce.com

Thank you for watching Module 6, getting ready for 2028. Please visit the FSMA 204 Resources page on the IFPA website for more information, or contact our team at FoodSafety@freshproduce.com with inquiries.

Common Questions

It is a free, six-module training series from the International Fresh Produce Association covering the FDA Food Traceability Rule and the Produce Traceability Initiative. The series explains what the rule requires, who it applies to, and the practical steps organizations should take to prepare before the compliance date.

The series is free and available to everyone. IFPA membership is not required to watch any module or read any transcript.

Anyone whose company grows, packs, ships, receives, or transforms a food on the FDA Food Traceability List. That includes growers, packers, processors, distributors, wholesalers, retailers, and foodservice operators — and within those businesses, food safety and QA, operations, IT, EDI, and procurement teams.

All covered entities share a single compliance date of July 20, 2028. FDA deliberately set one date across the entire supply chain, because traceability only works when information flows seamlessly from one trading partner to the next.

FSMA 204 applies to foods on the FDA Food Traceability List (FTL). For the produce industry that includes leafy greens, tomatoes, peppers, melons, herbs, and certain fresh-cut fruits and vegetables. The first step toward compliance is confirming exactly which of the foods you handle are covered.

FSMA 204 is a federal regulation; the Produce Traceability Initiative is a voluntary industry standard. PTI provides standardized case labeling and data practices that align closely with what FSMA 204 requires, and many major buyers expect PTI compliance regardless of the rule.

The series is designed to build in sequence, and Module 1 provides the foundation for the concepts that follow. You can jump to a specific module if you need a particular topic, and full transcripts let you scan for the section you need.

Yes. A full written transcript is published alongside every module, so you can read instead of watch, search for a specific term, or review the material after viewing.

NEXT STEPS

New to the rule? Start with FSMA 204 Explained on our FSMA 204 Resources page.

Ready to score your readiness? Download the free FSMA 204 Readiness Self-Assessment.

Building your records? use the PTI implementation guidance and electronic sortable spreadsheet templates.

Want to know where IFPA stands? Read our advocacy and comments to FDA on practical, WMS-supported traceability.

Need help?

Erik Larsen

Director, Supply Chain

International Fresh Produce Association

+1(302)607-2118 Email Erik Larsen

FSMA 204 Education Series

A free, six-module training series on the FDA Food Traceability Rule and the Produce Traceability Initiative.

THE SERIES AT A GLANCE

THE LEARNING PATH

Module 1 — Understanding FSMA 204

Read The Full Transcript

Module 1 — Understanding FSMA 204: Full Transcript

What this module covers

What FSMA 204 requires

Why the rule exists

The benefits of stronger traceability

Which foods are covered

Which activities are covered

The role of the Produce Traceability Initiative (PTI)

How FSMA 204 and PTI relate

The compliance deadline: July 20, 2028

Getting started on readiness

Knowledge check

Module 1 summary

What to do next

Module 2 — Core Traceability Concepts

Read The Full Transcript

Module 2 — Core Traceability Concepts: Full Transcript

The core traceability framework

Traceability Lot Codes (TLC)

Critical Tracking Events (CTE)

Key Data Elements (KDE)

How TLCs, CTEs, and KDEs work together

Operational impact across your organization

Module 2 summary

What's next

Module 3 — Does the Rule Apply to You

Read The Full Transcript

Module 3 — Does the Rule Apply to You: Full Transcript

Core criteria: Foods and activities

Supply chain traceability in practice: The tomato example

Activity-based compliance across covered entities

Exemptions and partial exemptions

Module 3 summary

Action items and readiness

What's next

Module 4 — Building Your FSMA 204 Program

Read The Full Transcript

Module 4 — Building Your FSMA 204 Program: Full Transcript

Scoring readiness with evidence

Conducting an operational gap assessment

Developing your traceability plan

Translating CTEs and KDEs into repeatable procedures

Recordkeeping and 24-hour response capability

Cross-functional ownership and governance

Technology evaluation and systems integration

Trading partner collaboration and supplier onboarding

Testing the chain: Product journey traceback

Turning assessment into a remediation roadmap

Module 4 summary

Next steps: Complete your self-assessment

Module 5 — Working Across The Supply Chain

Read The Full Transcript

Module 5 — Working Across The Supply Chain: Full Transcript

Trading partner readiness is compliance readiness

Tracking product and data movement: Tomato supply chain example

Common data standards: GS1 and PTI in produce

Traceability lot code sources and label integration

EDI 856, ASNs, and receiving exception management

Master data governance and cross-system alignment

Collaborative supplier onboarding and evidence-based scoring

Knowledge check

Module 5 summary

What to do next

Module 6 — Getting Ready for 2028

Read The Full Transcript

Module 6 — Getting Ready for 2028: Full Transcript

The three-phase implementation roadmap (2026–2028)

Scoring and validating readiness across six domains

Annual focus areas: 2026 through 2028

The 24-hour readiness test and mock tracebacks

Building the remediation action register

The six commitments for learners

Series summary and final call to action

Sources and contact