What is a Key Data Element (KDE)?
Miss one KDE at receiving and a recall trace dead-ends at your dock, however good the rest of your records are.
Key Data Element (KDE)
KDE
A Key Data Element is a specific fact the FDA's Food Traceability Rule (FSMA 204) requires a firm to record at each Critical Tracking Event in a food's path, such as the traceability lot code, quantity, location and date. Together, KDEs are the records an FDA traceability request asks a firm to produce.
FSMA 204 names the events and the facts. Critical Tracking Events (CTEs) are moments like receiving, transformation and shipping, plus cooling and initial packing for some firms. At each event the rule lists the KDEs to capture. Receiving, for example, means recording facts like the traceability lot code, the quantity, the product, where it came from and when it arrived.
The elements chain together through the traceability lot code. The code assigned when a food is initially packed or transformed follows it through every later event, which is what lets one query walk a lot from supplier to customer.
Why KDEs decide whether a trace works
KDEs matter because FDA's test is production speed, not good intentions. When FDA requests records, a covered firm must deliver an electronic sortable spreadsheet of its KDEs within 24 hours. Every element missing at capture time becomes a blank cell in that spreadsheet, and a blank cell at receiving stops a trace-back cold.
Transformation is where most processors lose the chain. Combine three input lots into one batch, and the rule expects the output lot's records to link back to all three. Paper batch records and recipe spreadsheets hold the quantities but drop the linkage. That linkage is the difference between recalling one lot and pulling everything you shipped that month.
- ReceiveSupplier lot code, quantity, date captured.
- TransformOutput lot linked to every input lot.
- ShipCustomer, quantity, lot code recorded.
- FDA requestThe 24-hour clock starts.
- Spreadsheet outSortable, electronic, complete.
Each node is a Critical Tracking Event. The KDEs are what you write down at it.
Related questions
01What is the difference between a KDE and a CTE?+
A Critical Tracking Event is the moment; a Key Data Element is the fact you record at that moment. Receiving is a CTE. The lot code, quantity and date you write down at receiving are its KDEs. The rule defines both lists.
02What is a traceability lot code?+
A traceability lot code is the identifier a firm assigns when a covered food is initially packed or transformed. It is itself a KDE, and it is the thread that connects every later event's records back to that lot.
03Do KDEs still apply now that enforcement moved to 2028?+
Yes. The rule's requirements are unchanged; FDA's compliance and enforcement date moved to July 20, 2028. Many buyers already require lot-level traceability in supplier agreements, so the practical deadline is often a contract rather than the enforcement calendar.
Some of the systems we have shipped
Related
- What does FSMA 204 require, and by when? →The rule KDEs come from, end to end.
- Is FSMA 204 delayed again in 2026? →The real deadline, and who set it.
- How fast must you produce traceability records? →The 24-hour clock KDEs feed.
- Best food traceability software for small processors →Tools that capture KDEs without an ERP migration.
- Business process automation →The service behind capture-at-the-source record systems.
