Reportable Food Registry

The Reportable Food Registry is FDA's electronic portal — operating since September 2009 — for industry mandatory reporting of food and dietary supplement safety issues that present a reasonable probability of serious adverse health consequences or death (SAHCODHA). The registry is the upstream notification gate that triggers FDA recall coordination, distribution-chain notification, and public-health follow-up. Submission is made via the FDA Industry Systems portal; the submission generates a unique CRFR number that tracks the event through closure.

RFR reporting is triggered when there is reasonable probability that use of, or exposure to, the food will cause serious adverse health consequences or death. The threshold is risk-based; SAHCODHA does not require that any consumer has actually been harmed. Specific scenarios that trigger reporting:

• Undeclared major allergen (FALCPA 9 allergens) above action level — most common reportable event in supplements.
• Pathogenic microbial contamination — Salmonella, Listeria monocytogenes, E. coli O157:H7, Cronobacter sakazakii (infant formula).
• Above-action-level mycotoxin contamination — aflatoxins above 20 ppb.
• Above-action-level heavy-metal contamination — lead, arsenic, cadmium, mercury at levels presenting acute toxicity risk.
• Pharmaceutical adulteration — undeclared pharmaceutical compound in dietary supplement (e.g. PDE-5 inhibitor in sexual-enhancement product).
• Foreign-object contamination — glass, metal, hard plastic at levels presenting choking / laceration risk.
• Mis-labelled potency presenting overdose risk — e.g. supplement labelled '100 mg' but actually containing '1000 mg' of an active with narrow safety margin.
• Tampering or sabotage — credible evidence of intentional contamination.
• Significant temperature-abuse event in refrigerated supplement — if the failure mode presents pathogenic-growth risk.

The 24-hour clock begins when the responsible party becomes aware that the food / supplement is reportable. 'Responsible party' is defined as the person who submitted facility registration under §415 — typically the manufacturer or U.S. agent. The clock is not subject to extension; weekends and holidays count. Pragmatic timeline within the 24-hour window:

• Hour 0 — Discovery (incoming test result, consumer complaint, regulator notification, internal investigation finding).
• Hours 0-4 — Internal triage: confirm the finding is real (rule out lab error, mis-attribution), determine scope (which lots, which distribution, which consumer-facing SKUs), determine reasonable-probability assessment.
• Hours 4-12 — Stakeholder alignment: QA + Regulatory Affairs + Senior Officer + Legal align on classification (Reportable / Not Reportable); decision documented.
• Hours 12-20 — Submission preparation: factual record of the finding, lot identification, distribution scope, contact information, recommended corrective action.
• Hours 20-24 — Submission via FDA Industry Systems portal; CRFR number received and recorded.
• Post-submission — FDA reviews; may request supplementary report; recall coordination engages if appropriate.

• FDA Recall Coordinator engagement — Recall Coordinator from FDA District Office typically engages within 24-48 hours of submission to discuss recall scope, classification, and timing.
• One-up / one-down notification — FDA may require the submitter to notify immediate suppliers (upstream) and immediate customers (downstream) within the distribution chain.
• Public-facing disclosure — most CRFR submissions become public via the FDA Annual RFR Report and via the recall enforcement report (if recall is executed); brand-name disclosure typically occurs at recall execution stage.
• Recall classification — FDA classifies the resulting recall as Class I (serious or fatal), Class II (temporary or reversible), or Class III (unlikely to cause adverse health consequences). Class I almost always follows from a SAHCODHA-triggered RFR.
• Reportable-food regulator data sharing — FDA shares RFR data with state regulatory partners, international counterparts (Canada CFIA, EU RASFF) where applicable.
• Trend analysis — FDA Annual RFR Report identifies trending hazard categories (e.g. undeclared allergens, Salmonella in specific commodities); industry uses for risk-based qualification of suppliers and processes.

• Under-reporting borderline events — internal classification deems 'probably not reportable'; consumer harm later emerges; investigation reveals reportable-threshold met. Most common §301(e) violation.
• Missing the 24-hour clock — internal escalation slow; submission filed at 30-48 hours. Even short delays are violations.
• Incomplete submission — missing distribution scope, missing lot identification, missing supplier information; FDA requests supplement; clock for supplementary report starts.
• Wrong responsible party — submission filed by brand when contract manufacturer is the §415 registrant; submission filed by contract manufacturer when brand is the registrant. Quality agreement should explicitly allocate.
• Failure to notify one-up / one-down — submitter files RFR but does not notify immediate supplier (potential common-cause investigation) or immediate customer (downstream distribution).
• Delayed escalation — QA discovers the issue but does not escalate to Regulatory Affairs / Senior Officer in time to make the 24-hour window. Internal SLA must be sub-12-hour from QA discovery to officer notification.
• Single-instance under-investigation — single consumer complaint dismissed as anomalous; investigation reveals systematic issue; reporting clock was triggered at first complaint, not at investigation conclusion.
• RFR confused with consumer AE reporting (DSNDCPA) — different regimes, different triggers, different portals; submission to wrong portal does not satisfy the other obligation.
• Lack of officer-level training — corporate officers unaware of strict-liability exposure under §303 for §301(e) violations; insufficient leadership engagement during 24-hour window.

• Reportability classification at intake: every quality event (OOS, complaint, deviation, recall trigger) auto-classified for SAHCODHA reportability using configurable risk-matrix; Reportable / Not Reportable / Under Review status.
• 24-hour clock: Reportable status starts visible countdown; auto-escalation at configurable thresholds (2 hour Reg Affairs, 4 hour Senior Officer, 8 hour Officer); breaches logged.
• Submission package auto-generation: pre-populated submission package using existing data — lot scope from genealogy, distribution scope from sales records, contact info from facility register, causal analysis from investigation report.
• One-up / one-down notification: V5 surfaces upstream supplier list (from BOM + receiving records) and downstream customer list (from sales records) for the affected lots; one-click notification workflow with template messaging.
• CRFR number tracking: after submission to FDA portal, CRFR number entered into V5; status tracked through FDA Recall Coordinator engagement, recall classification, recall execution, recall closure.
• Recall pre-flight integration: Reportable status auto-engages recall pre-flight engine; forward-models distribution exposure + downstream-recovery scenarios + media-communication preparation.
• Regulatory-officer dashboard: real-time view of all open Reportable events, 24-hour-clock status, escalation log, CRFR number, FDA-engagement status; supports officer-level oversight required under §303.
• DSNDCPA / RFR distinction: workflow asks correct-portal question at intake; events that satisfy both regimes generate parallel submissions to correct portals.
• Post-submission supplementary report: workflow generates supplementary report when new information emerges (additional lots, additional distribution states, completed root-cause analysis); submitted via FDA portal with linkage to original CRFR.
• Annual RFR Report cross-reference: V5 cross-references the publicly-published FDA Annual RFR Report for trending hazard categories; supports brand's risk-based supplier qualification programme.
• Officer training tracker: corporate officers training on RFR strict-liability exposure tracked; certification renewal cycle enforced.