FSMA 204 Compliance Map
When a recall costs $10M and takes 7 days, what is the price of a 2-hour trace?
Food Traceability List
FDA designated high-risk foods requiring enhanced traceability records.
| FTL Category | Examples |
|---|---|
| Leafy greens | Bagged spinach, romaine, butter lettuce, arugula |
| Fresh herbs | Basil, cilantro, parsley |
| Sprouts | Alfalfa, bean, radish, clover sprouts |
| Cucumbers | Whole cucumbers (fresh) |
| Peppers | Fresh bell peppers, hot peppers |
| Tomatoes | Whole fresh tomatoes |
| Melons | Cantaloupe, honeydew, watermelon |
| Tropical tree fruits | Mango, papaya, guava |
| Finfish | Fresh and frozen fish (specific species unverified) |
| Crustaceans | Shrimp, crab, lobster (fresh and frozen) |
| Mollusks | Oysters, clams, mussels, scallops |
| Shell eggs | Fresh shell eggs |
| Nut butters | Peanut butter, almond butter |
| Ready-to-eat deli salads | Pre-made mixed salads, deli case items |
| Soft cheeses | Fresh and soft-ripened cheeses (e.g., brie, queso fresco) |
Critical Tracking Events
Seven CTEs define the required record points across the supply chain.
| CTE | Description | Where It Triggers |
|---|---|---|
| Harvesting | Food harvested from farm | Farm / growing site |
| Cooling | Post-harvest cooling applied | Packinghouse / field |
| Initial Packing | Food packed into a container | Packinghouse / processor |
| First Land-Based Receiver | First US receiver of imported food | Port / import facility |
| Shipping | Food leaves a farm, facility, or warehouse | Shipper's dock |
| Receiving | Food arrives at a farm, facility, or warehouse | Receiver's dock |
| Transformation | Food changes form (e.g., cut, cooked, mixed) | Processor / manufacturer |
Key Data Elements × Stack Coverage
| KDE | Required At CTE | Baxus/DeVin Stack | Coverage |
|---|---|---|---|
| Traceability lot code (TLC) | Initial Packing, Shipping, Receiving, Transformation | Solana SPL NFT (mint = TLC surrogate) | Partial — lot code must map to mint address; reconciliation layer needed |
| TLC source reference | All lot-coded CTEs | On-chain metadata via Metaplex DAS | Partial — schema exists, field population not enforced |
| Location description (GLN or equivalent) | All CTEs | RedBite RFID scan location + on-chain event | Partial — location must be submitted as GLN; off-chain mapping unverified |
| Commodity description | Initial Packing | SPL NFT attributes field | Satisfied — wine/spirits mapped; food categories require extension |
| Quantity and unit of measure | Shipping, Receiving | SPL-404 fractional + NFT quantity field | Partial — unit standardization (cases vs. units) not enforced |
| Date and time of CTE | All CTEs | Helium LoRaWAN timestamp + Solana block timestamp | Satisfied — dual timestamp (sensor + chain) exceeds requirement |
| Reference document type and number | Shipping, Receiving | IPFS hash linked in NFT metadata | Partial — IPFS CID satisfies immutability; FDA reference doc format unverified |
| Name of transporter | Shipping | Not currently in stack | Gap — no custody-of-transport record in current architecture |
| Iridia DNA tag binding | Initial Packing | Iridia molecular tag linked to NFT | Satisfied for high-value items; cost prohibitive at commodity scale |
One Up, One Back
| Dimension | Paper-Based (Current) | On-Chain Custody |
|---|---|---|
| Visibility | Single-party view; shared by phone/email | All authorized parties read same chain |
| Retrieval time | 2–7 days per FDA 2020 study | Minutes (block query + IPFS fetch) |
| Dispute resolution | He-said/she-said; paper can be altered | Immutable timestamp; multi-sig custody |
| Audit cost | Manual labor; $50–$200/hr compliance staff | Query cost; automated compliance export |
| Cold chain proof | Temperature logs stored locally, often missing | Helium sensor events permanently on-chain |
| Recall scope | Over-broad (conservative) due to poor trace | Precise lot-level recall; smaller scope |
Deadline
FDA originally set FSMA 204 compliance for January 20, 2026. FDA extended the compliance date by 30 months to July 20, 2028, citing industry readiness concerns. Verified against FDA.gov FSMA 204 rule page.
The two-year extension creates a narrow adoption window: companies that implement now operate 2 years ahead of the mandate and can offer compliance-as-a-service to their supply chain partners before the deadline forces mass adoption.
Wedge Opportunities
| Gap | Opportunity | Who Buys |
|---|---|---|
| Traceability lot code reconciliation | API bridge: lot code ↔ Solana mint address, auto-generated at Initial Packing CTE | Packers, co-packers, cold storage operators |
| KDE submission API | Structured FDA-compliant record export from on-chain data; eliminates manual compliance labor | Any FTL-category producer or distributor |
| Sensor-verified temperature logs for perishables | Helium LoRaWAN cold chain proof attached to receiving CTE; converts sensor data to FDA-admissible record | Importers of tropical fruits, seafood, dairy |
| Transporter custody record | Missing stack layer — name and credentials of transporter at Shipping CTE | Logistics providers, 3PLs, freight brokers |
| Transformation event tracking | Cut/process/mix events not currently modeled in SPL NFT architecture; burn-and-mint pattern needed | Fresh-cut produce processors, deli manufacturers |
Context
- Food Industry — Industry overview and value chain
- Food Protocols — Standards stack including FSMA, GS1, SPL
- DePIN Platform — Sensor-to-chain infrastructure
- Solana — Settlement layer for lot code NFTs
Links
Questions
What is the minimum viable implementation that satisfies FSMA 204 for a single FTL category without disrupting the existing supply chain?
- Which CTE creates the most reconciliation failures in practice — Shipping or Receiving — and does on-chain custody change who bears the burden of proof?
- If the transporter custody gap is the only missing KDE, does that block full compliance or only partial credit?
- At what volume does the Helium sensor + Solana NFT architecture become cheaper per shipment than paper-based compliance?