Dynamic codes and redirects
Publish, archive and restore a code
Publishing makes a dynamic code serve its destination. Archiving stops it serving, without invalidating anything already printed. Restoring and publishing again brings the same printed matrix back to life.
Steps
- Publish a code once its destination is correct — before that, scans have nothing to reach.
- Archive a code when a campaign ends and you would rather scans stopped than landed somewhere stale.
- Restore and publish to bring it back. The printed matrix never changed, so old posters start working again.
- Prefer retargeting to archiving when the poster is still on a wall — a dead code is a worse experience than a redirected one.
How to check it worked
Scan a printed copy after each change. Published lands on the destination; archived does not reach it.
What usually goes wrong
- Archiving a code that is still in circulation, and treating the resulting reports as a printing fault.
- Assuming archiving invalidates the printed matrix — it does not.
- Publishing before the destination is ready.
Did this get the job done?
This did not help
Write to us with the platform and version, the steps you took, the result you expected, and the workspace or QR code involved. Mask any secret before you attach anything.
Write to support