App store QR code how to
SmartQRCode editorial · Updated October 2026
App store QR code how to is the iOS listing half of the App type: paste an apps.apple.com listing onto a hosted download page, optionally with Play Store as sibling. The carton stays when the listing URL moves. If that one App Store URL is frozen and uncounted, a Canva static file is the smaller job.
App store QR code how to
You are still on the App landing-page type, not a special Apple-only encoding. App Store URL is one of four link fields. At least one link is required. The honest iOS job is the apps.apple.com listing copied from the product page, not a search URL, not apple.com, not a redirector you do not control. The printed modules encode SmartQRCode. A bundle ID change is a dashboard paste, not a reprint, unless you encoded the store URL statically.
one code two stores is the usual design: App Store plus Play on one page, one scan total. Two printed codes are for two counts, not for two operating systems. The landing will not hide Play on iPhone.
Skip this when the listing is immortal and uncounted. Encode the App Store URL in Canva. Skip it when the job is a trailer. Use Video. Paid options are $1.99, $29, $97, or $197. There is no unpaid tier. The full type walkthrough is how to make an app QR code.
Use the apps.apple.com listing, not a search
- Pick App. Fill App Name first.
- Open the App Store product page on a desktop. Copy the apps.apple.com listing from the address bar.
- Paste it into App Store URL. Confirm it opens the product, not a search, not a category, not a country picker loop.
- If you ship on Android, paste Google Play URL as Play Store as sibling. Same rule: the product listing, not a search.
- Add Amazon or Website only if those are real destinations.
- Scan the paid code on an iPhone and on an Android phone. Each should still see both buttons if you pasted both. The preview before payment is /qr-preview.
- Export SVG for a cutter, or 300 dpi PNG or PDF for carton print. Packaging distorts on curves. Test-scan the formed pack, rather than stopping at the flat proof.
- Size: 2 cm across at about 30 cm for a box in hand. Larger if the code is on a shelf strip read from the aisle.
The app generator is the tool. Website URL is the raw hop if you do not want our download card.
Should you print two codes for two stores
should you print two codes for two stores is a measurement question. Two symbols give two scan totals. One symbol gives one total and both links. If the campaign question is which store the poster drove, print two. If the question is whether the crate was scanned, print one. Do not print two because you think iPhone cannot see a Play button. It can. It just may not care.
Transit ads and packaging often want one code. Store-specific magazine inserts sometimes want two. Decide before the plate.
What URL belongs in App Store URL
what URL belongs in App Store URL is the product listing. Campaign landing pages that then JavaScript-redirect to the store fail in in-app browsers. Country-specific listings (/app/id... versus /gb/app/...) should match the market on the box. If you localise later, edit the field. That is the hosted point.
A bundle ID change after a rebuild is the same edit. The shrink sleeve does not know. A static App Store QR in the modules still points at the old id. That print is then a 404.
iPhone cameras that open Play by mistake
They did not. The guest tapped Play. The landing showed both links. If that is unacceptable, omit the Play URL on that code and print a second code for Android, or live with one page. Do not blame the camera. iOS Camera and Android Camera / Google Lens both read a well-formed symbol. Low light and shrink-wrap glare fail more often than the wrong app.
Shrink, curves, and a formed-pack test scan
Flexo, shrink, and curves distort modules. A flat proof that scans on a desk can fail on the formed sleeve. Test the pack you ship. Metallic grounds scatter. Print the symbol on a solid white patch. Uncoated board drinks ink. Compensate with a slightly larger symbol or a coated stock, not by dropping error correction.
Export SVG for a cutter. Export 300 dpi PNG or PDF for toner. Quiet zone of four modules, kept off the shrink seam. Size: 2 cm in the hand, larger on a shelf strip read from the aisle. Error correction H if you add a logo or the pack scuffs.
Scan totals do not equal installs. They equal scans. Pause and archive are different states. A hosted listing page lasts as long as the provider resolves it. A static apps.apple.com symbol in the modules has no such dependency and cannot follow a bundle ID change.
A test scan on a formed sleeve with a phone that has never installed the app is the only proof that matters. Confirm the App Store URL field still matches the live listing, that Play is present only if you meant it to be, and that the camera is reading the printed modules rather than a leftover on-screen preview. If the landing title is the internal SKU, change it before the run leaves the building.
When a static App Store QR is enough
when a static App Store QR is enough is a one-SKU iOS app whose listing URL will not move and will not be counted. Generate it in Canva or an in-app tool. You are done.
Use the hosted App type when Play sits beside App Store, when the listing may move, when the pack must report scans, or when you want a named download card. Export a printer file at the real millimetre size. Keep /qr-preview off the plate. Keep the quiet zone off the shrink seam. A hosted download card is still a landing page: editable after print, with scan totals. It is not a silent hop into the App Store on the first scan.
Questions this raises
Only if you want two scan counts. One hosted page can carry App Store and Play together.
The apps.apple.com listing, not an App Store search, not a marketing site that looks like the store.
When that listing URL will never move and you do not need counts. Encode it in Canva or another static generator.
No. The landing shows the links you pasted. It does not silently pick a store by OS.
Paste the new listing URL. The packaging stays. A static App Store QR in the modules cannot follow a bundle ID change.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.