Shelf-Side Food Recall Check
Scan a food package at the shelf to check official recalls against its barcode and, when needed, its lot details, then get a clear next step.
At the grocery shelf, or just after seeing a recall in the news, a shopper opens the camera and scans a food package barcode. The product first matches the barcode against official recall databases; if the notice is limited by size, lot number, or production date, it immediately highlights the line of package text that needs another photo.
Once recognition is complete, the screen gives only three clear outcomes: recall matched, no current match, or insufficient information. For a match, it shows the official instruction to return, discard, or contact the relevant party, and creates an evidence page with the notice link, product details, and lot number that the shopper can show directly to store staff.
The recall database updates from regulator notices, and every result retains the corresponding notice version and lookup time. When a lot number is blurry, packaging is reflective, or the recall scope is incomplete, the product asks for another photo rather than labeling a guess as safe.
The initial version covers barcoded prepackaged foods and major official recall sources. It does not replace medical advice, assess unpackaged goods, or infer safety from a product category; it makes the lot-number check most easily missed at the shelf into one explicit action.
Why now
A September 1 post on r/AppBusiness explicitly asks whether an app exists that scans grocery barcodes and tracks food recalls. Comments suggest there is no mature solution: a barcode-led grocery workflow that surfaces current official food recalls at the shelf while clearly handling recall details that may depend on product variant, package information, or lot information beyond the barcode. S1 This is a single-post observation of user friction, not evidence of a trend or market size.