Product catalogues · Guide

Catalogue version controlUpdating a technical catalogue without inconsistent specifications.

How marketing, engineering and sales should approve revisions so print, PDF and website stay in step.

The first edition of a technical catalogue is the easy part. The hard part is the second, third and fourth — when specifications change, products are added and dropped, and three departments all want edits. Without a clear revision process, catalogues drift: the PDF says one thing, the printed copy another, and the website a third.

Why catalogues become inconsistent

Inconsistencies rarely come from one big mistake. They come from small, untracked edits: a value corrected on the layout but not in the master data, a product added to the PDF but not to the index, an urgent change emailed to the designer and never recorded. Version control is simply a way of making every change go through the same path.

Keep one source of truth

The master product spreadsheet — not the design file — should hold every specification. Changes are made there first, given a revision number, and then flowed into the layout. Our guide to preparing catalogue product data explains how to set up that spreadsheet.

Who approves what

  • Engineering / product management — technical values, standards, ratings and drawings
  • Marketing — product names, descriptions, structure and layout
  • Sales — which products and variants are still offered, and in which markets
  • One coordinator — collects changes, keeps the change log and sends a single approved list to the designer

Separate approvals matter because each team can only vouch for its own area. A designer should never be the person deciding whether a value is right.

Keep a change log

A change log can be a simple sheet with one row per change: date, product code, page, field, old value, new value, reason, requested by and approved by. It turns "who changed this?" into a ten-second lookup, and it gives the next edition a ready list of what has moved since the last print run.

Name and date every edition

  • Edition number and date on the cover or inside front page
  • The same edition reference in the PDF file name
  • A short "what changed" note sent with each new edition
  • The website PDF replaced at the same URL, so old links get the current version
  • Previous editions archived internally, not deleted

Planned editions and urgent corrections

Batch most changes into planned editions so that print and PDF stay in step. Keep a separate, faster route for urgent corrections — a wrong pressure rating cannot wait for the next edition — but put those through the same approval and change log, and update the PDF and the print master at the same time.

Frequently asked questions

Most B2B catalogues work well with a planned annual or twice-yearly edition, plus a controlled process for urgent corrections to the PDF in between.

Engineering or product management should approve technical values, marketing approves wording and layout, and sales confirms that products and variants are still offered. Each sign-off should be recorded.

Replace the PDF at the same web address so old links get the current edition, and keep an archive of previous editions internally for reference and disputes.

Put the edition date on the cover and in the file name, send a short notice with each new edition, and link to the website copy instead of attaching files.

Updating a catalogue?

We build catalogues designed to be updated.

Corpfolio designs catalogue systems with reusable templates and a clear revision path, so each new edition is faster than the last. See our product catalogue design service.