A recall is a race between your notice and the shelf. From the moment a defect is confirmed, every hour is another unit sold, dispensed or consumed, and the stock keeps moving while the paperwork forms up behind it.
The frustrating part is that the fastest channel you own is already deployed, printed on every pack in the field. It has simply been pointing at a static destination.
How a paper recall travels
The classic recall stack is a press notice, a regulator filing, distributor emails and a call centre. Every step is necessary, and every step loses fidelity. The distributor forwards a PDF, the wholesaler skims it, the retail counter misses it, and the person holding the pack reads none of it. Effort concentrates upstream. Risk concentrates downstream, in the hands of whoever opens the pack next.
The race is unfair by construction. A notice that takes a week to work its way to the counter competes with a product that sells through in a day.
The label becomes the notice
A dynamic code separates the printed artefact from what it resolves to. The square on the pack never changes; the resolution behind it is policy, and policy can change after the ink has dried. Point an affected batch at a recall notice and every label already in the field becomes the notice channel, surfacing at the exact moment someone attends to that specific pack: at the pharmacy counter, on the loading dock, at the kitchen table.
This is the principle secQR is built around: change without reprinting. Packs are printed weeks or months before a defect is known, so control has to live behind the code, in policy, where we can move it at the speed of the incident rather than the speed of a print run.
A hypothetical batch, walked through
Suppose a manufacturer confirms a stability failure in one batch of a humidity-sensitive tablet, weeks after that batch cleared the plant. In India the rails for the response already exist. Under Schedule H2 of the Drugs Rules 1945, the top 300 pharmaceutical brands have carried codes on their packs since August 2023, and the Drugs (Seventh Amendment) Rules 2026 extend the requirement to vaccines, anticancer and narcotic and psychotropic drugs from 1 July 2027, with antimicrobials following from 1 July 2028.
With a serialised estate, the recall becomes a scoped policy update. Scans of the affected batch resolve to a hold notice carrying the defect description and the return procedure. Every other batch resolves normally, so unaffected stock keeps selling and nobody destroys good inventory out of caution. If the failure only threatens stock shipped into humid coastal territories, the policy can scope by batch and geography together, leaving the same batch untouched where the risk does not apply.
A pharmacist scanning at the counter sees the hold instruction before dispensing. A patient scanning at home sees the same notice in plain language. Each scan lands in a tamper-evident log: which unit, where, when, and which version of the notice was served. That log changes the regulator conversation. A recall file built from courier receipts proves you sent notices. A scan log shows individual packs surfacing the notice, one interaction at a time, for as long as the batch keeps turning up.
What the code cannot do
Be honest about the limit. A code informs the person who scans it, and it pulls no stock off any shelf. Scan rates vary by category and by market, so the classic channels still run in full. The dynamic layer earns its place as the one channel that reaches individual packs and proves each contact.
A pack nobody scans is a pack nobody warned.
Precision is the quiet saving. Blanket recalls destroy good inventory because paper systems cannot tell batches apart once product leaves the dock. A batch-scoped policy can, which shrinks the recall to the units that deserve it.
The preparation happens before any incident: serialise at the line, keep batch metadata bound to each code, and rehearse the policy update the way you rehearse a fire drill. The teams that re-establish control fastest are the ones that chose the mechanism years before they needed it.
Regulatory summaries are for orientation only and are not legal advice.