The QR code on your packaging: duty and opportunity
The QR code on packaging is overrated and underrated at the same time. Overrated, because a blanket QR obligation from 2026 simply does not exist — and is sold regularly anyway. Underrated, because when the code does come, it is the first digital channel a brand still owns after the sale. This article separates the two: first what genuinely becomes mandatory and when, then what belongs behind the code so that an obligation turns into a channel.
- QR obligation in 2026
- does not exist — the code is a permitted but optional addition
- Physical from 12/08/2026
- identification mark and manufacturer details on the packaging (Art. 12)
- Harmonised material label
- 12 August 2028 at the earliest, subject to the implementing act
- Reusable packaging labelling
- 12 February 2029 at the earliest — here the digital data carrier is mandatory
- Digital Product Passport
- via the ESPR, Regulation (EU) 2024/1781, by product group from 2027
- Technical requirement
- open standard, machine-readable, scannable without an app
What genuinely becomes mandatory — and when
The sober starting point first: for general packaging labelling, Regulation (EU) 2025/40 (the PPWR) does not prescribe a QR code. Since 12 August 2026 an identification mark for the packaging and full manufacturer details have to be present — name or brand, postal address, electronic contact details. Those details belong physically on or attached to the packaging; a code alone does not replace them. Anyone selling you a QR rollout today as a “PPWR obligation from 2026” should be able to name the article.
The digital data carrier becomes mandatory in stages and in special cases. The harmonised EU material label and the labelling of recycled content in plastics bite on 12 August 2028 at the earliest — the pictograms themselves are only set by the Commission through an implementing act. For reusable packaging, a digital data carrier becomes a mandatory part of the labelling from 12 February 2029 at the earliest. Running in parallel is the Digital Product Passport under the Ecodesign Regulation (EU) 2024/1781 (ESPR), which is introduced product group by product group and attaches to the product, not the packaging.
Identification mark and manufacturer details on the packaging. A QR code is permitted, but optional and no substitute.
Harmonised labelling — at the earliest, subject to the implementing act. From here on, space on the surface gets tight.
For reusable packaging the digital data carrier becomes a mandatory part of the labelling.
Via the ESPR, product group by product group through delegated acts. Hits earlier or later depending on your range.
Why the code is coming anyway
The deadlines are one thing, the physics of the packaging surface another. With every stage the volume of mandatory information grows — material composition, recycled content, sorting guidance, origin details, product-specific evidence — and in every language of the markets you sell into. On a folding carton for cosmetics or an A6 card set that space does not exist. The digital data carrier is therefore not primarily a rule but the only solution to a surface-area problem.
On top of that comes a second argument that often weighs more heavily in packaging projects: content behind a code can be changed without reprinting. If an implementing act sharpens a requirement in 2028, printed information means reprinting the whole run — behind the code it is an update. Anyone ordering cartons today is implicitly deciding how expensive the next rule change will be.
The problem with the black-and-white PDF
And here is where the real mistake happens in practice. The code is treated as a compliance task and handed to whoever assembles the mandatory information. The result is a link to a PDF: black and white, unformatted, not built for a phone. Technically correct, commercially absurd.
Set it against the alternative for a moment. A mid-sized consumer brand spends a five-figure sum on a social-media campaign — for content with a half-life of 24 to 72 hours. The QR code on the packaging, by contrast, costs practically nothing to produce, sits physically in the customer’s home, is present for weeks and gets scanned at exactly the moment someone is actively engaging with the product. There are few contact points with a better ratio of cost to attention — and practically none that brands give away as consistently.
The quiet wrong turn
Hand the mandatory code to the documentation side and the channel is gone before anyone in marketing knew it existed. Undoing that has to wait for the next print run — at order volumes in the six- to seven-figure range, that means years.
Two layers behind one code
The clean architecture separates what the regulation demands from what the brand wants — and serves both from the same address. The mandatory layer has to be machine-readable, standardised and permanently reachable, because in time it will be read by authorities, trading partners and sorting plants. The experience layer is built for people and may do anything a product page may do.
Mandatory layer — for systems
- Material composition and sorting guidance, structured rather than as prose
- Recycled content and the evidence behind it
- Manufacturer details and the identification mark
- Product-specific mandatory information depending on sector and legal framework
- Machine-readable via an open standard, without an app, permanently at the same address
Experience layer — for people
- A digital manual instead of a leaflet — changeable, multilingual, with video
- Brand and origin story at the point of use rather than in an advert
- Interaction: guided onboarding, quiz, community access, registration
- Reorder, accessories, refill — right where the product is in someone’s hand
- Service: take-back, repair, disposal guidance, contact
The appeal lies in the overlap: what you have to publish anyway creates a channel you would otherwise have to buy reach for. The obligation pays for the access, the brand fills it. That is precisely why the question of who owns the code inside the company is not a matter of org chart but of strategy.
Timing decides more than the concept
The hardest constraint in these projects is not technology but the print run. Anyone who has just bought a batch in the millions cannot change the packaging at short notice — the stock is in the warehouse, and a reprint destroys the volume discount the batch was ordered that large for in the first place. With smaller runs the maths looks different: there the next order is due in a few months anyway, and the code costs nothing extra to print.
The label as an interim step
For existing stock a stuck-on code is the pragmatic answer — often already part of the finishing step, for instance where batch or price labels go on anyway. It works at manageable volumes and where you pack yourself or ship through a provider with flexible finishing. At million-unit batches on an automated line it does not: there the label reaches into the supply chain, and a marketing idea turns into a process project with three more parties involved.
What to settle now
- Date the next print run. That is the real window — not the statutory deadline.
- Settle ownership before the print files are signed off. If the code sits with documentation alone, you get the PDF.
- Fix a permanent address structure. A code on a 2027 packaging still has to resolve in 2035 — the URL structure is an architecture decision, not a campaign decision.
- Maintain mandatory and experience content separately but serve them together. Only that keeps the mandatory layer machine-readable while the experience layer is free to change.
- Commit to an open standard. A code that requires an app or points at a single vendor does not meet the purpose of the regulation.
- One product first. Working one product line through completely teaches more than a concept for the whole range.
Note
The dates named depend on the adoption of the respective delegated and implementing acts and may shift. This overview is not binding legal advice.
Talk to us
Build the mandatory information in a structured way
Before the code gets an address, it needs content. We collect the evidence from your supply chain and produce the mandatory documents from it — on a data basis that later feeds the experience layer too.
Discuss the approach
