Recall communication has a reach problem: press releases, retailer emails and news coverage all miss the person who matters most, the one holding the affected item, at the moment they are about to use it. The pack itself is the only channel guaranteed to be present at that moment, and once its code resolves through you, it becomes exactly that channel.
Why traditional recall reach is so poor
Recalls compete for attention in media the affected household may never see, then depend on the shopper connecting a vague product description to the specific item in their pantry. Every step leaks. The scannable pack removes the identification problem entirely: the item names itself, batch and all, and the answer is specific to it.
What the scan-time recall looks like
A shopper scans a pack from an affected lot and, instead of the product page, sees the notice: what happened, in the brand's own words, what to do, and where the official reference lives, in the shopper's language. A shopper scanning an unaffected lot sees the ordinary page, no fear where none is due, which is the precision argument of batch-level recalls. Machines are first-class too: tills and warehouse systems reading the code get recalled status as structured data, so quarantine can be automatic.
The trust mechanics
Handled this way, a recall is also a demonstration: the brand that can tell you precisely whether your jar is affected looks more competent, not less, than the brand issuing blanket warnings. Scan analytics close the loop, showing how many affected-lot scans saw the notice, evidence of communication effectiveness that a press release can never produce, and a metric regulators and retailers understand instantly.
Preparing the channel before you need it
The prerequisites are all ordinary Sunrise-era work: lot codes printed inside the Digital Link, lots registered as they are produced, and a rehearsed raise-and-lift, one API call each way, documented in the reference. Food brands aligning with FSMA 204 already maintain the lot identity; pointing the same identity at the consumer is the free second use.
Common questions
Is the pack really a recall channel?
Once the code resolves through you, yes: it is the one communication surface guaranteed to be in the hand of someone holding the affected item at the moment of decision.
What should a recall notice actually say?
The reason in plain language, the action to take, and a reference or link to the official notice. On Onpack the words are the brand's own; legal weight demands human-written text.
Do machines get told too?
Yes: machine scans receive the recall as structured data on a 200 response, plus a warning header, so inventory systems can quarantine automatically.
How fast does a recall propagate to packs?
Immediately: the next scan of an affected item sees the notice. There is no reprint, no app push, no delay beyond the scan itself.