QR codes backed by redirects

The code is printed.
The destination is not.

Encode a RedirHub redirect instead of a final web address, and every printed QR code becomes something you can repoint for as long as the print survives.

  • The printed code never changes
  • Destination updates in seconds
  • Every scan is measured

Works with codes you have already printed — if they encode a redirect.

Printed once

QR code encoding https://redirhub.com/qr

redirhub.com/qr

Encoded value unchanged

Scan resolves to

Launch week

GET redirhub.com/qr

302 → yourbrand.com/spring-menu

Spring menu

Guests scan the table card and land on tonight's dishes.

Browse dishes

Cycling through four destinations — pick one to take over.

⚠️ Read this first

A QR code can only be repointed if it encodes a redirect URL.

If the pattern contains the final web address, that address is part of the artwork and nothing can change it — not RedirHub, not anyone. This page is about the other kind: codes that encode a redirect you control.

Compare

Three ways to put a QR code into the world

They look identical on paper. What differs is who owns the destination after printing.

Encoded destination

Static QR code

Generated in a design tool or free generator

The final web address is baked into the pattern itself. Whatever it pointed at on print day is what it points at forever.

  • Free to generate
  • No account or vendor involved
  • Destination can never change
  • A reprint is the only fix
  • No scan data at all
Vendor-owned link

Dynamic QR inside a marketing suite

QR features bundled into a broader platform

The code encodes the vendor's short domain. You can repoint it, as long as you keep the plan that owns it.

  • Destination can be changed
  • Scan tracking included
  • The scan path is the vendor's domain
  • Codes stop resolving if the plan lapses
  • Redirect rules live outside your stack
Your domain, your rules

Redirect-backed QR with RedirHub

go.yourbrand.com/table-12

The code encodes a redirect URL on a domain you control. The redirect layer is the product, so the destination stays yours to change.

  • Repoint any code without reprinting
  • Branded redirect paths on your own domain
  • Scan analytics per code and per campaign
  • REST API and MCP for bulk updates

How it works

Four decisions that keep a printed code alive

The order matters — the first two happen before anything reaches a printer.

01

Create the redirect first

Set up a redirect like go.yourbrand.com/table-12 before anything goes to print. That URL is what the code will encode.

02

Encode the redirect, not the page

Generate the QR from the redirect URL. This single choice is what makes the printed code repointable later.

03

Change the destination anytime

Update where the redirect leads from your dashboard, the REST API, or an MCP-assisted workflow. Scans follow immediately.

04

Watch what the print is doing

Scan volume, geography, device, and referrer turn a physical asset into a measurable channel.

Why it matters

Print moves slowly. Campaigns do not.

Permanence

Print once

Packaging, signage, and collateral outlive the campaigns they advertise. A redirect-backed code keeps the print asset useful long after the offer behind it expires.

Control

Repoint in seconds

The destination is a setting, not a manufacturing decision. Change it for one code or thousands without touching anything physical.

Visibility

Offline becomes measurable

Every scan carries a place, a device, and a time. The gap between what you printed and what it produced finally closes.

Use cases

Wherever a code outlives the campaign behind it

Packaging, badges, signage, and collateral all get printed long before anyone knows what the destination should be a year from now.

Hospitality

Table cards & menus

Point today's scan at the seasonal menu, tomorrow's at a weekend offer, next month's at a reservation flow.

Retail

Product packaging

Boxes ship years before they are opened. Move the code from setup instructions to registration, reorder, or a recall notice.

Field sales

Business cards

One printed card that follows a new portfolio, a new calendar link, or a new role without another print run.

Events

Badges & signage

The same badge code walks attendees from registration to agenda, to check-in, to the post-event survey.

Support

Manuals & safety labels

Send owners to the current instructions, an updated video, or an urgent safety notice — long after the label was applied.

Campaigns

Flyers & out-of-home

Distribution finishes weeks before a campaign ends. Keep the audience you already reached pointed at what matters now.

Scan analytics

Printed codes should report back

A redirect sits between the scan and the destination, which is exactly where measurement belongs.

48.3K

Scans tracked

Across every printed code in the last 30 days.

37

Countries reached

Resolved to region and city for each scan.

82%

Scans from mobile

Split by device, browser, and operating system.

0

Codes reprinted

Destinations changed four times over the same period.

What you see with a redirect-backed code

redirhub.com/qr

Scan volume over time, per code and per placement

Country, region, and city for every scan

Device, browser, and operating system breakdowns

Which destination a code was pointing at when it was scanned

Campaign parameters preserved through the redirect

Raw scan data you can export or query by API

What you see with a static code

yourbrand.com/spring-menu (baked in)

No record that a scan ever happened

No way to tell which placement performed

No device or geography context

No history of what the code pointed at

Campaign parameters fixed at print time

Nothing to export, because nothing was captured

Over time

One print run, four years of different jobs

A single batch of table cards, followed across four years. The artwork on them never changed once.

  1. Day 1

    Codes printed

    10,000 table cards ship with go.yourbrand.com/table-12 encoded.

  2. Month 2

    Seasonal menu

    The destination moves to the spring menu. Nothing is reprinted.

  3. Month 7

    Website rebuild

    New URL structure lands. Redirects are repointed in one pass.

  4. Year 2

    Loyalty program

    The same cards start driving signups instead of browsing.

  5. Year 4

    Rebrand

    New brand, new site, same physical asset still sending traffic.

Why RedirHub

The redirect layer is the product, not a QR feature

Codes on packaging and signage depend on a redirect resolving correctly years from now. That is infrastructure, and it is what this platform is built around.

Branded redirect domains

Scans travel through a domain your customers recognize instead of a third-party shortener.

HTTPS on connected domains

Secure scan paths without certificate work, so the hop stays invisible to the person scanning.

Fast global redirects

The redirect hop is infrastructure, not an afterthought — built to resolve quickly wherever the code is scanned.

Bulk redirect management

Manage large code portfolios across packaging, retail, and events without hand-editing one at a time.

REST API

Create and repoint redirects from the systems that already run your campaigns and product catalog.

MCP support

Let AI-assisted workflows inspect and update redirect infrastructure alongside the rest of your stack.

Customer stories#

What people say about the redirect layer

Reviews of the RedirHub redirect service these codes point through, quoted from Trustpilot.

Quote

The UI is really easy to figure out, and it's very reliable. I especially like the easy URL shortener, far better than many of the alternatives. The redirects include SSL. Really generous free plan.

DA

Dax

Quote

I enjoy using RedirHub for its useful tools that help with my promotions. Its customer service efficiently helped me with my work.

DM

David Miller

Frequently asked questions

Only if the printed code encodes an active redirect URL. If it does, the destination behind that redirect can be updated at any time. A code that encodes a final web address directly cannot be repointed — the address is part of the pattern.
Scan it and look at the address bar as the page opens. If you briefly see a short redirect domain before landing on the final page, it is redirect-backed. If it goes straight to the destination, the destination is baked in.
No. The pattern encodes the redirect URL, and that URL never changes. Only the rule behind it does.
Yes. RedirHub supports branded redirect URLs on connected domains, so scans travel through a domain you own. Custom domains are included on every plan — two on Free, more on paid plans — with HTTPS issued automatically.
It is a normal HTTP redirect, resolved before the destination page starts loading. In practice people see the destination, not the hop.
Yes. Redirect analytics are included on every RedirHub plan, including Free. Each scan is recorded with volume over time, location, device, and referrer, and the data is available in the dashboard or through the API.
RedirHub is built to manage redirect records at scale, with bulk import and export and a REST API available on every plan. How many you can manage depends on your plan and setup.
Redirects resolve while the account and connected domain are active. This is worth planning for with any redirect-backed print run, whichever provider you use.