← All posts

FDA's June 15 lot-level traceability meeting: the pain points the industry raised

FDA held its June 15 lot-level traceability meeting and published the discussion paper behind it. Here are the real pain points the industry flagged, and why almost none of them are about you if you are a small producer.

Anas Marwan7 min read
FSMA 204FDAlot-level traceabilitysmall food producerspublic commenttraceability lot code

On June 15, the FDA held its second quarterly meeting on whether lot-level tracking actually works, and it published the discussion paper that framed the whole conversation. We previewed this meeting before it happened. Now that it has, here is the honest update we promised: the meeting was real, the comment window is still open, and almost none of the pain points on the table are about you if you are a small craft producer.

That last part is the surprise, and it is worth sitting with.

What changed on June 15 (and what did not)

The meeting happened. Roughly three dozen people spoke. FDA listened. And exactly nothing about the rule changed that day, which is normal: these are listening sessions, not decision points.

Here is what is actually true after June 15:

  • The compliance date is still July 20, 2028. Congress set it, and FDA has said it intends to comply with that directive. The meeting did not touch it.
  • This was the second of a recurring series. The first was a March 6 listening session hosted by the Partnership for Food Traceability. A third comes in September 2026, and a second FDA public meeting is already scheduled for November 6, 2026. The advocacy window is not closing, it is repeating.
  • The comment docket is open until July 15, 2026. Written comments to docket FDA-2014-N-0053 carry the same weight as speaking did.

So if you missed June 15, you did not miss your chance. You missed one stop on a quarterly tour.

Who was actually in the room

This matters more than it looks, so read the speaker list, not just the agenda.

The roughly three dozen people who spoke were overwhelmingly technology and software vendors (ReposiTrak, Trustwell, GS1 US, Wholechain, FoodComply, and a dozen more), distributors and wholesalers (AMCON, Four Seasons Produce, Russ Davis Wholesale), and large trade associations (the Consumer Brands Association, the National Grocers Association, Western Growers). Actual small craft producers were rare. A salsa maker and a small grocery cooperative were among the few exceptions in a room full of enterprise supply-chain operators.

That composition is the whole story of this meeting, because it shaped which problems got airtime. The people who showed up brought the problems they have. And the problems a 110,000-facility traceability network has are not the problems a four-person creamery has.

The pain points the industry actually raised

FDA's discussion paper is the cleanest record of what the industry has been complaining about, because the agency wrote it by collecting those complaints first. It lists eight areas "where we currently have the most questions." Here they are in plain language.

#Pain pointWho it actually affects
1Mixed-lot pallets. FTL foods arrive on pallets holding several lots, and they get mixed further in pick slots. To track every traceability lot code (TLC) accurately, a distribution center said it would have to scan every single case, which is "logistically challenging and perhaps cost-prohibitive."Distribution centers
2Inferred lot codes. Many DCs already calculate which lots shipped (from receiving order plus first-expired-first-out picking) instead of scanning. They want credit for a good inference plus a list of other lots that "might" have been included.Distribution centers
3Eaches. When a case is broken open to ship a few individual units, the TLC was printed on the case, not the unit, so the data falls off the item.Distributors, convenience stores
4Returns and reclamations. Keeping a full set of key data elements on individual items sent back up the chain is hard.Distributors, retailers
5Food waste recovery. Donated surplus food is already exempt from shipping records. The industry wants to know what else around recovery is unclear.Retailers, recovery orgs
6Intracompany shipments. Moving product between your own facilities, with no transformation, feels like duplicate recordkeeping.Multi-site operators
7Retail-kitchen transformation. A store that makes sushi to sell on-site is exempt, but if it sends some to a sister store, transformation and shipping records kick in.Restaurants, grocery delis
8No common data standard. Industry wants one format to exchange KDEs. FSMA legally bars FDA from mandating a specific technology.Everyone, but mostly vendors

Read that "who it affects" column again. Seven of the eight are problems of the middle of the supply chain: warehouses, distributors, multi-site chains, and retail delis. The one that touches everyone, the data standard, is the one FDA is legally not allowed to solve.

What this means if you are a small producer

Here is the part nobody else will tell you plainly, because the people writing the recaps are the vendors and associations who were in the room.

The flexibilities on the table are not for you. A "reasonable range of lot codes" helps a distribution center that cannot scan a mixed pallet. It does nothing for the creamery that assigns one clean lot code to a batch of chevre. The "eaches" debate is about a broken case at a convenience store, not a jar of almond butter you packed yourself. If you were hoping June 15 meant the rule was about to get lighter for small operations, the discussion paper does not contain a single scale-based carve-out for small producers. Not one of the eight topics is "exempt the little guys."

And there is a quieter point underneath all of it. Most of these flexibilities only work if your lot code is clean at the source. The whole downstream game of inferring and ranging lot codes assumes the TLC was assigned correctly the first time, by the entity that packed or transformed the food. That entity is often you. You are the TLC source. So the meeting, read carefully, does not relax the small producer's core job. If anything, it quietly makes it more important, because everyone downstream is now negotiating how loosely they can carry the code you created.

That is the same thing your retailers have been telling you all along, just from a different direction. Costco, Whole Foods, Wegmans, and Erewhon are not waiting for FDA to finish its quarterly tour. The questionnaire your buyer sent you is still due on the date they set, and it still expects a clean, traceable lot code from you. The June 15 meeting and the retailer portal live on completely different clocks.

The comment window is still open

If you want the rule to fit a business your size, the move is to say so in writing before July 15.

Submit a comment to docket FDA-2014-N-0053. The most useful thing you can do is fill the gap the speaker list revealed: FDA heard from vendors and distributors all afternoon. It barely heard from producers. A concrete note like "here is the exact step in my process where assigning a lot code costs me X hours a week, and here is what would make it workable" is worth more than another association talking point, precisely because the agency is not getting many of them.

A few things worth raising if they are true for you:

  • Where transformation forces a lot-code decision your current system cannot cleanly make.
  • The gap between what a retailer portal demands today and what the rule will require in 2028, and how a small producer is supposed to bridge it alone.
  • Whether the recordkeeping burden actually matches who has the staff to carry it.

And if you miss July 15, the September Partnership for Food Traceability discussion and the November 6 FDA public meeting are both still ahead.

What to do while the FDA deliberates

Advocacy is the long game. The buyer asking you for a clean lot trace this quarter is the short game, and the short game is the one with a deadline you cannot move.

If you are not sure where your own system stands, start there. Our FSMA 204 Compliance Score quiz takes about five minutes and tells you which parts of lot-level tracking would bite you in a retailer audit today. And if the specific question is whether your lot codes are valid, the TLC Validator checks the format in seconds.

The producer who shows up to the next FDA meeting with a working traceability system is also the producer whose comment carries the most weight, because they are describing real friction, not hypothetical friction. That is exactly the voice the June 15 speaker list was missing.


This post was first published on June 2 ahead of the June 15 meeting and substantially rewritten on June 23 with what the meeting and FDA's discussion paper actually covered. Sources: the FDA meeting page, the discussion paper, and the public comment docket.

Frequently asked questions

What was the FDA June 15 lot-level traceability meeting about?
It was a free virtual public meeting called Challenges and Solutions in Lot-Level Food Traceability, held June 15, 2026, from 12:00 to 3:30 p.m. Eastern. It was the second of FDA's quarterly engagements required by Congress to find additional flexibilities for the FSMA 204 lot-level tracking requirement. FDA published a discussion paper ahead of it listing eight areas where it has the most questions, and roughly three dozen stakeholders spoke.
What pain points did the industry raise at the meeting?
FDA's discussion paper centers on eight challenges: mixed-lot pallets that would force distribution centers to scan every case, inferring lot codes instead of scanning, broken-case 'eaches', returns and reclamations, food waste recovery, intracompany shipments, retail kitchens that transform food and send it to other stores, and the lack of a common data standard. Most of these are distribution-center and warehouse problems, not small-producer problems.
Does the FDA meeting change the FSMA 204 compliance deadline?
No. The enforcement date is still July 20, 2028, set by Congress, and nothing about that changed on June 15. Any actual flexibility would come later, through a separate process. Retailer traceability demands, like ReposiTrak onboarding and supplier questionnaires, are not affected by the meeting at all.
Can small producers still comment on FSMA 204 lot-level tracking?
Yes. Written comments on the discussion paper are due July 15, 2026, to docket FDA-2014-N-0053 on regulations.gov, and they carry the same official weight as speaking at the meeting. There are also more engagements coming: a Partnership for Food Traceability discussion in September 2026 and a second FDA public meeting on November 6, 2026.

Read next