Quick answer
If a product page should always offer the current manual, replace the file behind it. That keeps every existing link working — from the website, from emails, from QR codes on packaging, and from service documentation.
If customers still need manuals for older models or revisions, publish those separately instead of overwriting them.
For a large refresh: upload the files together, map them by model, document type and language, check the close matches, replace only the current manuals you approved, and open the real public links afterwards.
Manual links outlive almost everything else
A product manual stays useful for years, and its URL ends up on product pages, in QR codes, on packaging, in installer emails, in service tickets, in knowledge-base articles, on distributor sites, on printed labels and in search results.
Change that URL and you break references in places you cannot reach.
What does the page mean?
“Download Manual” on a product page should always serve the latest approved manual for that model. Replace the file.
“Manual — Revision B” is a specific revision. Revision C gets published separately.
“Manuals for discontinued products” is an archive. Never replace an old model’s documentation with the current generation’s.
Model numbers need care
Manual files are named by product code:
xg410-manual.pdfXG-410A_Install.pdfxg410-revC-en.pdf
Near-identical models deserve a proper look. A matcher can suggest candidates all it likes; it must not assume 410 and 410A are interchangeable, because on a product page they are two different machines.
Languages
A product may have English, Spanish, French and German manuals.
The language is part of which document this is. A batch must not collapse them together because the base product name matched — that puts the German manual on the English page and reports success.
QR codes and packaging
If a QR code on installed equipment points straight at the manual, that URL is effectively permanent.
Replacing the file is often the cleanest way to update a current guide without invalidating the code.
But if the code was deliberately tied to a specific model revision, replacing it with a different edition is wrong. Scan a real printed code after you replace anything.
Manuals shared by a family
One guide may cover a whole series:
XG 400 Series Installation Guide
linked from five product pages.
If the new guide still applies to all five, replacing the shared file is exactly right. If one variant has diverged, give it its own document before the overwrite.
Example: an annual manual refresh
A company receives:
- 60 revised manuals
- 12 translations
- 5 manuals for newly launched products
- 3 legacy manuals that should not be touched.
A safe run: upload all 80, map the existing models, look carefully at the close model numbers, map the language variants, mark the 5 new products as new, exclude the 3 legacy files, back up, replace the current manuals, then check the product pages, the QR links and the cache.
Replacing a manual is not approving it
The plugin does not know whether engineering approved this manual, whether legal approved the warnings, whether this is the revision currently in force, whether the PDF is accessible, or whether your retention requirements are met.
It manages where the file goes and what happened. Everything else is yours.
A better shape for new products
For future launches, consider a stable support route:
/support/model-xg410/manual/
rather than putting the raw uploads path on everything.
That page can point at the current manual, the translations, older revisions and related support — and you can change any of it later without reprinting a label.
None of which helps with the direct PDF links already in circulation. For those, keeping the file where it is remains the answer.
A correction, or a new revision?
Fixing a typo inside Revision C reasonably replaces Revision C.
A new Revision D probably deserves its own identity in the archive.
Your organization decides where that line sits. A common arrangement is a stable “current manual” link pointing at the latest revision, with the support archive keeping every named revision.
Equipment still in the field
Products stay in service long after they stop being sold.
Before replacing or removing manuals, think about the hardware generation, firmware compatibility, the installation method and the safety instructions.
That is why a legacy archive usually matters more than the tidiness of removing it.
Checking translations
When several translated manuals update together, look at the actual product page and check the language labels.
A perfectly correct file can still be sitting in the wrong language slot, and nothing about the file will tell you.
Summary
Manual updates are safe once the product identity and your revision policy are explicit.
Replace for the current manual, a corrected guide, and a stable QR-linked page.
Publish new for legacy models, separate revisions and archived manuals.
Related: Manufacturer product documents · Updating a PDF behind a QR code · Technical data sheets