Docs · How-to

Change where a printed code points

This is the whole reason a dynamic code exists, and it takes four steps. The menu is on the table, the sticker is in the window, the flyer went out last month · and the address behind all of them is a field you edit. Nothing is reprinted, nothing is re-issued, and the person scanning does not have to do anything at all.

Change it

  1. Open the code. Go to Links and click the row for the code you want to change. A panel opens on the right, with the short link at the top and the Overview tab already selected.
  2. Edit the "Destination URL" field. It is the first field on the Overview tab, under a two-button switch reading URL and Hosted page. Replace the address with the new one.
  3. Check it before you commit, if you like. Next to the Save button is an Open destination link. It opens what is currently typed in the field, saved or not, so you can confirm the new page actually loads before any scanner sees it.
  4. Press "Save". A "Link updated" confirmation appears and the Destination check box below the field re-measures the new address. That is it · the next person to scan the printed code lands on the new destination.

If the code was never published

Saving a new destination on a draft pops a dialog reading "Publish this code now?" · "The new destination is saved. The address still will not resolve until you publish." A draft's address does not resolve for anyone, so if the code is not live yet, the destination edit is not the step that was missing. Press "Review and publish". See Create your first QR code for the full publish flow.

What actually changed, and what did not

  • The symbol did not change · it encodes https://tap2u.link/summer-menu, and that string is write-once from the moment the code is published. Nothing you do in the design studio, and nothing you do here, can alter what is already on paper. That is the guarantee: a repoint cannot break a printed code, by construction.
  • Every copy followed · there is no per-copy state. The sticker, the flyer, the table tent and the screenshot someone took all resolve through the same short link, so they all move together.
  • It costs nothing · repointing is not metered. There is no per-edit charge and no monthly quota of changes. Scans still bill 1 credit each, as they did before.
  • Scan history is kept · the code keeps its identity, its analytics and its scan count across the change. You can see the before and the after on the same chart.

Point it at something other than a URL

The row of buttons above the Destination URL field switches what the code does, not just where it goes. Three kinds can be swapped on a code that is already printed: URL, WhatsApp and Location. A poster that sent people to your website can be made to open a WhatsApp chat instead, with the message pre-filled, and the printed code is still the printed code.

To send the code at a page taproute hosts for you rather than a site of your own, use the Hosted page half of the switch at the top of the Overview tab. The short link keeps working; it renders the page instead of redirecting. See Hosted pages.

Contact cards and WiFi joins are not in that switch. Turning a live code into one of those has to mint a hosted page behind it, and doing that silently to something already on paper is not a change this control makes on its own.

When a new destination is refused

Changing a destination re-runs the same safety screen that ran when the code was created · only a destination that actually changed is re-measured, so an unrelated edit costs nothing. Two outcomes are worth knowing about before you are standing in front of one:

  • Refused outright · the address is on a malware, phishing or unwanted-software list. The save fails and the code keeps its old destination, which is the right failure: a printed code never silently starts pointing at something that was just flagged.
  • Refused on the shared domain, allowed on yours · some content categories are not carried on the shared short host, because that hostname is other customers' reputation as well as yours. On a custom domain you have connected and verified, the same destination is your brand's call to make. Custom domains covers connecting one.
  • Saved with a note · the Destination check box under the field reports what was observed rather than what you should feel about it: whether the address answered, whether it is served over HTTPS, whether it redirects somewhere else. A low score is information, not a refusal.

The case this guide cannot fix

A static code has nothing to repoint

If the code was made static · the "Put the content in the code itself" answer, or any free generator that does not ask you to sign in · then the destination is inside the pattern. There is no field to edit, here or anywhere else, because there is no record: the scan never reaches us. Any tool claiming it can edit a printed static code is either wrong or is quietly talking about a dynamic one.

There is still one route back. If the static code points at an address you control, you can put a redirect at that address and hand the traffic to a dynamic code, so from then on it is repointable like any other. taproute has a setup for exactly this, including a daily check that the hop is still alive · it costs 50 credits, once. The diagnosis and the four handover methods are on QR code stopped working.

If the printed code points at a domain you never controlled, or at a vendor's short link on an account you cannot access, nothing repairs it. Reprinting is the honest answer, and any product that tells you otherwise is selling you a story. Static vs dynamic is the page to read before the next print run.

Doing it for many codes at once

If fifty printed codes all point at the same address and that address changes, editing fifty destinations is the wrong shape. Save the address once in the sidebar's Repository and point the codes at that entry instead · changing it moves every code that references it in one edit. The warning attached to that field is the point of it: "Every code pointing here follows the new address immediately." There is no staging and no undo.

If you want the code to send different people to different places rather than everyone to one new place, that is routing, not repointing: Send one code to different destinations.

Questions

Do I have to reprint the QR code after changing the destination?

No. The printed symbol encodes the short link, not the destination, and the short link never changes. Editing the destination changes what opens when someone scans; the ink is untouched and every copy already in the world follows on the next scan.

How long until the change takes effect?

The next scan gets the new destination. There is no cache to clear on your side and nothing for the person scanning to do · they scan the same code and land somewhere else.

Can I repoint a static QR code?

No, and no tool can, ours included. A static code carries its content inside the pattern itself, so the destination is literally the ink. If it points at an address you still control, you can put a redirect at that address and take the traffic back that way. If it does not, a reprint is the only honest answer.

Is there a limit on how many times I can repoint a code?

No. Changing a destination is free and unmetered · you are not billed per edit, and there is no monthly allowance of changes. Scans bill at 1 credit each whatever the destination is.

Why was my new destination refused?

Every destination is screened again when you change it, not only when the code was created. A destination on a malware or phishing list is refused outright. Some categories are refused on the shared short domain but permitted on a custom domain you own, because on your own hostname it is your brand carrying the content.