A distributor of the fictional Nordvale has three NV-200 datasheets: one downloaded from the website in spring, one attached to a March email, one a colleague forwarded last week. The operating temperature differs between two of them, and they all look different. Before quoting, the distributor calls Nordvale's sales team to ask which is right. If they do not call, they quote from whichever file they opened.
Old datasheets keep circulating because a PDF does not update itself once it leaves your website. You cannot recall the copies. You can make the current one easy to recognise, and the old ones easy to spot.
Why old versions keep circulating
- Downloads are copies. A datasheet downloaded in spring stays the spring version in someone's folder, however often you update the website.
- Email is the main distribution channel. Sales attach whatever is on their laptop. Distributors forward what they received.
- Distributor portals and catalogues copy your files. Their copy changes when someone there remembers to change it.
- Versions look different for the wrong reasons. When each update was made from a different template, by a different person or from a different system, the look changes with every version, and the reader cannot tell a newer design from a newer specification.
Gartner reported in 2018 that B2B buyers spend around two-thirds of a buying journey gathering, processing and de-conflicting information (reprint of Gartner's release). Two versions of one datasheet is exactly the kind of conflict they spend that time on.
Make the current version recognisable at a glance
The aim is that anyone holding two copies can tell in five seconds which is newer, without opening a website.
- A revision and a date, in the same place on every datasheet. For example "Rev. C, 2026-11-13" in the footer of every page. Same place, same format, every product.
- One design for every version. When the layout stays the same, a difference between two copies means a difference in content, which is the thing the reader needs to notice.
- A pointer to the current version. One line such as "Current version: nordvale.example/nv-200", printed on the datasheet. A reader with an old copy finds the new one.
- File names that carry the revision. NV-200_datasheet_RevC_en.pdf, not datasheet_final2.pdf.
- Document properties that match. The title field in the PDF should name the product and revision, not an old product or a colleague's draft.
- A change note to distributors. When a specification changes, send distributors the new revision with one line on what changed. Ask them to replace, not add.
The ten-document self-audit includes a check for revision and date on datasheets; run it on the last ones you sent.
Declarations of conformity are different
A datasheet is a sales document. A declaration of conformity is a legal one, and the rules are stricter.
EU product legislation follows a model set out in Decision No 768/2008/EC. Its model declaration starts with a unique identification of the product and an identification "allowing traceability", and the decision says the declaration "shall be continuously updated" and translated into the languages the Member State requires (Decision 768/2008/EC, Annex I Article R10 and Annex III). The exact wording that applies to your product is in the directive or regulation for its sector.
So a distributor holding an outdated declaration has an outdated compliance document, which is worse than an off-brand one. If your company is certified to ISO 9001, its document control clause (7.5.3 in the 2015 edition) already asks for version control and for documents to be available and suitable for use where they are needed (clause summary). Your quality team probably controls declarations already. The question is whether the copies your sales team and distributors send match what quality controls.
What a declaration must contain is for your quality team and, where in doubt, your notified body or lawyer. We format declarations; we do not decide their content.
Where the routine stops working
The six steps above hold as long as one person makes every datasheet from one template. They break down when:
- Datasheets come from several places. Some from Word, some exported from Excel or a product database, some from the ERP. Each has its own footer, so the revision ends up in a different place each time.
- There are several languages. Each translation is another file to keep on the same revision.
- The person who knew the routine moves on. Revision letters stop being updated, and the drift starts again.
At that point the design, including where the revision goes, has to live outside each file, so every datasheet comes out the same whatever made it. Our guide on consistent documents covers the options.
How to make distributors use the current datasheet
Doing it by hand, as above, depends on whoever edits each file remembering the revision line. What we do is move that routine into the template. We build one datasheet template from your brand: logo, fonts, colours, fixed text and fields. The fixed text can carry a line that points to your datasheets page; a link to one product's page comes with that datasheet's content. Datasheets then come out in that design whether the content arrives from a Word or Excel upload, the API or an MCP-connected agent.
The datasheet profile can also require labelled fields such as Revision and Date. If a required label is missing or empty, the PDF is refused instead of going out without it. That check covers whether the label is in the content, not where it sits on the page; the position follows how the template and the content are set up.
What we do not solve. We cannot recall copies already sent, and we cannot make a distributor replace a file. We do not keep your documents by default either (see how we handle data), so we cannot act as the place where the current datasheet lives; that stays your website or portal. What we change is that every new datasheet leaves with a revision and the same design, so a distributor holding two copies can see which is newer.
Setup takes up to five working days, usually less, with one review round on samples. You can get a free sample pack of up to three documents, checked by a person and sent within five working days. The samples carry a watermark and placeholder prices.
Questions
Do datasheets legally need a revision number?
We found no general EU requirement for marketing datasheets to carry a version. Declarations of conformity are different (see above), and your quality management system or your customers' contracts may require it for datasheets too. A revision and date cost one line and save phone calls either way.
Can we stop old PDFs from circulating?
No: once a file is sent, it is out of your hands. What you can do is make every copy say which revision it is and where the current one lives, so an old copy points its reader to the new one.
Should we put a QR code on the datasheet?
A QR code to the product page works if the link stays stable for years. A short printed web address does the same job for readers on paper or a screen, and it does not depend on a camera.
Where we fit
Your company's document templates, built and maintained for you.
- Built and maintained for you. We turn your brand guide into templates for offers, datasheets, declarations of conformity and reports, and keep them right as things change.
- Every source, one design. Your team uploads Word or Excel, your systems call the API, your AI tools connect over MCP. API and MCP are on every plan.
- One price for the company. No seats. From $99 a month plus $490 setup for one document type (pricing). Hosted in the EU, with a DPA.
We deliver finished PDFs. If your team edits Word all day, template software suits you better. And if your documents come from one source and one person already keeps the template right, you do not need us.
If your datasheets come from one template and one person updates them, the routine above is enough. We are for the point where they come from several systems and languages.
Sources
- Decision No 768/2008/EC, Annex I Article R10 and Annex III (as adopted), accessed 13 November 2026
- Explaining ISO 9001 clause 7.5.3, control of documented information (Auditor Training Online, 2023), accessed 13 November 2026
- Gartner says B2B buyers want more simplicity in accessing the right information (reprinted by MacTech, 20 August 2018), accessed 13 November 2026