Producers · Compliance

FSMA Compliance for Seafood Producers

Plain-language guidance on the Food Safety Modernization Act — specifically FSMA Section 204, the traceability rule that took effect in January 2026.

What Is FSMA?

The Food Safety Modernization Act (FSMA) was signed into law in 2011. It represents the most significant reform of U.S. food safety law since 1938. The core shift: from responding to foodborne illness outbreaks after the fact, to preventing them through science-based controls built into the production system.

FSMA has several rules that affect seafood. For producers, the two most important are the Seafood HACCP regulation (21 CFR Part 123, predates FSMA but is now enforced under it) and the Food Traceability Final Rule (Section 204).

FSMA 204 at a Glance

Official Name: Food Traceability Final Rule (Section 204)
Compliance Date: January 20, 2026
Applies To: Handlers of foods on the FDA Food Traceability List
Seafood on FTL: Finfish (fresh/frozen), crustaceans, smoked fish, fresh-cut fish, ready-to-eat dips/spreads with finfish
Core Requirement: Maintain KDE records for CTEs; provide within 24 hours on FDA request
Records Retention: 2 years from creation date

Who Does FSMA 204 Apply To?

The rule covers anyone who manufactures, processes, packs, or holds foods on the FDA Food Traceability List. Several exemptions exist — but most commercial seafood operations are covered.

✓

Commercial Fishermen (Harvesters)

If you harvest finfish, crustaceans, or other FSMA-designated species for commercial sale, you must maintain harvest records including the KDEs listed above. Very small business exemption may apply — see below.

✓

Seafood Processors

Any entity that processes (fillets, freezes, smokes, portions, or repackages) FSMA-designated seafood must document processing CTEs with full KDE linkage to harvest records.

✓

Distributors and Wholesalers

Distributors handling designated foods must maintain shipping and receiving CTE records and be able to provide them to FDA within 24 hours of a request during a foodborne illness investigation.

—

Restaurants and Retail

Restaurants and retail food establishments are generally exempt from FSMA 204 recordkeeping requirements — though they may face requirements from their suppliers or insurers.

—

Very Small Businesses

Businesses with average annual monetary value of all food sold of $1 million or less (3-year average) may qualify for the very small business exemption. This does not exempt you from Seafood HACCP.

—

Direct-to-Consumer Sales

Sales made directly to individual consumers (farm stands, CSF shares, farmers markets) are generally exempt from the traceability rule's recordkeeping requirements.

Critical Tracking Events and Key Data Elements

FSMA 204 defines the specific events (CTEs) at which records must be created, and the specific data fields (KDEs) that must be captured at each event. These are not suggestions — they are the regulatory minimum.

CTE: Harvest

The act of catching or collecting seafood from the wild or an aquaculture operation.

Required KDEs

→Harvester name and license/permit number
→Vessel name and registration number
→Fishing area / geographic coordinates or named area
→Harvest date
→Species (scientific name or accepted common name)
→Quantity and unit of measure
→Lot code or batch identifier

CTE: Landing

When harvested seafood is offloaded from a vessel at a port or dock.

Required KDEs

→Location of landing (port name, GLN if available)
→Date of landing
→Receiver name and contact
→Quantity received
→Species
→Reference to harvest lot code

CTE: Processing

Any transformation of the seafood — filleting, smoking, freezing, portioning, packaging.

Required KDEs

→Processor name and facility address
→Processing date
→Input lot codes (from harvest/landing)
→Output lot codes (new product form)
→Species
→Process type
→Quantity input/output

CTE: Shipping

Movement of product from one location to another — vessel to processor, processor to distributor, distributor to buyer.

Required KDEs

→Shipper name and address
→Receiver name and address
→Ship date
→Quantity shipped
→Lot code
→Bill of lading or shipment reference

CTE: Receiving

The counterpart to shipping — the event at which a new party takes custody of the product.

Required KDEs

→Receiver name and address
→Shipper name
→Receipt date
→Quantity received
→Lot code verification
→Reference to shipping documentation

Practical Steps to Comply

These steps apply whether you are starting from zero or auditing an existing operation.

Start with Harvest Records

Even if you are not yet ready for a full digital traceability system, start capturing the KDEs at harvest. A structured paper form or spreadsheet with vessel name, date, species, area, and quantity is a meaningful first step. You cannot backfill records — they must be contemporaneous.

Assign Lot Codes

Every batch of product needs a unique identifier that travels with it through the chain. This can be as simple as a date + vessel code + species code (e.g., PCS-2025-0314-HAL). What matters is that you can use the lot code to pull up all the KDEs associated with that batch.

Document Every Custody Transfer

Every time product changes hands — vessel to dock, dock to processor, processor to distributor — a shipping CTE and receiving CTE event needs to be created. These are what connect the harvest record to the end buyer's receiving records.

Be Ready for a 24-Hour Records Request

Under FSMA 204, FDA can request records for a designated food within 24 hours during a foodborne illness investigation. Your record system — paper or digital — needs to be organized well enough that you can pull all records for a given lot code in that window.

Consider Digital Compliance Tools

Platforms like Wholechain are built specifically for this compliance scenario. Mobile capture of harvest data, automated lot code generation, standardized KDE formatting, and records export in FDA-compatible formats. For producers selling into commercial channels, the ROI is straightforward.

Producer Getting Started Guide →HACCP Requirements Traceability Explained