FSMA 204 Key Data Elements (KDEs) — The 7 Fields Your Receiving Must Capture
TLC, quantity, product description, location, date, reference document, supplier — the 7 KDEs FSMA 204 requires at receiving. Where most operations fall short and how to fix it.
ShelfLifePro Editorial Team
Inventory management insights for retail and pharmacy
Companion to [FSMA 204 — what US grocers and distributors actually need now](/blog/fsma-204-deadline-2026-what-us-grocers-need-now). That post covers the rule shape; this one drills into the Key Data Elements you must capture per Critical Tracking Event.
Why the KDE list is the operational heart of FSMA 204
The FDA's Food Traceability Final Rule under FSMA Section 204 is structured around two concepts: Critical Tracking Events (CTEs — the moments where traceability data must be captured) and Key Data Elements (KDEs — the specific data points that must be captured at each CTE). The CTEs are the events; the KDEs are the fields.
For most grocers, distributors, and foodservice operators, the CTE that matters most day-to-day is receiving. This post walks through the 7 KDEs you must capture at receiving for any food on the FDA's Food Traceability List, what each one means, and where the typical operation falls short.
Not sure how much you're losing to expiry?
Run a free inventory waste audit — find your bleeding SKUs in 60 seconds. No sign-up required.
Run free auditThe 7 KDEs at receiving (per FDA Final Rule, 21 CFR 1.1335)
For each lot of an FTL food received, you must capture:
1. Traceability Lot Code (TLC). The unique identifier the prior trading partner assigned to the lot. This isn't just any lot code — it must be the specific TLC the supplier passed in their shipping records. If the supplier didn't pass it, you have a problem (their problem becomes yours when the FDA shows up).
2. Quantity received and unit of measure. How many cases / pounds / units in the lot.
3. Product description. Including the FTL category. "Leafy greens — romaine, bagged, 12 oz" not just "produce."
4. Location identifier of the receiving location. Your warehouse / store / kitchen address (or your internal location code that maps to an address).
5. Date you received the food. Local date at the receiving location.
6. Reference document type and reference document number. Typically the supplier's invoice or shipping document. Lets the FDA tie your record to the supplier's record.
7. Entity that shipped the food (your supplier). Their name + address (or the trading-partner identifier they registered with FDA).
Capture these 7 fields per lot, retain for two years, and you've satisfied the receiving CTE for FSMA 204. Sounds simple. The execution is where most operations break.
Where the typical operation falls short on KDEs
TLC capture is patchy. The supplier passes the TLC on the invoice or ASN, but the receiving staff records the invoice number in the inventory system and not the TLC. Six months later, when an FDA records request asks for "the TLC of romaine lot received March 14," staff dig through email looking for the original invoice PDF.
Quantity unit of measure is inconsistent. The supplier ships "10 cases" but each case contains 24 packages and each package is 12 oz. The FDA Final Rule allows quantity in any unit — but it must be consistent across your records. If you record "10 cases" at receiving and "120 oz dispatched" at outbound, the FDA can't reconcile the chain.
Product description is too vague. "Salad mix" doesn't satisfy the requirement. The FTL has specific categories (leafy greens, sprouts, fresh herbs, etc.) and the description must let an inspector identify which FTL category the product belongs to.
Reference document number missing. Staff record the lot but not the supplier invoice number. Without it, the FDA can't tie your record to your supplier's record, which breaks the chain-of-custody story FSMA 204 was designed to enable.
Receiving location is at company level, not at unit level. "Acme Foods Inc" doesn't satisfy the rule. The location identifier must point to the specific physical receiving location — your warehouse address, store address, or kitchen address. Multi-location operators sometimes consolidate to a corporate identifier and create a compliance gap.
The compounding problem at outbound
Receiving captures lot in. Selling / shipping captures lot out. The match between in and out is what makes the chain traceable. If the receiving system records lots cleanly but the outbound system loses lot information at the cash register or at the dispatch dock, the chain breaks.
Most failures here are at the POS. A grocery cashier scanning a clamshell of berries doesn't typically capture which lot the clamshell came from. The lot lives in the inventory system; the POS sees only the SKU. Without a link between the SKU sold and the specific lot received, you can't tell which customer's berries came from the recalled lot.
The fix: your POS must be lot-aware. Either the system enforces FEFO at the lot level (the cashier sells the earliest-expiring lot first, the system records which lot), or the picker / packer records the lot at fulfillment for delivery and pickup orders.
The three-tier traceability architecture
A well-designed FSMA 204 traceability flow has three tiers:
Tier 1 — Capture at receiving. All 7 KDEs land in the inventory system, tied to the lot record.
Tier 2 — Maintain during storage / transformation. If the lot moves between coolers or gets repackaged, the system tracks the move. If you process the lot (cut romaine becomes packed salad mix), the new lot retains a parent-child relationship to the source lot.
Tier 3 — Capture at outbound. Whether sold at POS, shipped to a customer, or used as ingredient in a prepared food, the outbound transaction records which lot was used.
Three tiers, integrated into one system. That's the architecture that survives an FDA records request.
What to do if your supplier isn't passing the TLC
This is a common surprise. You discover during your FSMA 204 readiness audit that one of your suppliers isn't passing the TLC on their shipping documents. Three options:
1. Push the supplier. They're also subject to FSMA 204 (they're a supplier of an FTL food, so the rule applies to them). Ask them when they'll be passing the TLC. If they have a timeline, document it. If they don't, escalate.
2. Find an alternate supplier. If the original supplier won't comply, you may need to switch. The FDA isn't going to accept "my supplier doesn't pass it" as a defense.
3. Document the gap. While you're working on (1) or (2), document the gap and your remediation plan. This isn't compliance per se but it's evidence of good-faith effort, which matters in enforcement decisions.
Where ShelfLifePro fits
ShelfLifePro captures all 7 KDEs at receiving — manually, via Invoice OCR, or via EDI 856 ASN integration depending on your supplier setup. The lot record carries through storage moves and transformations with parent-child relationships. The POS enforces lot-aware FEFO. On records request, the sortable spreadsheet exports in one click with the FDA-required fields.
Free 14-day trial — run your KDE-capture audit on day one.
Related reading
ShelfLifePro Editorial Team
The ShelfLifePro editorial team covers inventory management, expiry tracking, and waste reduction for pharmacies, supermarkets, and retail businesses worldwide.
Capture all 7 KDEs at receiving — automatically
Invoice OCR captures lot, quantity, supplier, and reference document number in 1.8 seconds per page. Free 14-day trial.
Weekly expiry-tracking playbook
One short email every Tuesday. FEFO tactics, markdown math, and real-world waste-reduction wins. Unsubscribe anytime.
No spam. Unsubscribe in one click.