You went looking in the Shopify admin for the QR code settings and could not find them. That is because they are not there. QR codes are not a built-in Shopify feature. Every QR code option for a Shopify store comes from a third-party app in the App Store, installed and billed separately.
That one structural fact drives every tradeoff in this comparison, so it is worth understanding before you install anything.
Codes come from apps, not from Shopify
The App Store lists a category of QR apps built specifically for merchants. They bind codes to things that exist inside your store: individual products, collections, discount codes, orders, and pickup or fulfillment flows. Billing runs through your Shopify account per app, commonly with a short free trial. Some apps offer a free plan and some do not, so read the listing rather than assuming.
Because these apps are separate businesses, quality, support, and longevity vary widely across the category. Some listings are mature with years of reviews. Others are new or thinly reviewed. That variance is not a criticism of any individual developer; it is a fact about app marketplaces generally, and it should shape how you evaluate a listing.
What the integration genuinely buys you
A standalone generator cannot match integration depth, and it would be dishonest to pretend otherwise. An app that lives inside your store has access to data an outside tool does not. Depending on the app, that can mean:
- Generating a code per product or collection automatically, pulling the correct URL without anyone typing it.
- Attaching a discount so the scan applies the offer at checkout instead of asking the customer to copy a code.
- Placing codes into order, pickup, and fulfillment flows rather than bolting them on afterward.
- Regenerating in bulk when the catalog changes, without exporting a spreadsheet first.
- Keeping billing on one invoice with the rest of your Shopify stack.
For in-store pickup, warehouse operations, and anything tied to order state, that access is the whole point. If your use case is "customer scans the shelf tag and lands on the right product page with the right promotion applied," an app is doing work no external tool can do.
We cover the retail side of this in more depth in our notes on QR codes for retail.
The dependency to plan around
Here is the risk that deserves a careful reading rather than a scare story.
Codes generated by an app generally depend on that app staying installed and subscribed. The redirect that makes a dynamic code work is typically served by the app vendor's infrastructure. Uninstall the app, let the subscription lapse, or migrate off Shopify, and live codes can stop resolving.
That matters in proportion to where the codes are. A code on a screen is trivially replaceable. A code printed on ten thousand product boxes is not. If the physical artifact will outlive your app subscription, you have coupled a printed asset to a software dependency, which is a decision to make deliberately rather than by accident.
Concrete questions to ask before printing anything durable:
- What happens to existing codes if I uninstall or downgrade?
- Does the vendor let me export the list of codes and their destinations?
- If I replatform off Shopify in three years, do the codes survive?
- Is there a documented policy, or am I inferring from a support reply?
This is the same class of problem we wrote about in what to do when a QR code generator shuts down, and the mitigation is the same: know where the redirect lives, and keep your own record of every destination.
Reading an App Store listing properly
Before installing, spend ten minutes on these:
Review volume and recency. A handful of reviews from one month tells you very little. Steady reviews across a couple of years tell you the vendor is still there.
Pricing and terms on the listing itself. Plans and limits differ per app and change over time. Read the current listing rather than a blog post, this one included.
Support responsiveness. Look at how the developer answers negative reviews. That is the support you will get.
Export options. Ask what file formats you actually receive and at what resolution. Do not assume vector is available; confirm it for the specific app before promising a printer anything.
Where a standalone generator fits
Standalone tools win in three situations:
Print runs meant to outlive a subscription. Packaging, signage, printed catalogs, anything with a multi-year life. You want the redirect owned somewhere independent of your storefront platform.
Codes that are not about a product. A code on a delivery insert pointing at a review page, a support portal, a returns form, or a recruiting page has nothing to do with your catalog and gains nothing from store integration.
Large batches from your own data. If you already have a CSV of URLs, a bulk QR code generator turns it into files directly, without going through a store object model that may not match how your data is shaped.
For any of these, generate a dynamic code so the destination stays editable, and export at the resolution your printer asks for. Our PNG export guide covers the raster settings; for anything large-format, ask your printer for vector before committing.
Splitting the job
Most stores past a certain size end up running both, and that is the right answer rather than a compromise. Use the app for anything that needs live store data: product-level codes, discount attachment, order and pickup flows, shelf tags that change with the catalog. Use a standalone generator for anything printed to last, anything unrelated to the catalog, and anything that must survive a platform change.
Open your Shopify admin, list every QR code currently in circulation, and mark each one as either store-data-dependent or print-durable. The second group is the one to move off the app and onto codes whose redirect you control. Start there.
