Use cases
Anywhere the link outlives the reason you printed it.
The test is simple. If you can't recall what you've already sent out, and the destination will change, it's a LinkShift code.
Restaurants and cafés
One table tent, laminated once. Brunch menu on weekend mornings, happy hour in the late afternoon, the full menu the rest of the time, and the closure notice over the holidays, scheduled in October so nobody has to remember.
Conferences and events
The QR on the badge goes to the agenda before the keynote, the slides during it, the feedback form right after, and the recording a week later. Four destinations, one print run.
Product packaging
Registration while the return window is open. Setup guide after. Reorder page once the consumables should be running out. The box was printed in a factory months ago.
Signage and vehicle wraps
The wrap costs more than most websites. The offer on it changes every season. Point the code at this quarter's landing page and leave the van alone.
Real estate
The sign goes up once. Listing details, then open-house times on the day, then "under contract," then the agent's next listing.
Classrooms and venues
The poster by the door points at today's schedule, this week's reading, or the form for whichever thing is happening in the room right now.
Books and publishing
A book is read for ten years and printed once. The companion link in chapter nine points at whatever your site looks like now, not what it looked like on the print deadline. Ebooks have the same problem in a quieter way, because the copy already on someone's device is the copy they'll open.
Product labels and compliance
The EU is phasing QR codes onto physical goods: battery passports from February 2027, then textiles, electronics and tyres. That label stays on the product for its whole life, what sits behind it changes as the product does, and somebody has to be able to show what it said last March.
Equipment and asset tags
The tag on a machine outlives three revisions of the manual and two service contracts. Point it at the current revision and the number that's answered today, without sending anyone into the field with a label printer.
Museums, trails and memorials
A placard is installed for a decade. The exhibit behind it gets re-hung every season and the audio guide moves the next time the site is rebuilt. The plaque doesn't move.
The part nobody asks until later
What happens if we go away?
It's the right question, and it's the most common way a printed code dies. Not a bad schedule: a trial that quietly ended, a plan that lapsed, a company that got acquired and switched the redirects off. The pattern on the box is fine. The server behind it isn't.
So print your codes under your own hostname. You add two DNS records, the codes carry your domain, and if we ever stop existing you repoint one record and every code you've printed keeps working. You own the namespace, not us. That's the whole answer, and it's why custom domains matter more here than they do for a link shortener.
And when it's not
Where you don't need this.
If the link lives on a screen, you can just change it. A short-link tool is cheaper and simpler for tweets, emails and bios, and several good ones are free.
If the destination is never going to change, any QR generator will do. LinkShift earns its keep when ink is permanent and the answer isn't.