How do you calculate recall exposure?

Multiply suspect units × handling cost per unit × defect prevalence%, then add the admin adder. For 8,000 units at $22 each with 35% prevalence plus $15,000: 8,000 × 22 × 0.35 = $61,600 variable + $15,000 = $76,600 total.

What is the cost per suspect unit?

Total exposure divided by units in the window. Here $76,600 ÷ 8,000 = $9.575 per suspect unit — the blended cost you carry across every unit in the window, defective or not.

How does traceability reduce recall exposure?

Better genealogy narrows the suspect window. Halving the 8,000-unit window roughly halves the variable cost, which is why coverage directly drives recall risk.

What is confirmed defect prevalence?

The share of suspect-window units actually defective. At 35%, roughly 2,800 of 8,000 units are truly affected; the rest inflate the window because you cannot isolate them.

Why is there a fixed admin adder?

Notifications, regulatory filings, and recall coordination cost the same whether the window is 8,000 or 80,000 units. The $15,000 adder captures that flat overhead.

Exposure radius vs actual recall cost — are they the same?

This is a planning estimate. Actual cost adds brand damage, litigation, and lost sales, which sit outside this model but often dwarf the handling figure.

Traceability, Serialization & Lot Genealogy calculator

Recall Exposure Radius Calculator

Recall exposure radius estimates the financial size of a recall event based on how many units fall inside the suspect window, what it costs to handle each affected unit, and the confirmed defect prevalence within that window. Quality directors, risk managers, and recall coordinators in food, pharma, and consumer products use it to compare scenarios: tight traceability shrinks the suspect window and the bill, while poor genealogy forces a wide window and a large one. It reframes traceability investment as recall-cost avoidance. The per-suspect-unit output also shows the blended cost you carry even for units that turn out fine.

What this calculator does

Estimates the financial exposure of a recall based on the suspect unit window and confirmed defect prevalence.
A quality director uses it to size recall exposure when traceability data defines the affected lot window.
It computes total recall exposure as suspect units × per-unit handling cost × defect prevalence, plus a fixed notification/admin adder, and the cost per suspect unit.

Formula used

Recall exposure = suspect units x handling cost per unit x defect prevalence% + admin adder
Cost per suspect unit = recall exposure / suspect units

Inputs explained

Units in suspect window:
Recall handling cost per unit:
Confirmed defect prevalence:
Notification and admin adder:

How to use the result

Use it to size a potential recall, compare a narrow versus wide suspect window, or justify traceability spend.
It uses a single average handling cost and one prevalence rate — real recalls have tiered logistics costs and prevalence that varies by lot or region.

Common questions

How do you calculate recall exposure? Multiply suspect units × handling cost per unit × defect prevalence%, then add the admin adder. For 8,000 units at $22 each with 35% prevalence plus $15,000: 8,000 × 22 × 0.35 = $61,600 variable + $15,000 = $76,600 total.
What is the cost per suspect unit? Total exposure divided by units in the window. Here $76,600 ÷ 8,000 = $9.575 per suspect unit — the blended cost you carry across every unit in the window, defective or not.
How does traceability reduce recall exposure? Better genealogy narrows the suspect window. Halving the 8,000-unit window roughly halves the variable cost, which is why coverage directly drives recall risk.
What is confirmed defect prevalence? The share of suspect-window units actually defective. At 35%, roughly 2,800 of 8,000 units are truly affected; the rest inflate the window because you cannot isolate them.
Why is there a fixed admin adder? Notifications, regulatory filings, and recall coordination cost the same whether the window is 8,000 or 80,000 units. The $15,000 adder captures that flat overhead.

Last reviewed 2026-05-12.