FP-002
Walk into almost any ecommerce business and ask who looks after the catalogue. The answer is rarely a single person.
Everyone improves part of the catalogue. Very few people improve the catalogue as a whole.
For many years, this has simply been accepted as the way ecommerce operates. Increasingly, that explanation no longer feels complete. As catalogues become larger, richer and more important to both customers and AI systems, these seemingly independent activities increasingly modify the same underlying information structure. Improving one area increasingly affects the integrity of the whole catalogue.
This publication explores why that change is occurring, and why maintaining the structural integrity of the catalogue while continuously increasing its value as a strategic information asset for customers, businesses and AI systems is giving rise to Catalogue Optimisation as a distinct professional discipline.
Most organisations view catalogue work as a collection of specialist activities. Content writing, SEO, merchandising, supplier management, product information, taxonomy, buying guides and navigation all appear to solve different problems.
Experience suggests something more interesting. As catalogues mature, improvements made in one area increasingly depend upon improvements somewhere else. Maintaining catalogue quality becomes less about coordinating individual tasks and more about understanding the catalogue as one connected system.
That system includes not only product content, but also taxonomy, attribute schemas, structured product data and the supporting knowledge customers rely upon before making purchasing decisions. Modern catalogues therefore require continuous stewardship rather than periodic improvement.
This publication explores why those responsibilities are giving rise to a distinct discipline.
Most ecommerce businesses already invest considerable effort improving their catalogue. So why would anyone suggest that Catalogue Optimisation is becoming its own discipline?
Product descriptions have always been written. Categories have always been organised. Specifications have always required updating, supplier information has always needed checking, and buying guides have always been published.
Nothing about these activities is new.
Yet many experienced catalogue teams recognise something changing.
When did
catalogues
become more than
a collection of
product pages?
Open a buying guide explaining how customers should choose the right laptop. It recommends comparing processor generation, memory, storage, screen resolution, and battery life.
Then open the product pages it recommends. Some products list every specification. Others mention only a few. Some hide important information inside paragraphs. Others don’t mention it at all.
The buying guide answers one set of questions. The product pages answer another. Customer service fills in the gaps.
Three different parts of the business quietly compensate for one another. Customers never see those boundaries; they simply experience one catalogue. They experience one information system, regardless of how many teams contribute to it.
Improving one part of the catalogue rarely stays isolated.
A team standardises product attributes. The category filters immediately become more useful. Now older products are missing those attributes.
The merchandising team reorganises categories. Navigation improves. Now similar products reveal completely different specification layouts.
Marketing publishes comparison articles explaining which features customers should evaluate before purchasing. Customers arrive at product pages looking for those features. Many cannot find them.
Every genuine improvement reveals another opportunity somewhere else. The work never quite finishes. Not because people are doing poor work, but because every improvement uncovers another part of the catalogue connected to it. Improvements that appear local often expose dependencies within the catalogue’s data structure, taxonomy and product information architecture.
Open a single product category and compare neighbouring products.
One product explains compatibility in detail. The next assumes the customer already understands it. One lists dimensions in a structured table. Another hides them inside a paragraph. A third omits them altogether.
Some products can be filtered by important attributes. Others disappear from filtered results because those same attributes were never recorded.
None of these differences were created deliberately. Each reflects a sensible decision made at a different time. Viewed individually, they appear insignificant. Viewed together, they reveal something more interesting.
The catalogue no longer behaves like a collection of individual product pages. It behaves like one connected system. Organisations divide the work. The catalogue never does. Every product page, attribute, category and buying guide ultimately contributes to the same underlying catalogue structure.
Most organisations explain catalogue work by describing the people responsible for it. Marketing creates content. Developers manage product data. Merchandisers organise categories. SEO improves discoverability. Operations coordinate suppliers. Customer service answers product questions.
It is a sensible way to divide responsibility. It may not be the best way to understand what is actually happening.
Consider how customers make purchasing decisions. They search. They browse categories. They compare products. They read buying guides. They return to product pages. They compare specifications. Then they decide.
From the customer’s perspective, these are not separate experiences. They form one purchasing journey.
Behind the scenes, the buying guide depends upon the same product information that powers specifications, attributes, filters and comparisons. Editorial content prepares customers for the catalogue. The catalogue completes the decision. Behind every customer interaction sits the same product information architecture, whose quality determines both customer understanding and machine interpretation.
Every part depends upon the others. Changes to taxonomy, attribute schemas and structured product data often propagate throughout the catalogue, increasing both capability and maintenance responsibility.
Perhaps we have been dividing the work in the wrong way. Instead of asking, “Who owns each activity?” perhaps we should ask, “What are all these activities actually trying to optimise?”
Writing product descriptions, maintaining supplier information, organising categories, standardising attributes, publishing buying guides, improving search visibility and answering customer questions all appear to be different kinds of work. The catalogue experiences them as one. So do customers.
The catalogue therefore behaves as a single information system rather than a collection of independent optimisation activities.
Every improvement quietly depends upon another. Every optimisation ultimately changes the same underlying asset: the catalogue’s information structure. The boundaries exist inside the organisation. They do not exist inside the catalogue.
Over time, these separate activities begin sharing the same responsibility: maintaining a catalogue that remains structurally consistent while continuously becoming more useful to customers, businesses and AI systems.
In other words, the catalogue is no longer simply a collection of product pages. It has become a strategic information asset. Like any strategic information asset, a catalogue requires continuous stewardship. That stewardship depends upon shared principles, shared methods and continuous improvement. Eventually, it becomes recognised as a discipline.
Perhaps the most surprising discovery is that very little of this work is actually new. Businesses have always written descriptions, organised categories, corrected supplier information, published buying guides and answered customer questions. What has changed is our understanding of how these activities relate to one another.
Customers never experienced separate departments. They always experienced one catalogue. Increasingly, they expect that catalogue to become easier to understand as the business grows, not harder. AI systems interpret it in much the same way—as a connected body of structured information rather than isolated pages.
Once that becomes clear, many familiar frustrations begin making sense. Teams stop asking why improvements never seem to stay finished. They begin asking how the catalogue can continuously increase the integrity, usefulness and long-term value of one of the organisation’s most important information assets.
Catalogue Optimisation is not emerging because ecommerce has accumulated more catalogue work.
It is emerging because modern catalogues have become strategic information assets that must remain structurally consistent while continuously becoming more valuable to customers, businesses and AI systems.
Strategic information assets require continuous stewardship supported by shared principles, shared methods and continuous improvement.
That is why Catalogue Optimisation is emerging as a distinct discipline.
Catalogues have become
strategic information assets
that require continuous stewardship.
If Catalogue Optimisation is emerging because catalogues behave as connected systems rather than collections of independent activities, how should organisations build a system capable of maintaining catalogue quality while products, suppliers, customer expectations and AI technologies continue changing?
That is the question explored in FP-003 A Catalogue Is Never Finished.