FSMA 204 Receiving Requirements for Buyers and Distributors

Most FSMA 204 coverage is written for the people who grow and pack produce. If you buy it, take it into a warehouse, and ship it back out, the rule lands on you differently — and the section that governs your obligation, 21 CFR 1.1345, is one most supplier-facing guides skip past.

This is what receiving actually requires, written for the buy side.

The short version

Every time you take possession of a traceability-lot of a listed food, you owe eight pieces of information, linked to that lot. You mostly don't generate them — your supplier does, and passes them to you. Your job is to capture them, keep them linked, and produce them on request.

The two places buyers get caught are receiving from an exempt supplier, where the obligations shift onto you, and intracompany transfers, which count as receiving more often than people expect. Both are below.

When this actually bites

The date situation is messier than most summaries admit, and worth stating precisely.

The rule's original compliance date was January 20, 2026. In August 2025 FDA published a proposed rule to push that out 30 months, to July 20, 2028. Separately, Congress directed FDA not to enforce the Food Traceability Rule before that same date, and FDA has said it intends to comply with that directive.

So the practical answer is July 20, 2028. But note the mechanism: a proposed extension plus a congressional enforcement bar is not the same thing as a finalized new compliance date. Confirm current status at fda.gov before making a decision that depends on it.

Retail buyers are a separate clock entirely. Several major chains have set supplier requirements ahead of FDA's timeline, and those are contractual — the federal extension does nothing for you if your buyer's purchase agreement says otherwise.

What counts as receiving

Receiving means taking possession of a food at a location after it was transported from somewhere else. Two clarifications matter more than they sound:

Intracompany movement counts. If you transfer product between two facilities with different street addresses, that's a receiving event — even though both locations are yours and no money changed hands. Multi-DC operations generate far more receiving records than they expect.

Pre-packing receipt doesn't count. Under § 1.1345(c), the section doesn't apply to receiving a raw agricultural commodity before it has been initially packed. Field-run product moving to a packinghouse isn't a receiving CTE. That's covered instead by the initial packer's obligation to record the farm and harvest location.

The eight receiving KDEs

For each traceability lot you receive, § 1.1345(a) requires records containing, and linked to that lot:

#	Key data element
1	The traceability lot code for the food
2	Quantity and unit of measure (6 cases, 25 RPCs, 200 pounds)
3	The product description
4	Location description for the immediate previous source, other than a transporter
5	Location description for where you received it
6	The date you received it
7	Location description for the traceability lot code source, or the TLC source reference
8	Reference document type and reference document number

Note item 4: the immediate previous source, other than a transporter. Your carrier is not the previous source. The previous source is whoever shipped it — which is often not who assigned the lot code, and that's why item 7 exists as a separate field. The TLC source is the entity that created the lot, typically the initial packer. On a load that has passed through a distributor, those are three different companies, and the rule wants all of them distinguishable.

Item 8 is the one operations underestimate. Reference document means the paperwork the event lives on — a BOL, purchase order, ASN, invoice, receipt, or database record. You need both its type and its number, and it has to point at something you can actually retrieve.

The trap: receiving from an exempt supplier

This is the paragraph buyers miss, and it inverts who does the work.

When you receive a listed food from someone the rule doesn't apply to — a small farm below the exemption threshold, for instance — § 1.1345(b) applies instead. The list is shorter, but one item changes everything:

The traceability lot code for the food, which you must assign if one has not already been assigned.

You become the lot code source. The location description you record for where you received the food is the TLC source. You're no longer copying data forward; you're originating it, and every downstream receiver's records will trace back to the code you created.

The exception: retail food establishments and restaurants don't have to assign a TLC in this situation. Distributors and wholesalers do.

Practically, this means an exempt supplier is not a lighter compliance burden for you. It's a heavier one. If a meaningful share of your inbound volume comes from small farms, you need a lot-code scheme and a way to physically apply it to cases before that product moves on.

What to ask your suppliers for

The rule doesn't dictate a format, which means the burden of getting usable data lands on your purchasing terms rather than on FDA. Worth specifying in writing:

• The TLC and TLC source for every lot, on the case label and in the ASN or invoice
• Product description matching what's on the label, not an internal SKU name
• Whether they consider themselves exempt, and on what basis
• A named contact for traceability records, separate from your buyer contact
• Confirmation they can produce records within 24 hours, since your own ability to respond depends on theirs

That last point is the one with teeth. FDA can require records within 24 hours of a request, and if your supplier can't reconstruct a lot quickly, you can't either.

FAQ

Do I need receiving records for produce I buy and resell without touching it?

Yes. Receiving is a critical tracking event regardless of whether you alter the product. If you also ship it onward, that's a separate shipping CTE with its own records.

Does receiving apply to product moving between my own warehouses?

Yes, when the two locations have different street addresses. Common ownership doesn't exempt an intracompany transfer.

What if my supplier sends incomplete or illegible records?

The expectation is that you go back to the source and ask for legible, complete information rather than filling gaps yourself. Build that into your receiving process as an exception workflow, because a lot you can't document is a lot you can't defend.

Do I have to assign a lot code when buying from a small farm?

If that farm is exempt from the rule and no code has been assigned, yes — unless you're a retail food establishment or restaurant. Distributors and wholesalers must assign one.

Is a PTI label enough to satisfy receiving requirements?

No. A PTI case label carries the identifiers efficiently, but FSMA 204 is a recordkeeping rule. The label helps you capture the data accurately; the records are still what FDA asks for.