FP-003
Most ecommerce businesses eventually invest considerable effort improving their catalogue. Product descriptions are rewritten. Specifications are corrected. Categories are reorganised. Supplier information is cleaned up. Missing attributes are added. Thousands of product pages are brought up to a consistent standard.
Eventually the project reaches its conclusion.
The remaining issues are resolved.
The final products are reviewed.
The catalogue is considered finished.
For a while, it genuinely feels that way.
Then another supplier sends revised product information. New products arrive. Existing products are discontinued. Manufacturers release updated specifications.
Customers begin asking questions the catalogue cannot yet answer, while buying guides and comparison pages gradually fall behind the products they were written to support.
Nothing has gone wrong.
The catalogue has simply continued changing.
This publication explores why every finished catalogue inevitably becomes unfinished, and why maintaining catalogue quality requires continuous stewardship rather than the pursuit of completion.
Most organisations approach catalogue improvement as a project. The objective is clear: improve the catalogue, resolve the outstanding issues and eventually complete the work.
Experience suggests something rather different.
No matter how successful the project, the catalogue quietly begins changing again almost immediately afterwards. New products arrive, existing ranges evolve, suppliers revise information and customers begin asking questions the catalogue was never previously expected to answer. At the same time, search technologies and AI systems continue changing how product information is discovered, interpreted and compared.
The catalogue that met yesterday’s standard slowly becomes different from the catalogue that must meet today’s.
The challenge is not that catalogue projects fail.
The challenge is that the standard itself never stands still.
Catalogue Optimisation is therefore not the practice of finishing a catalogue. It is the continuous stewardship of a strategic information asset whose quality must evolve alongside the business, its customers and the technologies that depend upon it.
This publication explores why every finished catalogue inevitably becomes unfinished.
Every catalogue improvement project eventually reaches the same moment. The final products are reviewed. Outstanding issues are closed. The remaining corrections are completed. Afterwards, a report is produced and the project is declared finished.
But what happens the next time a supplier changes its specifications? What happens when a product is replaced, customers expect new information or search engines begin interpreting products differently?
If the catalogue keeps changing, can it ever truly be finished?
That question changes the way catalogue quality must be understood.
Open the catalogue immediately after a major improvement project.
The descriptions are consistent. Specifications follow the same structure. Product attributes are complete, categories feel organised and navigation behaves exactly as intended. The catalogue reflects the standard the team worked so hard to achieve.
Now leave it untouched for a few weeks.
A supplier revises several product specifications. A manufacturer introduces a replacement model while quietly discontinuing another. New accessories require publishing, and product relationships that were complete only weeks earlier suddenly need updating.
None of those changes appear dramatic on their own, yet the catalogue no longer reflects the same moment in time.
Nothing broke. Nothing failed. The project ended.
Completion simply expired.
Ask a catalogue team a deceptively simple question.
Which product pages no longer meet today’s standard?
Most teams struggle to answer.
Not because they don’t care. Because they cannot see it.
Some pages were written only recently and still reflect the latest layout parameters. Others still contain raw supplier descriptions written years earlier. The catalogue rarely becomes outdated all at once. Instead, different parts of the data asset begin ageing at different speeds.
The catalogue rarely becomes
outdated all at once.
Instead, different parts begin
ageing at different speeds.
Without clear visibility, yesterday’s improvements quietly become today’s inconsistencies.
Products, suppliers and customer expectations continue evolving whether or not another catalogue project has been scheduled.
One product gains a revised specification. Another needs an updated compatibility statement. A new product range introduces attributes that older pages have never recorded.
Customers expect the catalogue to reflect what the business now knows. Search engines and AI systems increasingly depend upon consistent, accurate information to understand products.
The business knows more today.
The catalogue should know more too.
Ask almost any project manager how they know a project has finished.
They’ll usually point to a completed checklist.
The agreed work has been delivered, the outstanding issues have been resolved and the original objectives have been achieved.
Completion is both measurable and expected.
A building is finished when construction ends. A software feature is finished when it has been developed, tested and released. A warehouse is finished when the last wall is built.
Completion makes sense because the objective remains relatively stable. Once the work has been completed, the finished result can be maintained without fundamentally changing what it is.
Catalogues appear to fit the same pattern.
Product descriptions are rewritten. Categories are reorganised. Specifications are standardised. Supplier information is corrected. Missing attributes are added. Eventually the catalogue reaches an agreed standard and the project concludes.
It feels finished.
Yet the catalogue behaves differently from almost every other business asset.
The moment the project ends, the catalogue continues changing.
The catalogue continues absorbing change. New products introduce information it has never contained before. Existing products evolve as manufacturers revise specifications and replacement models appear. Customer expectations mature, while search technologies and AI systems continually raise expectations for structured product information.
None of these changes are unusual.
They are simply the normal behaviour of a growing business.
Perhaps that is where our thinking has been wrong.
Perhaps the objective was never to finish the catalogue.
Perhaps the objective was to ensure the catalogue continues meeting today’s standard, knowing that tomorrow’s standard will inevitably be different.
The project finished.
The catalogue didn’t.
Perhaps the problem has never been that catalogues become unfinished. Perhaps the problem is that we have been expecting the wrong outcome.
Projects naturally seek completion. They are judged by whether the agreed work has been delivered, the outstanding issues resolved and the original objectives achieved. Once the work is complete, the project comes to an end.
A catalogue behaves differently. Every catalogue improvement project produces a catalogue that accurately reflects one particular moment in time. It captures the products, supplier information, customer understanding and quality standards that existed when the work was completed. That achievement is real. But it is also temporary.
The moment the project ends, the catalogue continues changing. The catalogue quietly accumulates change. New products introduce information that did not previously exist, existing products evolve and businesses continually learn more about the products they sell. Customers ask new questions before making purchasing decisions, while search technologies and AI systems steadily redefine what well-structured product information looks like.
The project finished. The catalogue didn’t.
Every finished catalogue is simply a snapshot of the catalogue at one moment in its life. As the catalogue continues evolving, that snapshot gradually becomes less representative of today’s reality.
The objective of Catalogue Optimisation is not to preserve yesterday’s snapshot. It is to ensure the catalogue continues reflecting today’s reality while preparing for tomorrow’s.
A catalogue is never finished because the standard it must satisfy never stands still.
Continuous stewardship is therefore not something organisations choose after the project has been completed. It is the natural responsibility of managing a strategic information asset whose value depends upon continuously keeping pace with change.
Once that becomes clear, many familiar frustrations begin making sense. Teams stop wondering why the catalogue never seems to stay finished. Instead, they begin recognising that the catalogue was never supposed to remain finished.
Perhaps the catalogue did not become unfinished because the project failed. Perhaps it became unfinished because we expected a living information asset to behave like a completed project. The business continued learning while the catalogue gradually stopped reflecting everything the business now knew.
As new products were introduced, customer expectations evolved and the business accumulated new knowledge, the catalogue was expected to reflect that new reality. The standard quietly moved forward while parts of the catalogue remained exactly as they had been when the project ended.
The catalogue was never being measured against yesterday’s achievement. It was always being measured against today’s reality. Seen from that perspective, organisations begin asking different questions.
“When will the catalogue finally be finished?”
“What has changed since we last looked?”
“Which parts of the catalogue no longer meet today’s standard?”
“Where has the catalogue quietly fallen behind?”
Those questions reveal a different way of thinking. They no longer assume the catalogue has an end. They assume the catalogue continues evolving.
Those are not project questions. They are stewardship questions. And stewardship has no finish line.
Catalogues are never finished because the standard they are expected to meet never stands still. Every catalogue improvement project captures the catalogue at one particular moment in time.
From that moment onwards, the business continues evolving. Products change, customer understanding deepens and technology continually reshapes what good catalogue quality looks like.
The catalogue continues moving while the completed project remains exactly where it finished. Every finished catalogue therefore begins drifting away from the moment it was completed.
Catalogue Optimisation is not the practice of preserving yesterday’s catalogue. It is the practice of ensuring the catalogue continues reflecting today’s reality while remaining ready for tomorrow’s.
The catalogue is a living information system. It faces a steady stream of updates from suppliers, shifts in customer search habits, and new requirements from AI engines.
Treating catalogue optimization as a one-time project leaves the data exposed to constant, quiet decay.
Maintaining its value requires continuous system stewardship.
“A catalogue
is never finished
because
the standard
it must satisfy
never stands still.”
If every finished catalogue inevitably becomes unfinished, how can organisations recognise the earliest signs that catalogue quality is beginning to drift before customers, search engines and AI systems begin noticing?
That is the question explored in FP-004 Published Doesn’t Mean Sales-Ready.