How to leave your QR code platform without reprinting anything

This article tells you how to leave a QR code platform, including this one. We publish it because a company confident in its product should be able to explain how to stop using it, and because the alternative — people stuck on a platform they resent — is how this industry got its reputation.

The one rule

Never cancel before you migrate. Everything below depends on your old codes still resolving while you work. Cancel first and you are relying on your old vendor's policy for lapsed accounts, which across this industry is the single most complained-about thing there is.

Why chaining works

A dynamic QR code encodes a short URL and forwards it. Forwarding can point anywhere — including at another platform's short URL. So you can insert a new provider behind the old one without touching a single printed item.

The person scanning sees nothing different. Their phone follows one extra hop, which costs a few dozen milliseconds.

The method

1. Inventory what you have. Export a list of every code, its short address and its destination. Note where each one is physically deployed — this is the part people wish they had done.
2. Create matching codes on the new platform, each pointing at the same final destination as its counterpart.
3. Repoint each old code at its new counterpart. In the old platform, set the destination of code A to the new platform's short URL for code A. Printed code → old platform → new platform → destination.
4. Verify. Scan several physical items. Confirm they land correctly and that scans appear in the new platform's analytics.
5. Run both for a while. A month is sensible. Compare scan counts; they should track closely.
6. Reprint opportunistically. As material is reordered, use the new codes directly, removing the extra hop. There is no deadline.
7. Only then consider cancelling — and only once everything still in circulation has been replaced, or you have accepted that those items will stop working. Items in the wild that still carry the old code will break when the chain does.

What this does not solve

Static codes. A static code has the destination baked into the pattern. You cannot repoint it. If it points at a URL on a domain you control, change the redirect on your own server. If it points at a third-party URL, reprinting is the only option.

An already-cancelled account. If the old codes have already stopped resolving, there is nothing left to chain through. At that point the only route is reprinting — which is the whole argument for exporting static fallbacks while you still can.

How to leave ScanMePlz

Two routes, both of which we build and maintain deliberately.

Chain through us. Create your codes elsewhere, repoint each ScanMePlz code at its replacement, and leave it that way indefinitely. Even on the free plan, codes over the limit freeze rather than stop — they keep redirecting and keep counting scans — so the chain holds without you paying us anything.

Or take the static fallbacks. Download your Permanence Kit, available on every plan including free. It contains a static QR code for each of your dynamic codes, encoding that code's current destination directly. Reprint from those and you depend on nobody — not us, not whoever you move to.

If you are leaving because something was wrong, we would genuinely like to know: tell us.

Choosing the next one

Ask these before you commit, and get the answers in writing:

• What happens to my dynamic codes if I stop paying? Is that in your terms?
• Is scan recording capped, separately from redirects?
• Can I export a static fallback image for every dynamic code?
• Is billing available monthly, or annual only?
• What does a custom domain cost?

The third question is the important one. A platform that can hand you static fallbacks is a platform you can leave. One that cannot has made the decision irreversible, whatever its terms say.