It's 2pm Friday. Your tomato supplier just called.

The recall coordinator at your distributor has already stopped shipments. FDA wants lot-level records within 24 hours — where it came from, where it went, who touched it. You have three co-manufacturers, four finished-goods SKUs, and product in 47 retailers across 11 states. How much is in the channel?

$10M+

average cost of a food recall — before attorney fees or brand damage

The brands that survive a recall already know exactly where every lot went. The ones that don't are building their traceability system with an FDA investigator in the building.

The blast radius depends entirely on how your lots are linked

Scenario B is not a bigger version of Scenario A

Scenario A is containable. One ingredient lot, one production batch, three retailers. You can run that recall in a day with a spreadsheet. The product cost is low. The notification list is short. This is the scenario brands imagine when they think "recall."

Scenario B is what actually happens when a shared-ingredient lot touches multiple production runs. The same chili flakes lot went into your hot sauce on Monday, your spice blend on Wednesday, and your seasoning mix the following week — because your co-manufacturer ran three separate batches from the same pallet.

The result: 23 affected lots, 14 SKUs across five product lines, 6 retailers to notify, 5,785 cases still in channel. That is 47× the blast radius of Scenario A — from one shared ingredient lot.

The difference between Scenario A and Scenario B is not ingredient risk. It's whether you know, at the moment the call comes in, which batches shared that lot. Most brands don't know. The genealogy data isn't there.

Scenario B — product retrieval cost

$52K–$81K

cases recalled × avg. case value

vs.

Full recall — industry average

$10M+

product retrieval + logistics + testing + legal + PR + shelf recovery

against

Cinderhaven annual EBITDA (est.)

~$2.75M

11% EBITDA × $25M revenue — a full recall wipes out 3+ years

FSMA 204 compliance — July 20, 2028

Section 204 of the Food Safety Modernization Act requires traceability records for high-risk foods at each Critical Tracking Event (CTE). The table below maps FDA's required Key Data Elements (KDEs) against the data Cinderhaven already captures. The blast-radius graph above is built from these same records.

CTE	FDA KDE	Cinderhaven record	Status
Receiving (ingredient lots)
	Traceability lot code (TLC)	`ingredient_lot_id`	Captured
	Commodity / product description	`ingredients.name`	Captured
	Quantity and unit of measure	`quantity_kg`	Captured
	Supplier / shipper location	`supplier_id`	Captured
	Receipt date	`received_date`	Captured
	Reference document (BOL / PO)	—	Planned
Transformation (production batches)
	New TLC assigned	`fg_lot_id`	Captured
	Input TLCs used	`batch_ingredient_map`	Captured
	Transformation date	`production_date`	Captured
	Location of transformation	`co_packers.name`	Captured
	Product description (output)	`products.sku_id`	Captured
	Quantity (output)	`units_produced`	Captured
Shipping (finished goods lots)
	TLC shipped	`shipment_lot_id`	Captured
	Quantity and unit of measure	`cases_shipped`	Captured
	Recipient name and location	`retailers.name`	Captured
	Ship date	`ship_date`	Captured
	Reference document (BOL)	—	Planned

FSMA 204 compliance deadline: July 20, 2028 (FR Doc. 2025-14967 + Continuing Appropriations Act of 2026). Applies to FDA-regulated foods on the Food Traceability List (FTL). Hot sauces and spice blends are not on the current FTL; upstream fresh ingredients may trigger requirements at the receiving CTE.

Traceability readiness — ten questions

Most small food brands cannot answer all ten of these questions in under an hour. A brand that can is ready for FSMA 204 and for the Friday 2pm call.

Can you produce a complete lot genealogy within 24 hours?

FDA expects records on demand. "We're pulling it together" is not a defensible answer.

Do you capture ingredient lot codes at every receiving event?

If your receiving dock logs "chili flakes from Supplier A" but not the specific lot code, you cannot trace forward.

Do your co-manufacturers provide batch records that link input lot codes to output lot codes?

This is the Transformation CTE. It's where most small brands have a gap — the co-packer has the data, but no one ever asked for it.

Do your finished goods lot codes match what appears on the label?

Your ERP might track one format; the label says another. FDA traces from the label.

Can you identify every retailer and distributor that received a specific FG lot?

Ship-to records at the case-lot level — not just the order or the SKU. Distributor breaks into sub-lots that need to be tracked separately.

Do you know which lots are still in channel vs. sold through?

You can't scope a recall without this. Sell-through velocity by retailer tells you which cases are retrievable vs. already consumed.

If one ingredient lot was used across multiple production runs, do you know which ones?

This is Scenario B. The answer determines whether your recall is $52K or $10M.

Is your traceability data in a system, or in spreadsheets scattered across three inboxes?

FDA can request records going back two years. "We think we have it on Dropbox" fails the test.

Do you have a recall SOP that names the data systems, the record owners, and the 24-hour response plan?

The SOP doesn't run the recall — but it determines how fast you can. Every hour of delay widens the blast radius.

Have you run a mock trace in the last 12 months?

A trace drill — pick a lot code, run it forward, produce the full notification list — is the only way to verify the system works before the real call comes.

Data for this tool uses seed=400 (Cinderhaven Provisions genealogy, synthetic). Recall cost floor: Deloitte/GMA/FMI (2010), conservative. FSMA 204 deadline: July 20, 2028.