FDA sanitary-transport scope is more than sensor data
FDA's final rule covers named actors, vehicles and equipment, transportation operations, training, records, and waivers. A temperature reading can support the record but cannot decide scope or compliance by itself.
Editorial figure by Food Traceability Ledger. Source context: FDA — FSMA Sanitary Transportation Rule.
Scope begins with actor, activity, food, and mode
FDA's public rule page names shippers, loaders, carriers by motor or rail vehicle, and receivers. It also describes geographic and transport-mode boundaries, including treatment of certain import, export, and through-shipment situations.
A system therefore needs more than a shipment number and a device reading. The coverage record should preserve the food, activity, actor role, route, vehicle or rail movement, responsibility agreement, exception or waiver, and the point at which the covered U.S. transportation activity begins or ends.
Sanitary practice has several evidence classes
FDA groups the rule around vehicles and equipment, transportation operations, training, records, and waivers. Its examples include suitability and cleanability, temperature capability, separation and contamination controls, carrier-personnel training, and written procedures or agreements.
Those facts may live in fleet, warehouse, quality, training, contract, carrier, sensor, and document systems. A traceability platform can link the evidence, but it should not compress distinct responsibilities and records into a single condition flag.
Temperature is evidence, not the disposition
A temperature record can show what a device observed at a time and location under a stated calibration, placement, sampling, and data path. It does not alone establish the required condition, the complete shipment history, the source of a deviation, the safety of the food, or the appropriate disposition.
Buyers should test how the system joins sensor readings to the food and lot, vehicle or equipment, loading and receipt events, actor responsibilities, agreed conditions, alarms, investigations, decisions, and corrections. Missing or conflicting data should remain visible rather than becoming an automatic pass.
Traceability and sanitary transport answer different questions
Traceability can connect identities, quantities, locations, partners, and events. Sanitary-transport evidence asks whether covered actors and activities used the required practices and maintained the relevant training, procedure, agreement, and operational records.
The two domains can share shipment, lot, partner, location, time, and condition data while retaining separate authority, scope, and decisions. That separation lets teams investigate a condition issue without misrepresenting a trace event as a compliance finding or a compliance record as complete lot genealogy.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.