Quick answer
A printed QR code holds a fixed URL. Once it is on packaging, signage, brochures or instruction sheets, changing that URL means reprinting the lot.
If the code points at a PDF on your site and the document needs correcting, keep the URL and replace the file behind it — as long as the new file is still the same document.
Then scan a real printed code and check it gives you the new file. If it does not, look at caching before you replace anything a second time.
WP Bulk Replace does not make or manage QR codes. It handles the file at the other end of one.
Why a printed code raises the stakes
A link on a web page can be edited.
A QR code printed on product packaging, a restaurant menu, an equipment label, an installation card, a brochure, event signage, a building notice, a manual or a warranty card cannot.
Once it is printed, that URL is part of a physical object sitting in somebody’s warehouse.
Does the code mean “current”, or “this edition”?
Replacing only makes sense if the link was meant to stay put.
Fine to replace. The code says “Scan for the current installation guide.” The guide gets corrected. The URL should carry on serving whatever the current guide is.
Not fine to replace. The code is printed on a 2025 product and deliberately points at “Installation Guide — Revision A”. Replacing that with Revision D means somebody scanning a 2025 box gets instructions for a product they do not have.
Somebody has to decide which of those the code means. Nothing about the file can tell you.
How to do it
1. Scan the code first. Find out where it actually goes before you change anything. It might point at the PDF directly, at a redirect, at a landing page, or at a third-party shortener — and the answer changes what you need to do.
2. Confirm it is the same document. A correction, or a different edition?
3. Replace the file behind the existing link rather than uploading a new one.
4. Open the URL directly and check the content.
5. Scan an actual printed code, if you can get hold of one.
6. Try another device. A phone that scanned it last week may still have the old PDF.
Why caching is especially confusing here
QR workflows get tested on phones, and both mobile browsers and CDNs cache hard.
Which produces a very common wrong conclusion:
“The QR code is still pointing at the old file.”
The code is fine. The URL is fine. The replacement worked. Something in between is holding an old copy, and replacing the file again will not touch it.
A better shape for the next print run
For new projects, point the code at a page rather than a file:
example.com/manual/model-410/
Then the page can point at whatever the current file is. You get to change the file path later, explain what changed, add analytics, link older versions, and switch file formats — all without reprinting anything.
If thousands of codes already point straight at a PDF, replacement is how you keep them working.
Doing it for a whole product line
A manufacturer with 80 product manuals, each behind a QR code on packaging, runs a revision cycle:
- 70 obvious same-model replacements
- 6 files renamed for renamed models
- 2 discontinued products
- 2 brand-new products.
A batch keeps those four apart: replace, review, exclude, publish new. The codes themselves are somebody else’s job; getting the right PDF behind each one is this one.
Summary
A printed QR code makes a URL expensive to change.
If it means “the current document”: keep the URL, replace the file, and scan a real code afterwards.
If it identifies a specific edition, leave that edition alone.
Related: PDF linked from email · Files linked from printed material · Replace PDF without breaking links