---
title: "Guides — how to run the job, not just make the code"
description: "Worked examples for menus, app stores, packaging, split tests and protected codes, each honest about what it will not do."
canonical: https://reroutehq.com/resources
---

# Guides

Each guide covers a whole job rather than just making a code, and each one states plainly what the approach will not do.

## [How to put a QR code on a menu you can update without reprinting](/resources/restaurant-menu-qr-code)

*Restaurants, cafes, bars and hotels*

One code on the table tent that opens lunch at eleven and dinner at five, without a second print run.

## [How to A/B test a printed QR campaign and measure real conversions](/resources/ab-test-printed-qr-campaign)

*Marketers who have to justify a print budget*

Split traffic from a single print run between two destinations, and match the sale back to the scan that caused it.

## [How to send iPhone and Android users to different app stores from one QR code](/resources/app-store-qr-code-ios-android)

*App teams and anyone printing a download prompt*

One square on the poster that opens the right store for whoever scanned it, decided at the moment of the scan.

## [How to get packaging ready for GS1 Sunrise 2027 with a Digital Link QR code](/resources/gs1-digital-link-packaging-2027)

*Packaging, CPG and private-label teams*

Register a GTIN, point it at the destinations retailers and shoppers each need, and test it before artwork goes to print.

## [What is a GS1 Digital Link? The web address inside the new product QR codes](/resources/what-is-gs1-digital-link)

*Brands, packaging and supply-chain teams*

The definitional companion to the packaging guide: what the standard actually is, how a scan resolves, and what a resolver does.

## [How to password-protect, expire, or scan-limit a QR code](/resources/password-protect-expire-qr-code)

*Events, ticketing and internal comms*

For codes on things that stop being valid: a door ticket, a limited run, a document that should not outlive its meeting.

## [How to choose between a static and a dynamic QR code](/resources/static-vs-dynamic-qr-codes)

*Anyone about to print a code and unsure which kind*

The difference is not quality or scanning speed — it is whether the destination lives in the ink or behind it. That decides everything else.

## [How to make a digital business card you can update after printing](/resources/digital-business-card)

*Sales teams, founders, consultants and real estate agents*

One code on the card that opens your details as they are today, not as they were at the print shop.

## [How to put a QR code on a yard sign that outlives the listing](/resources/real-estate-yard-sign-qr-code)

*Agents, brokerages and property managers*

The sign is the durable object, not the listing. Give each sign a code you repoint as properties come and go.

## [How to run QR codes across an event — badges, booths and sessions](/resources/event-conference-qr-code-signage)

*Event organisers, conference teams and exhibitors*

Codes for the whole run of an event: the save-the-date, the badge back, the booth banner, and the swap to recordings after everyone goes home.

## [Leaving Bitly: what moves, and what stays dead](/resources/leave-bitly)

*Teams migrating off Bitly or Rebrandly*

The destinations come with you. The printed bit.ly square does not. Import creates new addresses; it cannot take over the old ones.

## [Running Bitly and reRoute together until the print run turns over](/resources/bitly-dual-run)

*Teams with bit.ly already on menus, posters or packaging*

Keep Bitly live until the print turns over. New rrte.link on the next run. Drain the codes people actually scan.

## [How big to print a QR code](/resources/qr-code-print-size)

*Anyone about to send a QR code to a printer*

Size follows scan distance, with a 2 cm floor for close range. Quiet zone and contrast matter as much as the millimetres.