Which kind of QR code do you need?

Every printed QR code is physically fixed once the ink dries. What changes between “kinds” of QR code is where the meaning lives: in the printed dots, in a destination you control, or in a record a system looks up. Pick the approach that matches how long the object lives and how often its meaning changes, and the rest of the decision gets easy.

What are the main kinds of QR code?

There are three that matter in practice, plus specialised cases.

Approach	What the code holds	You change it by	Best when
Static payload	The final data (URL, Wi-Fi, vCard, text)	Reprinting	The data is small, fixed, and needs no tracking
Managed redirect	A short link you control	Editing the destination in a console	Printed material stays in circulation and the destination may change
Stable identifier + resolver	A durable identity (for example a GTIN)	Updating the record the identity resolves to	An object has a long life and its status changes over time

A managed redirect and a resolver are the two that keep a printed code useful for years. The static payload is the right tool when independence from any service matters more than editability.

Which of these does redireo handle?

redireo is built for the two durable approaches, on a domain you own.

• Managed redirect. The printed image never changes. You edit the destination in the console and the next scan follows the new rule, with no reprint. Every destination is reputation-checked before it goes live. This is the default for marketing links, campaigns, and any printed code with a long shelf life. See static vs dynamic QR codes.
• Stable identifier with a resolver. A GS1 Digital Link on your GTIN resolves to the current record for that product, so one code can lead to product information today and recall or reorder information later. See GS1 Digital Link vs a plain QR code.

Both can also resolve by context, sending a scanner to a different destination by country, language, device, or platform, because the routing logic lives in the resolver, not in the printed dots.

When is a static or specialised code the right tool instead?

Reach for a different approach in three cases, and use redireo for everything around them:

A static payload wins when the data is small and permanent and you want it to work with no service in the loop, such as a Wi-Fi password on a fridge magnet. A regenerated, short-lived code is the pattern behind payments, device login, and single-use tickets, where the code must bind to one transaction and expire; those belong to payment and authentication systems, not a redirect. A digitally signed offline payload is used where a scanner must verify a credential with no network. redireo does not issue those specialised codes, and that is by design: its job is the durable redirect and the owned resolver.

How do you choose in one pass?

Answer these in order and stop at the first “yes”:

1. Does the code represent a payment, a login, or a single-use ticket? Use the payment or authentication system that owns that flow.
2. Does the data need to work fully offline with no service? Use a static payload.
3. Is the code on a product with a long life whose record changes over time? Use a stable identifier with a resolver.
4. Otherwise: use a managed redirect so you can edit, measure, and route without reprinting.

The security of any of these comes from the surrounding controls, not from the barcode looking “dynamic.” A redirect can still be copied or covered by a fraudulent sticker, so pair it with the protections in what quishing is and how to reduce the risk.

Once you know the approach, get the physical code right with the print and scanning guide, and run it well with operating a dynamic QR programme.