A grower-producer in Alsace bottled her 2019 Riesling Grand Cru to lay down. Riesling of that quality is built to age — fifteen, twenty years in a good cellar before it hits its window. She did everything the new rules asked. Since December 2023, EU Regulation 2021/2117 requires wine sold in the Union to disclose its full ingredient list and nutrition declaration, and lets producers move most of that off the physical label and onto a digital “e-label” reached by a QR code. So onto the back label went a QR. She signed up with a wine-specialist e-label service, paid the first year, and printed.
The bottles went into the cellar, into a few specialist merchants, into private cellars across three countries. A handful went to collectors who will not pull the cork until the late 2030s.
Eighteen months later the e-label service sent a pricing-change email. The plan she had bought was being discontinued; existing labels would migrate to a new per-cuvée tier at a higher annual rate, or the QR codes would stop resolving at the next renewal. The bottles were already in cellars she would never see again. She could not recall them, peel the back labels, and reprint. Her only real choice was to keep paying, indefinitely, on terms the vendor would set, for as long as a single bottle of that vintage might still be opened — which, for a cellar-worthy Grand Cru, is twenty years.
That is the wine problem in one paragraph. The bottle outlives the vendor’s pricing page. This article is about how to put a QR code on a wine bottle label that satisfies 2021/2117 and is still resolving when someone finally opens the bottle — even if the company you bought the QR from is long gone. It is a wine-specific companion to our broader guide on QR codes for product packaging and to the pillar on QR codes that don’t expire.
Disclosure up front: Heldqr is our product. There is a section near the end recommending it for part of this problem and another section listing the cases where it is the wrong tool. We have tried to keep the recommendation honest enough that you can ignore it and still leave with a better print decision.
What 2021/2117 actually requires — and what it doesn’t
The relevant change came in with the Common Market Organisation amendment, Regulation (EU) 2021/2117, and applied to wines produced from the 2023 harvest onward — in practice, on shelves from December 2023. It brought wine into line with the rest of packaged food on two points: a list of ingredients and a nutrition declaration (energy value plus the standard nutrients) must now be available to the consumer.
The concession that created the whole QR market: producers may show the energy value on the physical label and provide the full ingredient list and complete nutrition declaration electronically — via a QR code or other digital means — rather than cramming it all onto the glass. The Commission has issued guidance on what the electronic presentation may and may not do: the e-label must not carry marketing content, must not collect or track user data for marketing, and must present the mandatory information cleanly.
Two consequences fall straight out of that for the QR itself.
First, the destination matters as much as the code. A QR that resolves to a page stuffed with ads, retargeting pixels, or “scan to join our newsletter” interstitials is not just tacky — it may put you offside with the no-marketing-content rule on the regulated portion of the e-label. Several generic free QR generators monetise exactly by injecting an interstitial or ad before the redirect. On a wine e-label, that is a compliance hazard, not just an annoyance.
Second, the obligation lasts as long as the bottle is on the market — and for wine, that can be decades. Nothing in the regulation says the e-label may go dark once the vintage stops selling at the cellar door. As long as a bottle is legally on the market and capable of being scanned, the information has to be reachable.
Why wine breaks the QR-SaaS business model
Most QR-code subscriptions are quietly priced on an assumption: that the printed thing has a short, commercially active life. A menu changes every season. A flyer is dead in a month. A trade-show banner is recycled after the show. Under that assumption, “your codes deactivate when you stop paying” is a tolerable deal, because you stop paying at roughly the same time you stop caring.
Wine violates the assumption in three directions at once.
Shelf life. A simple Vinho Verde or a Beaujolais Nouveau is drunk within a year. But a Bordeaux cru classé, a Barolo, a vintage Champagne, a Sauternes, an Alsace Grand Cru, a Rioja Gran Reserva — these are designed to be cellared for ten, twenty, even thirty years. The producer’s commercial interest in that bottle ends at the sale. The regulatory obligation, and the collector’s expectation that the QR works, does not.
Irreversibility. Once the bottles leave the winery they are uncatchable. They are in private cellars, in restaurant racks, in auction lots, in someone’s gift cupboard. There is no “push an update to the label.” Whatever you printed is the final answer for the life of that glass. The exemplar packaging guide calls this the irreversibility asymmetry; on wine it is at its most extreme, because the cellaring window is the longest in everyday consumer goods.
Per-cuvée economics. A small estate making 2,000 to 15,000 bottles across four or five cuvées has the same legal duty as a négociant moving ten million bottles, and a tiny fraction of the budget. Wine-specialist e-label vendors typically price per cuvée or per label — some as annual subscriptions, others (e-label.eu, for instance) as a one-time fee per new label with prior years staying free (e-label.eu). For a grower with five cuvées and a long-tail back-catalogue of older vintages still in trade, a per-cuvée annual fee, with renewal terms the vendor controls, is an open-ended liability sitting against bottles you may have sold years ago.
Put the three together and you get the structural mismatch: the median small SaaS company operates a handful of years before shutting down, being acquired, or pivoting — shorter than the cellaring window of a single serious bottle. Printing a wine e-label QR against a subscription vendor is, statistically, betting your compliance on a company that will probably not exist when the bottle is opened.
The wine-specialist vendors, fairly
There is a real category of wine-e-label services — PinotQR, e-label.eu, and a set of national-language incumbents — and they exist because they solve a genuine problem: they hand you a compliant ingredient-and-nutrition page template, handle the multi-language requirements, and give you a QR without you having to build anything. For a winemaker who does not want to think about web infrastructure at all, that convenience is worth something.
What they are, almost without exception, is vendor-hosted services with recurring or per-label fees. And the thing the convenience pitch does not address is the question this whole article turns on: what happens to your e-labels if the vendor shuts down, gets acquired, or restructures pricing? When we have looked, these services do not publish a true continuity commitment. e-label.eu goes further than most — it promises to keep e-labels online for at least ten years, backed by insurance (e-label.eu) — but even that stops short of a shutdown-scenario plan: no open-source resolver, no exportable mapping of your codes to destinations. That silence is not malice. It is the industry default. But on a product with a twenty-year cellaring window, the default is the whole risk.
So the honest framing is: these vendors are fine at the compliance-template job and unproven at the durability job. If you buy from one, the question to put to them in writing is not “is your page compliant” — it probably is — but “if you stop operating, what specifically happens to the QR codes already on bottles in my customers’ cellars, and can I get a machine-readable export of every code and its destination today?”
What to check before you print
A short checklist, wine-specific, in the order the decisions actually come up.
- Is the destination page free of marketing content and tracking? The regulated e-label must present mandatory information without marketing or data collection. Rule out any free generator that injects an ad or interstitial before the redirect.
- Static or dynamic? A static QR bakes the destination URL into the pattern — it works forever with no server, but you can never change where it points. A dynamic QR points at a provider’s redirect, which you can re-target, but which depends on that provider staying alive. For wine, dynamic is usually right, because the e-label format guidance is still settling and you may need to update the page across a vintage without reprinting. But dynamic is also the fragile choice, because the redirect is the vendor.
- Does the provider publish a continuity plan? In writing, public, irrevocable: what happens to your codes if they shut down? The answer you want names a notice period, an open-source resolver, and an export of your code-to-destination mappings. Silence means “nothing.”
- Can you point the QR at your own domain? This is the single most important durability lever for cellar-worthy wine, and it gets its own section below.
- Can you export every code and its destination, any time, without a sales call? A vendor who makes this trivial is not planning to use lock-in as leverage.
- Is pricing flat or per-cuvée? Per-cuvée pricing turns every vintage and every label into a recurring line item that compounds as your back-catalogue grows. Flat pricing bounds the cost.
- The physical fundamentals. At least a 2 cm square for comfortable hand-scanning, a clear quiet-zone margin, strong contrast against the label stock, and a higher error-correction level (Q or H) so the code still reads under a wine-stained, humidity-curled, cellar-aged label.
The custom-domain point — this is the durability answer for cellared wine
Here is the lever almost no one prints with, and the one that matters most for a bottle meant to be laid down.
If your dynamic QR encodes a short URL on the vendor’s domain — say theirservice.io/x7k2 — then the printed code is only as durable as that domain and that company. When the company dies, the domain eventually lapses, and every bottle carrying that code goes dark at once. No amount of “lifetime” marketing survives the domain expiring.
If instead the QR encodes a short URL on your own domain — qr.yourestate.com/riesling19 — pointed at the redirect provider via DNS, then the printed artefact depends on a domain you control. The provider can vanish; you re-point the DNS at any other redirect layer, or at a plain static page, and every bottle in every cellar keeps resolving. For wine specifically, where the bottle outlives any plausible vendor, putting the QR on your own domain is the difference between a twenty-year compliance obligation you can always honour and one you have handed to a stranger’s pricing page.
This is not a Heldqr-only idea — any provider worth using at this scale supports custom domains, and you should require it of whoever you choose. It is the printed-QR survival path, full stop.
How to do this with Heldqr
Disclosure again: Heldqr is our product. Here is how the tiers map onto wine, including where the free tier is genuinely enough.
For a single cuvée — a grower bottling one wine, or testing the whole approach on a 1,500-bottle micro-cuvée — the Free tier carries it. €0, unlimited codes, no expiry, no trial countdown, no scan cap that ever deactivates a code, no ad injected into the redirect, no credit card. A free code keeps resolving for as long as we operate and keeps recording lifetime scan totals. There is a soft 100-scans-per-month nudge per code and a small branded caption on the SVG export, neither of which deactivates anything. For a one-cuvée estate, that is the entire job done for nothing.
The reason to move to Pro, at €9 a month (recommended), is the custom domain. Pro gives you unlimited codes, a clean export with no caption, custom shortcodes, and 30-day analytics with country and device breakdown — but for wine the decisive feature is that you can print the QR against your own domain. Do that, and the e-labels on bottles cellared past any future Heldqr shutdown keep resolving independent of us: you control the domain, so you control the survival of the printed code. That is the only honest way we can tell a winemaker “this will still work when the bottle is opened in 2040” — not because we promise to live that long, but because the custom domain means you don’t need us to. At €9 a month it is a fraction of a per-cuvée subscription stack, and it covers your whole range, not one label.
Business, at €29 a month, is for an estate or a cooperative running many cuvées and vintages, or a contract bottler handling labels for several growers: it adds three seats, bulk CSV import to generate and update e-label codes across a whole catalogue in one operation, API access, and daily analytics with a year of history.
The cross-cutting promise is the same on every tier, and it is the part that matters for a cellar: codes resolve for as long as we operate, you can edit the destination URL at any time (it propagates in under sixty seconds, and the printed shortcode never changes), and we publish a single continuity plan for everyone — twelve months’ notice, the resolver source published at month six, per-account exports plus an opt-in public dump at month nine, and final shutdown at month twelve. We do not hand over the bare heldqr.io domain at shutdown, which is exactly why custom-domain survival (Pro and up) is the printed-QR survival path for bottles meant to outlast us. The resolver is open-source and the analytics are cookieless — country and device class only, no IPs, no cookies — which also keeps the e-label on the right side of the no-tracking rule. Pricing and the full plan live at /pricing and /continuity.
If that fits — a small estate, a regulation-forced e-label, an allergy to per-cuvée subscriptions — you can create the first code here.
What Heldqr is NOT the right answer for
Heldqr is a durable redirect layer. It is not a wine compliance platform, and there are cases where you want something else.
A full e-label compliance suite. If you want software that generates the ingredient-and-nutrition page for you, manages the per-market language variants, validates the declaration against the regulation, and keeps a compliance audit trail, that is a wine-e-label DAM/compliance product, not a redirect layer. The wine-specialist vendors above do that part. Heldqr makes the QR durable and lets you re-target it; it does not author or validate the regulated page. Many estates will pair a compliance tool for the page with a durable custom-domain redirect for the code — that is a perfectly sensible split.
Per-bottle serialization and anti-counterfeit. If you need a unique code per bottle, tamper-evident authentication, or a track-and-trace flow validated against a central registry — the kind of thing used against grey-market and counterfeit fine wine — that is a serialization specialist’s job, not ours. We work at batch/cuvée granularity, not unique-per-unit.
Very high volume. A large négociant or co-op moving millions of bottles per cuvée with sustained heavy scan traffic is outside what the public tiers are priced for. Talk to us first; the defaults are built for small and mid-sized estates.
A purely static case. If your e-label lives on a URL on your own domain, and you are confident that domain and that exact page will both stay live and compliant for the full cellaring life of the bottle, a free static QR from a tool like QRCode Monkey or Adobe Express is correct and costs nothing. You only need a redirect layer when you expect to change the destination — which, given the still-settling e-label guidance, most producers eventually do.
In closing
Wine is the hardest case for a printed QR, because the gap between “print” and “last scan” is the longest in everyday consumer goods, and the regulation gives you no way out: once a bottle is on the market, the e-label has to resolve. The bottle will outlive the vendor’s pricing page. It may outlive the vendor.
So treat the print decision the way you treat the wine: assume the long horizon, and plan for it. Choose dynamic so you can keep the e-label current as the guidance moves. Insist on a published continuity plan so a vendor’s disappearance is a migration, not a recall. And above all, print the QR against a domain you own, so the code on a bottle cellared for two decades resolves because you control where it points — not because a company you bought a subscription from in 2026 is somehow still around. Do that, and the QR on the back label is as durable as the wine in front of it.
Heldqr is our product — a durable, dynamic QR redirect layer with a published continuity plan and custom-domain survival for printed codes. If you are weighing it for a wine e-label, start with the pillar guide on QR codes that don’t expire and the broader packaging guide, or just ask us at hello@heldqr.com.