Ecommerce & retail
QR codes for ingredients and allergen information
A QR code may supplement ingredient and allergen information but never replace it: EU food information law and FDA labelling rules require the declarations on the pack itself. Use the code for depth the label cannot hold: full sourcing, per-batch data, precautionary detail and recall communication.
The line you must not cross
Start with the compliance fact, because everything else is downstream of it: mandatory food information must appear on the pack. In the EU, the Food Information to Consumers regulation requires the ingredient list (with the 14 regulated allergens emphasised within it) directly on the label. In the US, FDA labelling rules likewise require ingredient and major-allergen declarations on the package. A QR code is not an accepted substitute for either, and "scan for allergens" as the only route is both non-compliant and dangerous: the person with the anaphylaxis risk may have no phone, no signal, or thirty seconds in a shop aisle.
So the design rule is fixed: the code supplements, the pack declares. Everything on this page assumes the printed declaration is already correct and complete. This is the food-specific case of a general principle: see when not to use a QR code.
What the code is genuinely good for
The printed label is size-constrained and frozen at print time. The linked page is neither, which makes it the right home for:
- Full ingredient depth: sub-ingredients of compound ingredients, sourcing and origin per ingredient, certifications (organic, kosher, halal) with certificate numbers rather than just logos.
- Precautionary detail: the reasoning behind a "may contain" statement: which line, what cleaning protocol, what testing. Precautionary labels are blunt instruments; allergic consumers value the detail behind them.
- Per-batch information, if the code is batch-level (a GS1 Digital Link carrying GTIN plus batch), the page can show data for that batch: supplier lot, production date, test results.
- Reformulation history, "the recipe changed in March 2026: added milk protein" is exactly what a repeat purchaser with an allergy needs and the label cannot say.
- Languages: the pack carries the market's mandated language; the page can carry thirty.
The recall channel
The under-used case: when a product is recalled for an undeclared allergen (one of the most common recall causes) the batch-level code on pack becomes your direct channel. The landing page flips to a recall notice for affected batches, and someone standing in their kitchen holding the product can check their unit in ten seconds instead of parsing a press release's batch ranges. This only works if the code encodes or asks for the batch, which is the argument for batch-level codes over one generic per-SKU URL; serialisation covers the mechanics.
Practical notes
- Place the code near the ingredient declaration, labelled ("Scan for full ingredient and sourcing detail"), at ≥ 2 × 2 cm with a clean quiet zone; food packs are busy and the packaging rules on creases, gloss and curvature all apply.
- The landing page must be fast, real HTML (screen-reader accessible), and must not demand an app or a cookie wall before showing allergen data.
- Keep the URL stable for the product's shelf life plus pantry life, tins outlive campaigns by years.
- Nutrition data behind a code is the sibling use-case and usually shares the same landing page.
FAQ
Can allergen information be provided only via a QR code?
No. EU food information law and FDA labelling rules require ingredient and allergen declarations on the pack itself. A QR code may add depth but cannot be the only route, for legal reasons and because the at-risk shopper may have no phone or signal.
What allergen detail should go behind the QR code?
The reasoning behind precautionary statements, sub-ingredient and sourcing detail, certification evidence, per-batch production data and reformulation history, the things a size-limited printed label cannot carry.
Can a QR code help with food recalls?
Yes, if it is batch-level. The landing page can show a recall notice for affected batches, letting a consumer check their exact unit in seconds. A generic per-product URL can only show a general notice.
Where should the code sit on a food pack?
Next to the ingredient declaration, clearly labelled, at 2 × 2 cm or larger with a full quiet zone, away from creases and seams. The linked page must load fast and expose the information without an app or sign-in.
Try it: free, no signup
Related
- QR codes for nutrition information, Extended nutrition data behind a QR code, per-portion calculators, diet filters, the smart-label pattern, and honest expectations about scan rates.
- QR codes on product packaging, A packaging QR code has to work for as long as the product exists, which makes permanence the design constraint rather than size. Point it at a stable…
- QR codes for serialised products, Unit-level codes done right: opaque serials resolved server-side, GS1 SGTIN framing, batch generation at production scale, and the use-case stack.
- When not to use a QR code, Do not use a QR code where the audience is moving, where a tappable link already exists, where it would be the only route to essential information, or…