A code on a pack can carry its lot: 01/00860001234567/10/A42 says this product, lot A42. Your product page can read that. Add a recall block, name the lots, and a shopper holding one of those jars sees the notice at the top of the page. Everybody else sees the page they always saw.
Why this beats re-pointing a link
The other way to run a recall is to point that lot's link away from your page entirely, at a notice you host somewhere else. That works, and it is still there if you want it. But it means writing a second page in a hurry, it loses everything the product page already said, and it takes the lot off your own address.
A recall block keeps the page and grows a banner on it. There is one page to maintain, and the notice sits above the ingredients rather than instead of them.
Adding one
- 1Open the product's Page tab
Products, the product, Page.
- 2Add a block, Recall notice
It is under Reads the scan, with the authenticity block.
- 3Write what happened
What the problem is, and what somebody holding this pack should do. Plain words. They are standing in a kitchen.
- 4Name the affected lots
Exactly as the code carries them. Case does not matter and stray spaces are ignored, but a different lot code is a different lot.
- 5Add a button if you have somewhere to send them
A refund form, a contact page. Optional.
- 6Simulate the scan before you publish
Beside the preview there is a box for a lot. Put the affected one in and the preview becomes the page that pack gets. This is the only way to see a recall notice before it is real.
- 7Publish
The next scan of an affected pack gets it. Nothing else changes.
Tip. The notice is always drawn first, whatever order the blocks are in. Somebody holding a recalled pack has to see it before anything else, so that one is not a choice.
The pack has to carry the lot
Heads up. None of this fires if the printed code is the GTIN alone. The lot has to be in the address, as the /10/ segment, and that is decided at artwork time.
Nothing is reprinted once it is: the lot is already in the code, and the page simply starts reading it. But a run printed without one scans identically on every pack, and no notice can reach only the affected jars.
https://id.yourbrand.com/01/00860001234567/10/A42
When it is over
Delete the block, or empty the list of lots, and publish. The next scan of those packs gets the normal page. There is nothing cached and nothing to undo.
Keep any notice page you linked to online, though. Printed packs stay in circulation for years, and an address that 404s looks worse than the recall did.
Ready to make your own QR code?
Free QR codes rendered as you type, no signup to try. Premium makes them dynamic for $4 a month.
Still stuck? Search the help center, or contact support and a person will answer.