Ink is immutable; destinations are not, provided the code was printed with the one property that matters: it carries a resolver address rather than the final destination. That indirection is the entire trick behind every claim that the barcode is now editable, and it deserves to be understood plainly.
The mechanism in one paragraph
A pack printed with onpack.link/01/09506000134352 names the product, not the page. What answering that URL means, redirect to a campaign, serve a hosted page, show a recall, answer a machine with data, is configuration on the resolver, editable any time. Printed marketing QRs that embedded the final campaign URL directly have no such layer, which is why they die with the campaign, per the lifespan analysis.
What changing actually looks like
Open the product in the console, change the destination or the page, save; every unit in the field follows on the next scan. The same edit surface covers the graduated interventions: an expiry-aware warning, a recall on one lot, a different destination per country, all changes to configuration, none to ink.
Why this changes packaging economics
Packaging decisions are printed months before the shelf and live years on it. Without indirection, every web decision is frozen at artwork signoff; with it, artwork carries identity while behaviour stays current. That is what lets brands print Sunrise-ready codes today without predicting their 2028 web strategy, and it is why the code outliving the campaign is a feature rather than a bug.
The one caveat: choose an exit-friendly resolver
Indirection concentrates trust in the resolver, so the resolver must be leaveable: standards syntax, configuration export, your own domain if you want it. That is a solved requirement if you select for it, per the selection guide; Onpack treats exportability as a design goal and publishes the commitment in its terms.
Common questions
Can a printed QR code's destination really change?
If the code contains a resolver URL, yes, forever: the print carries the address, the resolver decides what answering it means. Only codes that embedded the final destination directly are stuck.
Does redirecting hurt speed for shoppers?
A resolver hop adds milliseconds at the network edge; shoppers cannot perceive it, and the scan is counted before the redirect.
What happens to codes if a campaign page is retired?
Repoint the destination in the console and every printed pack follows instantly. This is precisely the failure mode dead marketing QRs suffer and resolver-backed codes do not.
Is this lock-in to the resolver?
Judge by exit: standard URI syntax plus configuration export means moving resolvers is a DNS change. Avoid proprietary shortlink schemes where identifiers are not portable.