A QR code is a picture of a string of characters. ISO/IEC 18004, the standard that defines the symbology, puts the data in the pattern of black and white modules, so whatever text was encoded is fixed the moment the code goes to print. If that text is a web address, the printed code points at that address for as long as the decal lasts. You cannot edit it or take it back.
That part people understand. The part that costs money is what happens when the encoded address belongs to somebody else.
Static and dynamic codes are two different objects, not two settings
A static code holds your destination directly. Scan it, and the address you encoded is the address the phone opens. Nothing sits in between.
A dynamic code holds a short vendor address instead. The phone opens that address, the vendor's server looks up where you currently want people sent, and answers with a redirect. The advantage is genuine, and it is the only reason to use one: you can change the destination without reprinting. The cost is that the first hop belongs to the vendor, and every scan from the day you print onward depends on that vendor answering.
The redirect layer fails more often than the print does
Google ran a redirect service called Firebase Dynamic Links and shut it off on August 25, 2025. The shutdown FAQ is blunt about the scope: all links served by Firebase Dynamic Links, both those hosted on custom domains and those on page.link subdomains, stop working, and a clicked link returns an HTTP 404 to the end user. A custom domain spared nobody, because the redirect logic lived at Google, not at the domain.
The same date applied to Google's old goo.gl shortener, where links with no recent activity were switched off. Active ones were kept, and Google's published test for telling the difference is to open the link: if it redirects with no message in the way, it carries on working.
Commercial QR vendors are plainer still. QR Tiger's support documentation says that when a paid subscription expires or is cancelled, all dynamic QR codes become invalid. Note what is unharmed in that sentence. The code is fine. The decal is fine. What the decal points at is gone.
The two minute check
Scan one of your own printed codes with a phone and read the host, in the camera preview or in the address bar before the destination loads.
- If the host is a domain you own, you control the redirect and you can move it.
- If the host is a vendor domain, the vendor controls it, and your print is only as durable as that account.
Then count what is already in circulation. Lawn signs and window decals on a vacant unit. The maintenance code on a fridge magnet. Codes in the lease package, on the parking permit, on the laundry room wall. All of it is printed, and reprinting a building's worth of it carries a cost and a lead time of its own.
Own the first hop
The fix is unglamorous. Put the printed code on a path at a domain you own, something along the lines of yourdomain.ca/u/204, and have your own web server issue the redirect. You keep the one thing a dynamic code is for, which is changing the destination later, and you keep the ability to change hosting or vendors without touching anything that was printed.
Then write the mapping down. A plain list of every printed path and where it currently points, kept somewhere other than a vendor dashboard. Owning the domain is what lets you repoint it. The mapping is what lets you rebuild the redirects once you have.
A code on a wall is a promise with no expiry date printed on it. Worth making sure the promise is yours to keep.
