A dynamic QR code only works for as long as the service behind it stays online and paid for. Keeping printed codes working for years comes down to a handful of habits: keep your account and billing current, keep a written record of every code and where it points, review destinations on a schedule, and know what you will do if the service ever shuts down. This article turns those habits into a practical checklist you can follow monthly and yearly.
Why dynamic QR codes need maintenance
A static QR code encodes the destination directly into the pattern. Scan it, and the reader goes straight to that URL or text. Nothing sits in between, so nothing can break except the destination itself.
A dynamic QR code is different. The printed pattern encodes a short URL on a domain owned by the QR code service. When someone scans it, they hit that short URL first, and the service redirects them to your real destination. This indirection is the whole point: you can change the destination later without reprinting the code. It is also the whole risk. If the service goes offline, if the short domain expires, or if your subscription lapses and the service disables your codes, every printed instance stops working at once.
That risk is not hypothetical. Printed codes live on packaging, signage, business cards, vehicle wraps, and product labels for years. Services change ownership, domains lapse, companies shut down. A code printed in 2024 will still be scanned in 2030, and the only way to make that likely to work is deliberate maintenance.
The honest summary: a dynamic QR code is a small ongoing commitment, not a one-time print job. If you cannot commit to that, print static codes for anything permanent, and use dynamic codes only where you genuinely need to change destinations later.
Keep the account and billing details current
The most common way dynamic codes die is boring: an expired credit card, a closed email address, a lapsed subscription that silently disables redirects. None of these are technical failures, and all of them are preventable.
Do the following:
- Use an email address you check regularly for the QR service account, not an address tied to a role you might leave or a domain you might let expire.
- Keep a payment method on file that does not expire soon, or set a calendar reminder a month before the card's expiry date.
- Turn on renewal and payment-failure notifications, and actually read them.
- If the account belongs to a company, make sure at least two people can access it. A single-employee account is a single point of failure when that person leaves.
- Note the renewal date and the plan's terms. Some services disable codes on payment failure after a grace period; some delete data after long inactivity. Know which applies to you.
If you manage codes for an organisation, treat the account like any other production credential: documented ownership, a recovery path, and someone responsible.
Record where each code is printed and what it points to
When you have five codes, you can remember them. When you have fifty spread across menus, posters, and packaging, you cannot. A simple register solves this. A spreadsheet is enough.
For each code, record:
- A name or ID (for example, "menu-2024-table-tent").
- The short URL the code encodes.
- The current destination URL.
- Where the code is physically printed, and roughly how many copies exist.
- The date it was printed, so you can estimate when a reprint is realistic.
- Who owns it, if multiple people manage codes.
- Status: active, retired, or expired campaign.
Keep this register somewhere that survives the loss of any one computer or person. If the QR service itself offers code management and notes, you can use it, but keep an independent copy. If the service ever becomes unreachable, the register is what tells you which printed items are affected and what they were supposed to point to.
Also record the scan history baseline: roughly how many scans a healthy code gets per month. You need that baseline later to notice a drop.
Review destination pages on a schedule
A redirect can be working perfectly while the page behind it rots. Common failures: a page redesigned so the content moved, a product discontinued, a campaign page taken down, a site migrated to a new domain with broken paths, or a page that now loads but confuses visitors.
Review each destination at least yearly, and monthly for anything on high-traffic print runs. On each review, check:
- Does the page load on mobile data, not just office Wi-Fi? Many visitors scan on phones.
- Does the page still show what the printed material promises? A poster advertising a 2024 event should not link to a 2026 homepage.
- Is the content current, or does it need updating?
- Does the URL still resolve, or does it redirect again (sometimes through several hops) to something unexpected?
When you find a stale destination, update the redirect in the QR service. That is the payoff of dynamic codes: a two-minute fix instead of a reprint.
Never delete a page a code points to
The single most damaging habit is deleting destination pages. Someone cleans up the website, removes an old landing page, and every printed code pointing at it starts showing a 404. The QR code itself is fine; the target is gone.
Rules to follow:
- Before deleting any page, check your register (and your QR service's redirect list) for codes pointing at it.
- If a page must be removed, set up a redirect from its old URL to the closest relevant page: the new product page, the current menu, the site section that covers the same topic.
- Keep old campaign URLs redirecting for as long as the printed material exists. A flyer handed out in 2023 can surface in a drawer in 2028.
- If you cannot create a redirect, change the dynamic code's destination to a working page instead. That is exactly what dynamic codes are for.
The same applies to domain changes. If your website moves from one domain to another, keep redirects running from the old domain for years, not weeks. Printed material does not respect your migration timeline.
Handle expired campaigns deliberately
Campaign codes need a retirement plan. A code for a finished promotion should not keep sending people to a dead page or, worse, to a page advertising a competition that ended months ago.
Options, in order of preference:
- Point the code at a current, relevant page: your homepage, a "this campaign has ended, here's what we offer now" page, or the product's permanent page.
- If the printed item is nearly out of circulation and scans have dropped to near zero, mark the code retired in your register and leave the redirect pointing somewhere harmless.
- If you plan a reprint cycle anyway, note in the register that the next print run should carry a new code.
Avoid deleting the code itself in the QR service while printed copies still exist. Deleting it usually kills the short URL, and any surviving print item becomes a dead code. Retire in your records; keep the redirect alive.
Watch scan statistics for sudden drops
Most dynamic QR services show scan counts per code. This data is not just marketing trivia; it is your early-warning system.
Check statistics monthly. Look for:
- A sudden drop to zero on a code that previously got regular scans. That often means the redirect broke, the destination page is down, or the service is having problems.
- A steady decline that matches the printed item leaving circulation. That is normal ageing, not a fault.
- Errors or unusual redirects in the service's logs, if available.
When a code drops to zero, test it yourself: scan the printed item with two different phones. If it fails for you, fix the destination or the redirect. If it works for you but shows no scans, the printed items may simply be gone, or the service's statistics may lag.
One honest caveat: scan statistics are only as reliable as the service providing them, and a drop can also mean the service's own tracking is broken. Statistics are a signal to investigate, not a verdict.
Have a plan if the service shuts down
This is the part most people skip, and it is the part that matters most for multi-year print runs. Any dynamic QR service can shut down, be acquired, change its short domain, or change its terms. You cannot prevent that, but you can prepare for it.
Your contingency plan should cover:
- Export your register and, where the service allows it, your code list and scan history regularly. Keep the export outside the service.
- Know what you control. Some services let you use your own custom short domain; if yours does, and you own that domain, you keep control of the DNS even if the service changes. That is a meaningful advantage: if the service shuts down, you can point that domain at a new redirect service and the printed codes keep working, because the printed pattern encodes your domain, not theirs. If the printed codes encode the service's own short domain, you are dependent on them keeping it alive.
- Decide in advance what you would do in a shutdown: migrate to another service (possible if you control the domain), mass-update destinations, or accept the loss and prioritise reprinting the highest-value items.
- For truly permanent items, prefer static codes from the start, or dynamic codes on your own domain.
Write the plan down in one paragraph, with the register. A plan that exists only in someone's head does not survive their holiday, let alone their resignation.
Keep a copy of the static fallback
A static QR code that encodes your main URL directly will work as long as your website works, regardless of any QR service. Keeping a static fallback costs almost nothing and covers the worst case.
Practical steps:
- Generate a static QR code for your primary, stable URL (usually your homepage). Store the image file with your register.
- For every printed dynamic code, note in the register what the static fallback destination would be, so a future reprint can switch to static if the dynamic approach is being abandoned.
- If a service ever shuts down and you must reprint, print static codes pointing at pages you control, or dynamic codes on your own domain through a new provider.
The fallback does not rescue already-printed dynamic codes; nothing can. What it does is make your recovery fast and your next print run safe.
Monthly and yearly checklists
Monthly (15 minutes for a handful of codes)
- Confirm the QR service subscription is active and payment went through.
- Check scan statistics; investigate any code that dropped to zero or fell far below its baseline.
- Spot-check two or three codes end to end: scan the printed item, confirm the destination loads on a phone and shows current content.
- Update the register for anything changed during the month: new codes, new destinations, retired campaigns.
- Check that any new page launched this month that a code points to is live and mobile-friendly.
Yearly (a deeper review, an hour or two)
- Test every active code by scanning it, not just checking the dashboard. Physical items can be damaged, faded, or covered.
- Review every destination page for currency and relevance; update redirects where content has moved.
- Re-verify account access: recovery email works, payment card not near expiry, at least two people can log in for organisational accounts.
- Export and back up the register, code list, and scan history.
- Reassess the shutdown plan: is the service still healthy? Is the short domain still the same? Has anything changed in the terms?
- Decide on reprints: any printed item due for a redesign is an opportunity to fix, retire, or convert codes.
- Prune the register: mark codes whose printed items are definitively out of circulation.
Conclusion
Dynamic QR codes are genuinely useful, but they are a service you subscribe to, not a file you print once. The key takeaway: treat every printed dynamic code as an ongoing commitment. Keep the account alive, keep a written register of codes and destinations, review pages on a schedule, never delete targets, watch the statistics, and hold a documented plan plus a static fallback for the day the service is not there anymore. Do that, and your printed codes can keep working for years. Skip it, and the first lapsed payment or shut-down provider silences every code you ever printed.