Publishing a recall notice

What it does

Publishing a recall notice changes what a printed code answers. Nothing about the label or the symbol on it changes; what changes is where a phone or a scanner is sent when it reads that symbol.

You choose the affected grain — a whole product, one batch, or one individual unit — and from that moment every scan that resolves to it lands on the notice.

Exactly who it reaches

People who scan the code. Nobody else.

It does not notify a regulator. It does not notify your retailers, your distributors or anybody in your supply chain. It is not a filing, and it is not a substitute for one. Those obligations are real, they vary by market and category, and they are yours.

We are precise about this because the alternative is a brand assuming a button did something it did not do, at the worst possible moment.

Why it writes two links, not one

A recall notice writes two links to every affected grain: the recall link itself, typed so a machine can ask for it by name, and an override of that grain’s default link.

The second one is the one that matters, and it is easy to miss. Link shadowing works per type: a batch-level link of one type does not displace links of other types. So a recall link on its own would be reachable to anything that asked for a recall specifically — and a plain phone-camera scan, which asks for nothing in particular, would still land on the ordinary product page and never see the notice.

Both links get written every time, and a notice with only the first of them would look published from the dashboard while a shopper’s camera carried on reaching the ordinary product page.

What it costs

Nothing, on every plan, including the free one.

The recall flow is never gated, never throttled, and never carries an upgrade prompt at any point. It creates whatever batch records it needs to work even when batch management is a paid feature on your plan. A product under an active recall is exempt from fair-use degradation and from the Starter throttle for as long as the recall is active.

A safety action that a billing state can interfere with is not a safety action.