FSMA 204 Supplier Checklist for Produce Buyers

Your traceability records are only as good as what your suppliers send you. FSMA 204 makes each link in the chain dependent on the one before it, which means a buyer's compliance is largely a procurement problem rather than a systems problem.

This is what to establish with suppliers, and why each item matters.

Why the deadline isn't the real deadline

FDA's original compliance date was January 20, 2026. A proposed rule would move it 30 months to July 20, 2028, and Congress separately directed FDA not to enforce before that date, which FDA has said it will honour.

But your practical deadline is usually earlier and comes from your own customers. Major retailers have set supplier traceability requirements on their own timelines, and those are contractual. If you sell into a chain that requires full KDE data next season, the federal extension buys you nothing. Work backward from your buyer's requirement, not FDA's.

That also cuts the other way when you're the buyer: your suppliers have heard "it's been pushed to 2028" and many have stopped work. Asking now is how you find out.

What you need from every supplier

Six things, in writing, before the load ships:

1. The traceability lot code, on the case and in the data. A code that exists only on paperwork forces manual keying at your dock and breaks the moment a case is separated from its BOL. It should be on the label and in the ASN or invoice.

2. The traceability lot code source. This is the entity that created the lot, usually the initial packer. It is frequently not the company that shipped you the load, and your receiving records need both separately.

3. Product description matching the label. Not their internal SKU nickname. If their description and your receiving record don't match, reconciling a recall traceback becomes manual.

4. Their exemption status, and the basis for it. This is the question that changes your obligations, and it's covered below.

5. A named traceability contact. Separate from your buyer contact. When FDA asks for records, you need someone who can answer within hours, not a salesperson who forwards it.

6. Written confirmation they can produce records in 24 hours. Your ability to respond depends on theirs. Ask what format — if the answer is "we'd pull the files," that's a no.

The exemption question, and why it matters most

Ask every supplier whether they consider themselves exempt from the Food Traceability Rule, and on what basis.

The reason is counterintuitive: an exempt supplier increases your workload rather than reducing it. When you receive an FTL food from someone the rule doesn't apply to, § 1.1345(b) requires you to assign the traceability lot code yourself if one hasn't been assigned. You become the lot code source. Every downstream record traces to a code you created, on product you never packed.

Retail food establishments and restaurants are excepted from that assignment duty. Distributors and wholesalers are not.

So the answer determines whether a given supplier is a data-passing relationship or a data-origination one. Those need different receiving workflows, different labelling capability, and different volumes of effort — and you can't tell which is which by looking at the pallet.

Questions that expose gaps

Vendor questionnaires get yes-answered. These are harder to bluff:

• "Show me a case label and the matching ASN for a recent shipment." One artifact reveals whether the lot code, product description, and TLC source actually agree.
• "Who assigned the lot code on this load?" If they hesitate, they may be reshipping without understanding whether they transformed it.
• "Do you repack or relabel anything you send us?" If yes, they're a transformer and should be assigning new codes. Many don't realise it.
• "What's on your Food Traceability List determination?" Coverage is by commodity and more specific than most summaries suggest.
• "If we called at 4pm Friday for every lot of one item from the last 90 days, what happens?" The 24-hour clock doesn't care that it's the weekend.

What to put in purchasing terms

Keep it short and specific:

• KDEs required at or before delivery, in a named format
• Case labels carrying the TLC in scannable form
• Notification if exemption status changes
• Records retrievable within 24 hours on request
• Right to audit traceability records

The last one matters because the alternative is discovering the gap during a recall.

FAQ

What if a supplier says they're exempt?

Get the basis in writing, and plan to assign lot codes yourself. Under § 1.1345(b), receiving from an exempt supplier means you assign the TLC if one hasn't been assigned — unless you're a retail food establishment or restaurant.

Can I rely on a supplier's PTI label to satisfy my records?

Not by itself. The label carries the identifiers, which makes accurate capture much easier, but FSMA 204 is a recordkeeping rule. You still maintain the receiving records.

Do I need this from suppliers of non-FTL commodities?

Only foods on the Food Traceability List are covered. Coverage is by commodity and narrower than many people assume, so confirm rather than applying it blanket.

What if a supplier sends incomplete records?

Go back to the source and ask for complete, legible information rather than filling the gaps yourself. Build it into receiving as an exception workflow.

Should I wait until closer to 2028?

Your retail customers may require it sooner, and suppliers who have stopped work will need lead time. The cost of asking early is a few emails.