🔒All inputs are processed locally in your browser. Nothing is transmitted, stored, or logged. Inputs disappear when you close the tab.

OCG-Industries Showcase · Cluster ⑫ Physical Supply-Chain and Goods Provenance

Food Traceability and
24 Hour Recall

Enter a lot's three critical tracking events, each an event type, a location, a traceability lot code, and a day, plus when the record was requested and when it was ready. This tool checks that the key data elements are complete on every event, that the lot code holds steady across the chain, that the events land in date order, and that the whole record was ready inside 24 hours of the request. A one-up one-down trace built this way is something you reconstruct from the record, not something a food safety lead reassembles by phone while the clock runs.

Data: 21 CFR Part 1 Subpart S (FSMA 204) · GS1 EPCIS 2.0

Critical Tracking Events STEP 1

Event 1

Event 2

Event 3

Request Clock STEP 2
Hour zero, your own reference point
Use -1 if the records are not ready yet
Status
—
Traceable, or the first failing reason
Missing KDEs
—
Across all three events
Response Hours
—
Ready hour minus request hour
Detail
KDE missing count—
Lot code consistent—
Chronology ok—
Request hour index—
Records ready hour index—
Response hours—
Within 24 hours—
Status—
Policy Mandate v2.0 · what is this?

Exhibit: a worked example that computes in your browser. It is not regulatory-grade output. Source card on AINumbers: industry card c12-2.