The Real FSMA Implementation Timeline for Grower-Shippers is 18-24 Months

For operations moving volume across multiple harvest locations and facilities, a disciplined FSMA 204 implementation realistically spans 18-24 months. Anything shorter typically compresses testing and training which can cause traceability systems to fail under pressure. Here’s what an estimated timeline looks like:

Phase 1: Operational Assessment & Interdepartmental Mapping (3-4 Months) 

This is where most companies underestimate the amount of prep work needed. Before selecting or configuring software, you need to assemble an interdepartmental team: 

• Senior Leadership 

• Facilities Operations (receiving, packing, cooler, storage and shipping) 
• Harvest management 
• Food safety / QA 
• IT 
• Warehouse leadership 
• Sales / Order management 

Together, your team needs to be able to evaluate not just “what data we need,” but the answers to FSMA preparation questions as well:

• Where is each CTE occurring? 
• When does the corresponding KDE become available? 
• Who is responsible for each CTE? 
• How and what KDE’s are currently recorded? 
• Is it recorded at the moment of activity; or reconstructed later? 

These questions will vary depending on the CTE’s your business works with.

Harvest (CTE):

• When is Harvest Location confirmed? 
• Who assigns the Grower Lot? 
• On Field Packed Items, who assigns the Traceability Lot Code (TLC)? 
• Is it written on paper, keyed into a system, or captured on a digital device? 
• When is it entered into a system at the time of activity, same day, or later? 
• What reference documents need to be included? 

Initial Cooling (CTE): 

• Is the cooling start time recorded automatically? 
• Is the location linked digitally? 
• What reference documents need to be included? 

Packing (CTE): 

• Are the grower and grower source verified prior to packing? 
  • If so, who does it and where? 
• When and how is the Traceability Lot Code generated? 
• Where and how are case traceability labels printed and applied? 
• Are case TLC’s captured at palletization? 
• What reference documents need to be included? 

Shipping (CTE): 

• Are case TLCs captured as pallets are built, staged, or consolidated? 
• How does pallet content TLC’s recorded in shipping? 
• What reference documents need to be included? 

Receiving (CTE):

• Are packed cases labeled with case traceability labels containing TLC? 

• How will you handle packed produce without proper case traceability labeling? 

• What reference documents need to be included? 

• What reference documents need to be included? 

In many operations, KDE’s are already available, but are not being captured at the right moment or in an easily retrievable manner. If the FDA requests your data, you have 24 hours to supply it. This is the phase where lot integrity must be achieved.

Phase 2: Process & Lot Architecture Design (4–5 Months) 

Hopefully the preparation questions exposed gaps in your workflows to address. A common issue you may have been thinking about is bullet three, “Who is responsible for each CTE?”. Answering that question doesn’t have to be hard, but your workflows will need to be redesigned around control. Here’s what I recommend.

• Designing bin-level identification discipline 
• For each CTE determine exactly when and how each KDE will be captured 
• Assigning clear ownership for each data element  
• Examining and potentially redefining Traceability Lot Code structure 
• Establishing pallet-level verification checkpoints

The goal of these improvements is to move your traceability discussion from “We usually capture that KDE.” to a confident “This employee captures this data at this moment, using this device or method.” Without properly defining who owns the data, it may cause problems with data storage. Remember, the FDA only gives your operation 24 hours to provide these records.

Phase 3: Software Integration & Configuration (4–6 Months) 

This phase is about making sure technology is aligned with your defined traceability process. This includes assessing if you need to replace your Grower Accounting or ERP system or if it is flexible enough to integrate with other systems.

You will want to assess your Lot Traceability Code; how it will be structured and how will be issued. Then you will want to review your case traceability label, the PTI Harmonized label is accepted by most receivers. Then you will want to align your mobile data collection with operational workflows, ensuring the KDE data is captured and recorded electronically. Once this is done you will want to map out your hardware deployment including:

• When and where labels will be printed as well as where you will need mobile scanners and/or forklift mounted tablets for data collection
• The areas where you need WIFI or Private Cellular installation or coverage verification in your facility and yard areas

Integration is both technical and operational. Your data must flow seamlessly through:

• Harvest documentation
• Inventory systems
• Packing lines
• Palletization
• Shipping
• Advance Ship Notices

Four to six months gives you plenty of time to test out device configs and refine new integrations in a live produce environment. It’s also enough time to stress test your data collection through seasonal transitions.

Phase 4: Workforce Deployment & Culture Shift (3–4 Months) 

Technology does not enforce discipline. People do. This is why training your team and shifting culture are so important. Training addresses what needs to be done, developing a culture of accountability ensures it get done. This phase includes:

• Supervisor accountability training
• Operational workflow verification and enforcement
• Traceability Lot Code transition protocols
• Exception handling procedures
• Daily traceability reporting verification

Phase 5: Validation, Mock Recalls & 24-Hour Stress Testing (3–5 Months) 

Before enforcement begins, your system must be pressure tested to ensure your team is 24-hour recall ready.

This phase includes:

• Retailer documentation reviews
• Pallet-level TLC validation audits
• Full trace-forward and trace-back exercises with both suppliers and customers
• Simulated FDA 24-hour record requests
• Verification that no manual reconstruction is required

The goal here is precision, not speed alone. If your mock recall expands beyond the necessary lot scope, refinement happens here and not during a real event.