But fixed information does not necessarily mean a fixed online experience. If the code contains a URL you control, you can update the page at that address without replacing the printed code. GS1 explicitly describes updating a linked experience while leaving the barcode and packaging unchanged. [2]
Static is often enough when you can keep the encoded information useful for the life of the printed material. For a website link, that means maintaining the address—not freezing the page forever. This is the practical decision rule used in this guide.
What stays fixed—and what can change?
Separate these three layers:
| Layer | What happens after printing? |
|---|---|
| Encoded data | The text or URL represented by the printed pattern stays fixed. |
| Content at that URL | The website owner can update the linked experience without changing the pattern. |
| Redirect destination | If the encoded URL uses a redirect, whoever controls that redirect can change where it sends visitors. |
The distinction follows the fixed-data definition, GS1’s explanation of updatable linked content, and the way HTTP redirects operate. [1][2][3]
For example, a restaurant could encode https://example.com/menu. Updating the menu page would not require a new QR code. If the restaurant moved the page, it could preserve the old address with a redirect—provided it still controlled that address. HTTP redirects are specifically used to keep existing links working after URLs change. [3]
How is that different from a dynamic QR code?
In common website-link usage, a dynamic QR setup puts a stable intermediary URL in the symbol and manages the destination behind it. The printed pattern does not rewrite itself; the routing changes. OASIS describes this distinction as changing the destination while the embedded short URL remains the same. [1]
That routing does not have to come from a QR-code subscription service. A website administrator can manage redirects, and GS1 documents the same principle for Digital Link addresses. The important question is who controls and maintains the encoded URL. [3]
When a static QR code is enough
The following are editorial recommendations based on the distinction between fixed data and changeable web content—not results from device or print testing.
You control a stable web address
Consider static encoding for a brochure linking to your support page, a business card linking to your website, or signage linking to a maintained information page. The page can evolve while its address stays usable. GS1’s packaging guidance demonstrates this same fixed-code, updated-experience arrangement. [2]
For a PDF that will be revised, consider linking to a maintained download page rather than a file address you expect to replace. This recommendation follows the Department of Energy’s warning that address changes break QR links unless redirected. [4]
The information itself can remain fixed
Directly embedded text can suit a short, unchanging message. Embedded contact details can also be reasonable if you accept replacing the code when those details change. Unlike a linked profile page, the directly encoded information cannot be updated behind the scenes. [1]
Website-level measurement meets your needs
Static does not mean untrackable. A static code can contain a URL with UTM campaign parameters. With Google Analytics collecting data on the destination site, those parameters can identify campaign-referred traffic. That is an application of Google’s documented campaign-URL method, not a built-in reporting feature of the QR symbol. [5]
Treat the resulting website visits as website measurement—not proof that every camera scan was counted. Google’s method reports traffic reaching Analytics through tagged URLs; it is not a counter embedded in the printed code. [5]
When you need more than direct static encoding
Consider managed routing when you need to change destinations after printing but cannot maintain the original address yourself. Redirects work through the server handling the encoded address, so control of that address matters. [3]
If a campaign requires reports, routing rules, or access controls, write those requirements down before choosing a system. Do not assume the label “dynamic” guarantees a particular feature. The symbol, routing service, and measurement setup are separate parts of the implementation. This is an editorial purchasing precaution based on the architecture described above. [1]
Expensive-to-replace packaging is not automatically a reason to choose either type. Instead, make continued URL control and maintenance a requirement. GS1’s guidance shows that printed static data can still connect to updated digital content. [2]
Before you print: a practical checklist
- Check the decoded information. Confirm that the code contains your intended text or URL. Record who controls any intermediary address or redirect. This follows from the fixed-data and redirect distinction. [1]
- Preserve the quiet zone. DENSO WAVE specifies a clear margin four modules wide on every side of a standard QR Code. A module is one small square in the pattern. [6]
- Avoid obstructing the pattern. DENSO WAVE warns that illustrations and overlays can deform a code and impair reading. [7]
- Label it and provide an alternative. Add a clear purpose, such as “View the menu,” plus a readable web address. DOE recommends adjacent destination text and accessible placement. [4]
- Test before committing. DOE recommends testing with a mobile phone. As an additional production precaution, check a proof at its intended size and placement, then assign someone to maintain the destination. These are recommended checks; no physical testing was performed for this article. [4]
References
[1] OASIS, Secure QR Code Authentication Version 1.0 — https://docs.oasis-open.org/esat/sqrap/v1.0/os/sqrap-v1.0-os.html
[2] GS1, 2D Barcodes at Retail Point-of-Sale Implementation Guideline, sections on web content and redirection — https://ref.gs1.org/guidelines/2d-in-retail/
[3] MDN, Redirections in HTTP — https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Redirections
[4] U.S. Department of Energy, QR Code Standards and Best Practices — https://www.energy.gov/cmei/communicationstandards/qr-code-standards-and-best-practices
[5] Google Analytics Help, URL builders: Collect campaign data with custom URLs — https://support.google.com/analytics/answer/10917952?hl=en
[6] DENSO WAVE, Point for determining the code area — https://www.qrcode.com/en/howto/code.html
[7] DENSO WAVE. Generating a QR Code. https://www.qrcode.com/en/howto/generate.html



