Food Recall Lot Reconciliation: Explain Shipments, Stock, and Missing Joins

Define the affected product, lot, source context, and notice evidence precisely. A commodity match is a review lead, not proof every product in the category is affected.

Retain the notice version and capture time separately from internal records. A public notice cannot replace actual receipts and shipments, and a notice correction should not rewrite historical operational evidence.

Explain received quantities using shipments, remaining stock, processing inputs, returns, waste, and other dispositions. State units and conversion rules: case counts cannot be compared directly with individual units.

Follow transformation relationships before listing recipients. Stopping at the processing step can omit buyers who received outputs derived from the affected source lot.

Include an unresolved bucket for shipments and receipts with missing lot joins. Missing evidence is not evidence that those records are unaffected.

Test repeated lot strings from different sources and a missing shipment allocation. Distinguish supported affected records, evidence-backed exclusions, and unresolved follow-up.

FoodChainAPI suggests candidate Food Traceability List categories from product descriptions. Save the reviewed result beside the product specification; a category match does not establish exemptions, complete operational records, or certify compliance.