Retiring and Replacing Expired QR Codes

A promotion ends, the coupon window closes, or legal withdraws an offer — but the square on the window, the sticker on the shelf, and the photo in a customer’s camera roll do not know the calendar moved. Retiring and replacing expired QR codes is the operational half of campaign life: what happens after the hard stop when materials are still in market, redirects still fire, and someone in operations must decide whether to tombstone, evergreen, reprint, or pull physical assets down. Get this wrong and scanners land on expired pricing, contest rules that no longer apply, or a bare 404 that feels like neglect.

This guide is about post-expiry operations — decision trees, tombstone UX, inventory ownership, field pull-downs, swapping damaged or static codes for dynamic redirects, archiving analytics without erasing history, compliance, franchise proof, and residual scan handling. It complements seasonal and limited-time QR campaigns, which covers launch, rotation, and calendar-first planning; here the focus is what you do when the offer is over and the world still scans. For instrumentation while codes are live, use tracking dynamic QR campaigns. For fundamentals on editable redirects, read static vs dynamic QR codes and QR code short links and redirects explained. Broader standards sit in Best Practices.

Why expiry is a product decision, not a marketing afterthought

Expiry touches legal, retail ops, support, and data teams — not only the marketer who closed the campaign in email. When a code still resolves but the destination is wrong, you create bait-and-switch risk: the printed CTA promised a deal the page cannot honor. Regulators and franchise agreements care about truth in advertising; customers care about whether the brand respects their time.

Treat every printed or durable code as having two clocks:

Clock	What it controls	Typical owner
Offer clock	Price, eligibility, contest rules, inventory	Legal / merchandising
Redirect clock	Where the short link sends scanners	Marketing ops
Physical clock	What remains mounted, packed, or photographed	Field / retail

Those clocks drift. Marketing may retire the redirect on time while stores still display last month’s cling. Finance may extend redemption in the POS while the landing page says “ended.” Retirement work aligns all three clocks and documents who approved each change.

Decision tree: retire, evergreen, or replace print

When a code’s offer expires, choose an explicit fate for the redirect and the physical asset. Do not default to “leave it” because the dashboard still shows scans.

Offer ended?
├─ Can you still honor something truthful at scan? (evergreen catalog, loyalty, store finder)
│  ├─ Physical asset stays up months/years → EVERGREEN REDIRECT (update destination)
│  └─ Asset comes down within days → RETIRE (tombstone) then PULL-DOWN
├─ Cannot honor anything (illegal offer, ended contest, recalled SKU)
│  ├─ Asset removable → RETIRE + PULL-DOWN on schedule
│  └─ Asset not removable soon (packaging, mailed insert) → TOMBSTONE or EVERGREEN with zero false promise
└─ Printed URL is static OR code is damaged/unscannable
   └─ REPLACE SURFACE (new print or overlay) — prefer NEW DYNAMIC code identity for measurement

Retire (tombstone) when the promotion must not imply availability. Flash coupons, one-time event badges, and compliance-limited claims fit here. The redirect should land on a short, branded tombstone — not a generic 404.

Evergreen redirect when the substrate outlives the offer: window vinyl, annual catalog backs, product cartons, trade-show panels you cannot reprint this quarter. Point to an experience that is true today: category hub, “what’s new,” loyalty signup, or store locator. Evergreen is not “keep last year’s landing page.” It is a deliberate new destination that matches what a reasonable scanner expects after the season.

Replace print when the encoded URL is static (cannot edit behind the pattern), the QR is physically damaged, or the printed caption is permanently wrong (“40% off” when finance ended the discount). Overlay stickers, new cling, or a corrected SKU label are field tasks — plan them in the inventory sheet before hard stop.

If you are still choosing between static and dynamic for the next flight, static vs dynamic QR codes and short links and redirects explain why retirement is cheaper when the pattern stays fixed and only the redirect changes.

Tombstone page UX: honest, fast, one next step

A tombstone is the landing experience after retire. It should load quickly on mobile, state clearly that the promotion or event ended, and offer one obvious next step — shop current offers, join email, find a store, or view the next scheduled event. Avoid walls of apology, auto-playing video, or login gates that block the message.

Effective tombstones share these traits:

Headline matches reality — “This offer ended on [date]” or “This event has concluded,” not vague “Thanks for visiting.”
No expired prices or SKUs — remove countdown timers, coupon fields, and hero products from the ended campaign.
Brand continuity — same fonts and colors as live campaigns so the page feels intentional, not broken.
Accessible structure — one h1, logical heading order, sufficient contrast; scanners often use screen readers in bright storefronts.
Support path — one line for “Questions about an order?” with a monitored channel, not a dead chat widget.

Soft-close pages (offer ending soon) differ from tombstones: they still sell urgency. At hard stop, promote honesty over conversion tricks. Landing craft for active campaigns lives in QR code landing page best practices; tombstones apply the same mobile-first discipline with a narrower goal.

Test tombstones the way you test live offers: testing QR codes before you print applies to redirect QA after retirement — scan from Android and iOS on cellular, confirm analytics tags still fire if you track tombstone views, and verify cache/CDN does not serve yesterday’s sale page.

Inventory, ownership, and the code lifecycle sheet

Seasonal programs spawn dozens of codes; retirement fails when no one knows which ID hung in store 1842. Maintain a lifecycle sheet (spreadsheet or ops tool) keyed to code ID, not only campaign name.

Minimum columns:

Code ID / dashboard name (include retired_YYYYMMDD suffix when closed)
Offer end date and legal owner who signed hard stop
Current destination URL and tombstone / evergreen URL
Physical SKU, print job, or kit number
Placement type (window, wobbler, receipt, packaging)
Region / store list / franchisee
Status: live → soft_closed → retired | evergreen → pulled (physical)
Pull-down owner and due date
Notes (contest rules archive link, coupon code range, partner exclusivity)

Ownership must be named before launch: who may edit redirects at 10 p.m. on a Saturday, who approves tombstone copy, who emails franchisees about pull-down. Ambiguity produces “someone thought IT would flip the link.”

Align status changes with tracking dynamic QR campaigns naming — when you archive a code in the dashboard, mirror the label in UTMs and the sheet so year-over-year reports do not mix retired traffic with active campaigns.

Field operations: pull-down checklists and replacement

Physical retirement is where digital work meets glass and cardboard. A pull-down checklist should be boring and assignable:

Confirm redirect fate in dashboard (tombstone or evergreen) before crews remove signage — scanners mid-pull should not hit a 404.
List every surface by store ID: quantity, location photo reference, replacement creative SKU.
Assign remover and verifier (two roles when possible).
Define disposal (destroy expired cling, return to warehouse, recycle packaging inserts).
Install replacement creative or blank filler per brand standards.
Capture compliance photos (see franchise section below).
Mark pulled in the inventory sheet with date and initials.

Replacing damaged or static codes often means a new sticker over the old square or a full reprint. Prefer a new dynamic code identity when the replacement is a distinct print run — you keep clean analytics for “original flight” vs “field replacement.” If you must reuse the same short link on a repaired label, document the repair date so residual scan spikes are explainable.

When static codes were used historically, retirement may require physical swap to dynamic at replacement time — encode a stable short URL, test contrast and quiet zone, then retire the old static destination at the web server if anything still pointed there. Testing QR codes before you print remains mandatory for replacement batches; a rushed overlay in the field is a common source of unscannable patches.

Archive analytics without deleting history

Teams sometimes delete retired codes from a dashboard to “clean up.” That erases scan history you need for compliance, franchise audits, and year-over-year learning. Archive, do not delete.

Action	Effect on history	When to use
Archive / label retired	Past scans remain; code hidden from active lists	Default at hard stop
Change destination	New funnel segment; history often continuous per code	Evergreen or tombstone
Create new code ID	Clean split between campaigns	New print or new placement
Delete code	History lost or fragmented	Avoid except GDPR/legal erasure orders

In reporting, segment post-retire residual scans separately from in-window performance. Residual traffic measures leftover materials and social shares — useful for ops (did pull-down work?) — not for claiming promo ROI. Close books using the offer window defined at launch, as described for seasonal close-out in seasonal and limited-time QR campaigns.

Export or snapshot dashboards when vendors limit retention. Store PDF/CSV with the campaign archive folder alongside legal approvals and creative PDFs.

Dynamic platforms such as Izoukhai’s dynamic QR generator support ongoing edits and real-time analytics on unlimited codes and scans ($3.99/month or $39.99/year), so you can flip a destination to a tombstone without reprinting and still read historical scan curves for the retired offer. Codes keep working after you cancel, which matters when retirement work spans quarters and you should not lose redirects because a subscription lapsed mid-pull-down.

Legal, offer compliance, and contest rules

When an offer expires, more than marketing copy expires — terms, disclaimers, and eligibility may impose obligations on what a scanner can still see.

Price and availability claims — tombstones must not show stale prices. If evergreen routing sends users to a category page, ensure featured modules do not resurrect ended SKUs.
Contests and sweepstakes — archive official rules with end date; tombstone should point to winners page or “concluded” notice per counsel guidance.
Coupons and barcodes — if POS no longer honors a code, the landing page must not instruct users to present an invalid coupon.
Regional restrictions — geo-targeted offers need geo-aware retirement or evergreen so a retired US promo does not flash in a market where it never ran.

Document approvers for tombstone copy the same way you document offer launch. A one-line email “marketing turned it off” is weak evidence if a regulator or partner asks what scanners saw on day thirty-one.

Franchise and multi-location compliance photos

Franchise systems cannot assume every location pulled cling on Tuesday because headquarters sent an email. Photo proof closes the loop: empty mount, new creative installed, or approved evergreen still in place.

Standardize a lightweight ritual:

Required shots: wide context (aisle/window), close-up of QR or removal, store ID visible (door decal or metadata in upload).
Upload to a shared drive or field app tied to the inventory row.
Review sample by region; escalate repeat offenders before the next kit ships.

Pair photos with redirect state: if analytics show scans from a store marked pulled, either the photo was wrong, a duplicate unauthorized sign exists, or a customer-shared image drives traffic. Residual scan handling (below) helps triage.

Multi-location naming and rollup patterns overlap with franchise campaign guides elsewhere in the handbook; retirement is where those naming conventions pay off — bfcm26_window_regionwest_2026 retires without touching bfcm26_window_regionsouth_2026.

Residual scan handling after retirement

Scans after hard stop are normal. Packaging circulates, wedding photos include your table tent, and marketplace resellers ship old cartons. Plan for them instead of treating each spike as an incident.

Classify residual scans:

Pre-pull-down, post-redirect — destination already tombstoned; physical asset still up. Fix: accelerate pull-down; message is correct.
Post-pull-down — asset removed but scans continue. Likely digital sharing or inventory in channel. Monitor; no reprint unless fraud or confusion is costly.
Evergreen drift — scans hit evergreen URL but bounce rises. Refresh evergreen content; test mobile speed per landing page best practices.
Wrong region / wrong store — misrouted dynamic rules left active. Fix redirect rules; audit tracking segments.

Set an alert threshold (e.g., >N scans per day on a retired code two weeks after pull-down) for ops review, not automatic panic. Teach support staff the tombstone script: what to tell customers who expected the old offer.

Replacing expired static codes with dynamic (upgrade path)

Organizations often discover retirement pain only after printing thousands of static codes tied to one-off URLs. The upgrade path is incremental:

Stop issuing new static campaign codes; use dynamic short links for all time-bound offers.
At next physical touch (reset, remodel, packaging refresh), swap to a dynamic code with a documented ID in the inventory sheet.
For long-lived packaging, plan an evergreen dynamic at first print so only the redirect changes at end-of-life.
Keep server-side redirects from legacy static URLs if old prints still exist — mirror the tombstone experience.

Damaged codes on active campaigns sometimes get a field overlay. Treat overlay as a new print event: QA scan distance and glare, confirm the old pattern is fully covered, and log the change. Izoukhai’s toolset — customize colors and frames, export SVG for vendors, edit destinations on the fly, view device and location analytics — fits teams that replace batches without per-code fees; see Izoukhai’s dynamic QR generator when you standardize on one unlimited plan for both live and retiring codes.

Retirement runbook checklist

Use this sequence at every hard stop (copy into your project management tool):

Confirm hard stop — legal/merchandising sign-off; offer clock stopped in POS and email.
Choose fate — retire (tombstone), evergreen, or replace print per decision tree.
Publish destination — tombstone or evergreen live; mobile QA on cellular.
Update inventory — status, URLs, owners, pull-down due dates.
Notify field — kit list, pull-down order, photo requirements, support script.
Soft-close already done? — if not, skip straight to tombstone; do not leave sale page up.
Execute pull-down — verify with photos; mark pulled.
Analytics — archive code in dashboard; export snapshot; segment residual scans in reports.
Retrospective — leftover surfaces, static upgrades needed, timeline slips for next season.

Pair the runbook with calendar planning from seasonal and limited-time QR campaigns so retirement is scheduled when the campaign is booked, not discovered when support tickets spike.

Conclusion

Expired QR codes are a lifecycle problem: redirects, printed promises, and field reality must move together. Use a clear retire / evergreen / replace-print decision tree, ship tombstone pages that respect scanners and lawyers, keep a living inventory with named owners, run pull-downs with proof, archive analytics instead of deleting it, and treat residual scans as operational signal — not campaign success.

Next steps: validate dynamic retirement mechanics in static vs dynamic QR codes and short links and redirects; instrument and name codes with tracking dynamic QR campaigns; QA tombstones and replacements with testing QR codes before you print; align active landing craft via QR code landing page best practices; and coordinate time-boxed launches with seasonal and limited-time QR campaigns. More guidance lives in Best Practices.

When the offer clock stops, the redirect should already know its fate — and field teams should know which square comes off the glass before a stranger’s scan becomes your brand’s problem. Tools like Izoukhai’s dynamic QR generator ($3.99/month or $39.99/year, unlimited codes and scans, on-the-fly destination edits, analytics, codes that keep working after cancel) make the digital half of retirement fast; the checklist makes the physical half accountable.