Most manufacturer catalogues are laid out the way the factory thinks about its own product families. Buyers arrive with an application and a deadline, and the mismatch is why the catalogue never gets past the first meeting.

Open almost any industrial catalogue and the structure is the same: Series 100, Series 200, Series 400, each with its own dimension table. That organisation reflects how the products were developed and how the plant is scheduled. It reflects nothing about how a buyer arrives.
A buyer arrives with a problem stated in application terms — a pump seal that keeps failing on a hot caustic line, a gearbox for a conveyor at a specified duty, a fastener that has to survive a coastal atmosphere. He does not know that you call it Series 200, and he has no way of finding out except by reading all four sections and hoping.
Reorganising around the application does not mean throwing away the series structure. It means putting an entry point in front of it: , and routes the reader into the right family. The engineering content underneath stays exactly as it is.
The cheapest version of this is a two-page cross-reference at the front: applications down one side, families and part number prefixes across the top. It takes an afternoon with your applications engineer and it saves every reader the work of guessing.
There is a specific moment you are designing for: an engineer is writing a specification or filling in a comparison sheet, and he either has your numbers to hand or he does not. If he does not, he uses the competitor's numbers, because they are on his screen. Everything else in the catalogue is secondary to making that moment easy.
The data he needs is unglamorous and non-negotiable. Give it in a table, in the same units your buyers use, and do not scatter it across a paragraph of prose.
Two things matter as much as the data itself. Give every variant a part number that can be pasted into an enquiry, and state clearly what is standard stock and what is made to order — a lead time surprise discovered after the specification is written is how a supplier gets dropped.
Engineers are used to qualifiers and are reassured by the right ones. A temperature limit stated as continuous versus intermittent, a load rating tied to a named duty class, a corrosion claim tied to a specific medium and concentration — these read as competence. They tell the reader that somebody who understood the product wrote the page.
The wrong qualifier does the opposite. Phrases like up to, suitable for most applications, designed for demanding environments and typically achieves signal that a number exists but you are unwilling to commit to it. The reader assumes the real figure is worse than the one you would not print.
The rule is simple. Qualify the conditions under which a number holds, and never qualify the number itself. If a figure genuinely varies by variant or by application, publish the range with the conditions at each end rather than the flattering endpoint alone.
Almost no industrial purchase is decided by the person who first found you. Your contact forwards something to a design engineer, a quality manager or a purchase head, usually with a one-line note and no context. That forwarded page is doing the selling in a room you are not in.
Design for it deliberately. One product family per page: what it is, the applications it is used for, the full specification table, the part numbers, the standards, the drawing, and a named contact with a direct number. It has to make sense to a reader who has never heard of you and will not scroll back to find out who you are.
This is also the page that decides whether you make the approved vendor list. A page that answers the quality manager's questions without a follow-up call is worth more than a brochure that requires one, because the follow-up call frequently does not happen. Put the revision date and the part number range in the footer so the page identifies itself wherever it ends up.
Print, PDF and web page have different jobs and the same content. The mistake is to write three times, which guarantees three versions of a tolerance figure and a slow argument about which is correct. Write the specification once and hold it in one place — a spreadsheet is enough for most manufacturers — then set it into each format.
The print catalogue is for the stand, the meeting and the shelf in the buyer's office. Keep it structural: the application entry points, the family overviews, the range tables. Do not put anything in print that changes more than once a year, and put the web address for the current data on every page.
The PDF datasheet is the working document. One family per file, named so it is findable on a desktop months later — a file called datasheet_final_v3.pdf will be deleted. The web page is where the buyer arrives from a search, so the specification table has to be real text on the page rather than an image of a table, and the datasheet link has to be visible without scrolling past the company history.
Gating a brochure behind a form looks like lead generation and usually functions as a filter against your best prospects. The engineer comparing three suppliers under time pressure will download the two datasheets that are open and specify from those. The form collects the people with time to fill in forms, which is rarely the same group as the people writing specifications. Students, competitors and consultants fill in forms readily; the buyer with a deadline does not.
There is also a practical failure. Specification work is often done at odd hours and against a deadline, and a form that demands a company email and a phone number before releasing a dimension table simply sends that reader to a competitor or a distributor listing.
If you need enquiry capture, put it where it belongs: an enquiry form on the same page, a clearly stated request-a-sample route, and a named contact rather than a general address. Open technical data and an easy way to make contact will out-produce a gate, and the enquiries that arrive will already be specified.
Cut the chairman's message, the aerial photograph of the plant and the paragraph about your commitment to quality. None of it is read, and all of it pushes the specification table further down the page. Certifications belong in the catalogue as a line item with the certificate number, not as a page of logos.
Cut adjectives that no reader can verify — robust, world-class, cutting-edge, best-in-class. They occupy the space where an operating limit should be, and an engineer reads them as an absence of data. If a product genuinely outperforms the alternatives, say on which parameter and by how much, using your own test conditions. A single measured comparison, with the method stated, does more than a page of superlatives.
Finally, cut anything you cannot keep current. A catalogue with a discontinued variant still in the table costs you more credibility than a thinner catalogue would have. Decide what you will maintain, maintain it properly, and put a revision date on every page so that a reader can tell at a glance whether what he is holding is still true.
Key takeaways
Keep the product families as the underlying structure, because that is how your engineering and production data is held, but add an application-based entry point in front of them. Buyers arrive knowing their duty, medium and operating conditions, not your series numbers. The entry section routes them into the correct family in one step.
Dimensions with a drawing, the tolerances actually held in production, material grades under their standard designation, the standards and certifications the product is built to, and full operating limits including pressure, temperature and medium compatibility. Add part numbers that can be pasted into an enquiry, and state what is stocked versus made to order.
For technical data, no. An engineer comparing suppliers against a deadline will specify from the datasheets that open immediately. Publish the datasheet openly and put an enquiry form, a sample request route and a named contact on the same page — the enquiries that come through will already be specified.
Hold the specification data in one source, such as a single spreadsheet, and set it into each format rather than writing each version separately. Keep material that changes frequently out of print entirely, and put a revision date on every page so a reader can see whether the copy in front of them is current.