QR codes are having their second life, and business cards are one of the best places to use one. But most QR cards fall down on the same detail: not the code itself, but the page it opens. The code is a doorway. What matters is the room behind it.
Point it at a card, not a file
The classic mistake is linking the QR to a PDF or a plain contact file. The person scans, a download starts, and now they are staring at a file instead of a page — with nothing to tap and no obvious next step.
Link it to a live digital card instead: a real page with your photo, tappable contact rows and a one-tap save button. Scanning should feel like arriving somewhere useful, not like starting a download.
Static vs dynamic — and why it matters
A static QR bakes the destination in forever; if that destination is a specific PDF, you can never change it without reprinting. A QR that points to a hosted card page is effectively dynamic: the code stays the same, but you can update the card behind it any time — new number, new role, new links — and every printed code keeps working.
That is the quiet superpower of a card-backed QR. Print it once, on a badge, a sticker, the back of a paper card, and it never goes stale.
Printing it so it actually scans
Keep the code at least 2cm across, keep a clear quiet zone of empty space around it, and keep strong contrast — dark code on a light background. Do not stretch it, tint it into your brand colour until it is unreadable, or bury it in a busy photo.
- Test the printed code with two or three different phones before you order a batch.
- Add a short line of text under it — “Scan to save my contact” — so people know what it does.
- Use the same code online and in print, so one link is all you ever share.
OneSol builds the QR into every digital card automatically, pointing at a page you can edit any time, with the save button already there. Make one free at onesol.io/card.
Static vs Dynamic: The Choice You Can't Reverse Later
The single biggest QR mistake is baking the wrong kind onto something you can't reprint. A static code has the destination encoded directly in the pattern — change where it should go and you've got a new code, so every printed card is now wrong. A dynamic code encodes a short redirect you control, so the printed pattern never changes but you can repoint it whenever you like. For anything you print in quantity, you want the dynamic sort.
The practical consequence shows up the day your number changes or you launch a new booking page. With a static code on five hundred cards, you're either reprinting or living with a code that leads somewhere stale. With a dynamic one pointing at a card page you own, you edit the page and every card ever handed out is instantly current. The pattern on the paper is just a signpost; keep the destination editable and the signpost never expires.
There's a related trap: generating a 'free QR' through a random online tool that quietly switches the redirect off after a trial, or vanishes entirely. If the code routes through a service you don't control, your cards die when that service does. Generate it from the same place your card lives, so the code and its destination are one thing, not two you have to keep alive separately.
Printing It So It Actually Scans
A QR that looks fine on screen can be unscannable in print, and you won't find out until you're at a stand watching someone's camera fail to lock on. Give it room: keep a clear quiet zone — a margin of empty space — around all four sides, because a code crammed to the edge or overlapping text often won't read. As a rough floor, print it no smaller than about two centimetres square for a handheld card, larger for anything scanned from a distance.
Contrast does the heavy lifting. Dark code on a light background scans reliably; the fashionable inverse — a light code on dark, or a pale code tinted to match your brand — is where scans quietly fail under real lighting. If you must colour it, keep the code markedly darker than its background and test it, rather than trusting how it looks in the design file. And never lay it over a busy photo.
Then test the finished, printed card, not the mockup. Scan it with both an iPhone and an Android camera, in ordinary indoor light, from the distance someone would actually hold it. Do it from a matte print and, if you can, a glossy one — glare on gloss can defeat a code that scanned perfectly on matte. Five minutes of testing saves a whole print run.
Point It at a Page You Own, Not a Dead End
A QR is only as good as where it lands, and the common error is pointing it straight at a single platform — a raw Instagram profile, a PDF on some file host — rather than a page you control. Send it instead to your own card or link page, and from there people choose: save your contact, book, message, follow. One scan, several doors, all of them yours to rearrange.
Mind the landing experience too. The page behind the code should load fast on mobile data and make the next step obvious within a second of opening — no cookie wall, no app-install nag, no pinch-to-zoom PDF. Someone who scanned out of mild curiosity will give you about two seconds; a heavy or confusing page spends that goodwill before they've done anything.
Above all, avoid routing through anything you might lose. A QR tied to a specific app account, a shortened link from a service that may sunset, or a trial-limited generator all leave your printed cards one shutdown away from leading nowhere. Owning the destination is what lets a code you printed today still work in three years.