Digital Architecture

The web catalogue is not a product list. It is a decision architecture.

An industrial catalogue that mirrors the manufacturer's internal logic shuts out buyers searching by application, material or regulatory requirement. Every reference may be there and still remain unfindable.

Publicado
Lectura 8 min

Introduction

An industrial manufacturer can have two hundred product references perfectly documented in its internal system and a website where none of them appears in a way that allows a technical buyer to find it without already knowing what to look for.

An industrial company's web catalogue should not be built as an ERP dump in HTML format. And yet that is exactly what happens on a disproportionate number of websites in the sector. Product families carry the name given by the production department. Categories follow the warehouse coding. The hierarchy mirrors the manufacturer's org chart, not the research journey of someone evaluating a supplier.

From inside the company, that structure makes sense. From outside, it solves nothing.

In March 2026 Gartner published a survey of 646 B2B buyers in which 67% stated they preferred a purchasing process without sales rep involvement. 45% had used artificial intelligence tools during their most recent purchasing process. The buyer no longer waits for someone to explain the catalogue. They evaluate it alone, on the website, using their own criteria. And if the structure does not answer, they move on to the next supplier without ever opening a contact form.

The manufacturer's internal classification is not the buyer's classification

There is a pattern that repeats across industrial websites of every size.

The company manufactures technical components. Internally it groups them by production line, process type or warehouse coding. A fastener manufacturer classifies by head type and thread size. A cable protection manufacturer, by product series. An electrical component manufacturer, by internal catalogue family. That classification is transferred to the website as-is, as if the visitor were another factory employee.

The problem is that the technical buyer does not search that way.

An engineer at a food processing plant is looking for A4 stainless steel fixings suitable for high-pressure washdown environments compliant with their sector's hygiene directives. They do not care that internally the reference belongs to "series 300". They care whether it solves their application.

A purchasing manager in the railway sector needs cable protection systems with EN 45545-2 classification for rolling stock. They enter searching for a specific regulatory reference, not an internal family name.

A maintenance technician needs a replacement compatible with existing equipment. Their search logic may be dimensional, may be by material, may be by compatibility with a specific chemical or thermal environment. It has nothing to do with production logic.

Each profile enters with its own framework. If the website only offers one entry point — the manufacturer's — all the other frameworks are cut off before they even begin.

What a poorly structured catalogue costs the company

The problems of a poorly structured catalogue are not cosmetic. They are architectural problems that directly affect three website functions: search ranking, cross-selling and conversion.

Google indexes pages, not catalogues. If two hundred references are compressed into a single listing page, that page will compete for a handful of generic terms and will never rank for specific technical searches. A technical buyer does not type "industrial components" into Google. They type "M8 countersunk A4-80 stainless steel bolt for marine environment" or "IP68 cable gland for 12mm cable with ATEX zone 1 certification". If the website has no pages that answer those searches, qualified traffic never arrives.

A flat catalogue shows products as isolated items. The visitor arrives, finds what they are looking for — if they are lucky — and leaves. Or does not find it and leaves just the same. They do not discover that the supplier has more products related to their application. They do not understand that the company covers a complete ecosystem of needs. Each visit closes without generating the commercial connection that a well-thought-out architecture would have produced.

A catalogue that offers no journey generates no contact. The visitor arrives, looks at a shallow datasheet, does not find enough context to advance their evaluation, and closes the tab. McKinsey has been documenting through its B2B Pulse Survey that 54% of B2B buyers would switch suppliers if the digital experience failed to meet their expectations. The buyer does not just want to find the product: they want to be able to advance their technical evaluation without having to call anyone.

And all of this has a cost that is rarely measured but is absolutely real: every search that goes uncaptured, every relationship between products that is not shown, every evaluation that stalls for lack of information, is a commercial opportunity that silently shifts to a competitor who has already solved those problems.

The technical buyer does not have a single search logic

One of the most common mistakes when designing catalogue architecture is assuming there is a single valid navigation path. There is not.

The product engineer may enter searching by material. The purchasing manager may enter by sector. The maintenance technician may enter by geometry or part reference. The quality manager may enter by certification. The client's commercial director may enter looking for signals that the supplier understands their market.

Each of these profiles has a different search framework, a different urgency and a different way of evaluating whether a supplier deserves attention. When the website only offers one path — the manufacturer's — all the other frameworks go unanswered.

Companies that solve this well do not do so by chance or by installing a plugin. They do it because someone has done prior analytical work: understanding who searches, how they search, what they need to see to move forward and what relationships exist between the company's products that the buyer will not discover on their own.

That work is not web design. It is business analysis applied to digital architecture. And it is what separates a catalogue that informs from one that converts.

Artificial intelligence amplifies the problem

Everything above is compounded by a factor that carries increasing weight: artificial intelligence.

Forrester noted in its 2026 predictions that 30% of B2B buyers already considered generative AI tools a relevant interaction during the final purchasing decision phase. And it documented in 2025 that 61% of procurement leaders stated that their organisation already used or planned to use a private generative AI engine to support purchasing processes.

When an engineer asks ChatGPT, Gemini or any AI engine which European supplier manufactures a specific component with a particular certification for a regulated application, the AI needs structured, accessible content to give a concrete answer. If the manufacturer's website does not have that information organised in a way a system can interpret, the AI will not find it. And if it does not find it, it will not recommend it.

A flat catalogue without semantic hierarchy or structured data is not citable material — neither by Google nor by AI engines. A well-architected catalogue is. And that difference, which already matters today, will be decisive in the coming years.

Companies that have already resolved their catalogue architecture are positioning themselves now to be the sources AI cites tomorrow. Those that have not are ceding that ground without knowing it.

The catalogue is the most underutilised digital asset of the industrial company

An industrial manufacturer almost always has more product capacity than its website reveals. References that do not appear. Variants that are not mentioned. Applications that are not documented. Sectors that are served but have no presence in the site structure.

That gap between productive reality and digital reality has a direct cost. Every reference absent from the website is a search that goes uncaptured. Every sector with no digital presence is a buyer who cannot find the entrance. Every datasheet without technical depth is an evaluation that stalls before generating contact.

The website catalogue should not be a passive mirror of the ERP. It should be the company's most powerful commercial asset in the digital environment. But for it to work as such, it is not enough to add more references to a flat listing. The architecture needs to be rethought from a perspective that combines deep knowledge of the company with an understanding of how the technical buyer searches and researches in each target sector.

That work begins before design and before development. It begins with an analysis that most web projects skip.

Conclusion

An industrial company's web catalogue is not a section where products are listed. It is a decision architecture that must respond to multiple search logics, integrate the sector's regulatory context and offer sufficient technical depth for the buyer to advance their evaluation without needing to call.

When the catalogue structure mirrors the company's internal logic instead of the buyer's research logic, the result is predictable: products that exist but are not found, sectors that are served but not shown, and commercial opportunities that vanish before the first contact.

The difference between a catalogue that takes up space and one that generates business is not the number of references. It is the architecture behind it.

If your website catalogue does not reflect the company's real capacity or respond to the way the technical buyer researches, I can analyse the current structure and propose an architecture that turns your technical content into a real commercial asset.

Request catalogue architecture analysis

Adrián Morín

Developer & Visual Architecture

Responsible for technical development, interface design and dependency-free web architecture.