A strange thing to hear from a vendor, so let's say it plainly: the most important evaluation question in this category is what happens when you leave. Printed codes are the longest-lived asset most marketing teams own — boxes from 2024 are still on shelves in 2027 — and every dynamic code binds that paper to whoever serves the redirect. That's not a scandal; it's the mechanism. But it makes portability a due-diligence item, and almost nobody checks it until the renewal email makes them.
The dependency, stated exactly
A dynamic code prints a short URL on the vendor's (or your) domain. If the service behind that URL stops answering, every copy of the print stops working — no negotiation with physics available. So the exit question decomposes into two: who owns the domain on the paper, and can the mapping from printed URL to destination leave in a machine-readable form. Everything else is contract detail.
The four questions to ask any vendor
- 1. Whose domain is on my print? A branded domain you own is the strongest form of portability — the paper names your registrar entry, and the server behind it is replaceable in principle. On a vendor domain, portability rests entirely on the next three answers.
- 2. What exactly happens on cancellation? In writing. Some tools deactivate live dynamic codes when a paid plan lapses; some keep them on a grace tier; some are silent, which is an answer too. Ours is published: static codes are untouched forever by construction, data and artwork stay exportable, and paid redirects wind down with notice rather than a cliff.
- 3. Can I export the mapping? Every slug, its full printed URL, its current destination, and its status — as a file, on request, without a retention negotiation. We produce exactly this as a continuity file, built for the engineer at whatever platform comes next; it includes archived codes on purpose, because paper doesn't know it was archived.
- 4. What survives the vendor entirely? Anything encoding its destination directly — which is why static codes belong on assets that must outlive everyone, and why a platform that charges for static codes is quietly taxing your independence. They're unlimited and free here for that reason.
Reading the answers
You're not looking for a vendor who pretends departure is easy — migrating a live estate has real steps, and repointing printed codes to a new serving arrangement is work wherever you go. You're looking for the difference between work and hostage negotiation: whether the artefacts you'd need exist as a matter of course, or get invented, priced and slow-walked when you ask. A vendor confident in the product treats the exit as a feature spec; the comparison pages track how the major platforms answer, fairly.
The plan, in one afternoon
Before the first big print run: put the code URLs on a domain you own if the scale justifies it; get the cancellation terms in the contract file; request a sample continuity export and check it opens into columns; and route anything truly permanent to static codes. Then stop worrying about it — which is the actual point. An exit you could take on any Tuesday is the reason you'll rarely need to, and the discipline costs one afternoon against paper that lives for years.