AP-001
Catalogue work can be easy to underestimate when it starts as an ordinary maintenance request.
A client asks for a product range to be updated. Some attributes need correcting and several older products follow a different specification format.
On the surface, it is routine ecommerce maintenance. But the agency may first need to work out which attributes are correct, why similar products follow different conventions and what else could be affected by the change.
The requested update may be straightforward. Understanding the catalogue well enough to make it correctly may not be.
That matters because, for agencies working through maintenance requests, these problems can arrive one task at a time. When each request is treated simply as another maintenance job, it is easy to underestimate how much catalogue work is actually involved.
For agencies maintaining ecommerce stores, catalogue requests can appear unremarkable.
Add these products.
Update this supplier information.
Correct these attributes.
The client is asking for a visible change, and the agency quite reasonably begins by considering the work required to make it.
In a coherent catalogue, the relationship between request and effort can be straightforward. If an attribute is wrong, correct it. If a new product needs adding, follow the established product structure. If supplier information changes, update the affected products.
The difficulty appears when the agency can no longer assume that one clear structure or convention exists.
Before changing an attribute, someone may need to determine which version is supposed to be used. Before adding a product, the agency may need to decide which existing product-page convention should be followed. Before updating supplier information, it may first need to establish whether older products in the same range should also change.
The client may still have asked for something relatively small, but the agency first has to resolve questions about the catalogue around the requested change.
Over time, a catalogue can carry the history of decisions made as the business changes.
Suppliers revise their information. New product ranges introduce attributes that older ranges never required. Categories expand beyond the purpose for which they were originally created.
None of this necessarily reflects poor management. Individual decisions made along the way can be sensible responses to the needs of the moment.
Their accumulated effect becomes visible later.
Two products that should be comparable may describe the same specification differently. A filter may work for recently added products while excluding older ones. One product range may follow current supplier terminology while another still uses an earlier convention.
The agency making the current change therefore has to work through earlier catalogue decisions before it can determine what should now be considered correct.
This is where a maintenance request begins to contain work that the request itself does not describe.
Changing a value may be simple. Establishing which value should be used may require investigation.
Adding an attribute may be technically straightforward. Determining whether it should replace an existing attribute, coexist with it or be applied more broadly across the catalogue requires a different kind of judgement.
The client sees the requested change. The agency may also need to investigate, reconcile and preserve the catalogue around it.
The underlying condition may not be described directly in the client request. Instead of describing several years of product, supplier and merchandising decisions that have created inconsistencies, the request may simply be:
“Can you fix these products?”
The next request may concern a category. Another may involve supplier information or filtering.
Each request can have a clear beginning and end. The agency investigates it, completes the change and closes the work.
Handled one by one, these requests look like ordinary maintenance. Across repeated requests, however, the agency may notice that the same inconsistencies keep creating additional investigation.
Questions that should have predictable answers require checking. Similar products cannot safely be assumed to follow the same conventions. Changes that appear routine demand more context before anyone can make them confidently.
In a request-driven maintenance relationship, the agency experiences this through individual tasks because that is how the work arrives.
The difficulty, however, may be created by the accumulated condition of the catalogue.
That difference is easy to miss when every occurrence presents itself as another maintenance request.
It is natural to estimate catalogue work from the requested output.
Ten products need updating. A category needs correcting. Several attributes need standardising.
The request gives the agency something tangible to scope.
But the apparent size of the requested change is not always a reliable measure of the work required to make it correctly.
Suppose a client asks for one technical specification to be standardised across ten products.
If all ten products follow the same structure and the correct information is known, the task may genuinely be small.
Now suppose those products were added over several years. The specification appears under two attribute names. Some products use terminology that the supplier has since changed. Others contain the value in a different part of the product page.
The requested output is still ten updated products, but the work now includes establishing which structure and terminology should govern those updates.
The requested change tells the agency what the client wants to happen.
It does not necessarily tell the agency what must be understood, reconciled or decided before that change can happen properly.
The problem is not simply that the work takes longer. It is how that additional work is interpreted.
Two hours may be recorded against fixing ten products. Several more may sit against correcting a category. A developer may spend part of a maintenance task investigating why filtering behaves inconsistently.
The completed change is visible. The investigation, reconciliation and judgement required to make it correctly are much easier to absorb into the task itself.
That does not mean every catalogue update should be treated as a major optimisation exercise. Some changes are genuinely routine, and a well-structured catalogue should make routine work easier.
The distinction becomes important when apparently simple requests repeatedly require the agency to investigate how the catalogue currently works, reconcile competing conventions and decide how consistency should be preserved.
At that point, the recurring difficulty is no longer explained adequately by the individual request.
It is being created by inconsistencies and earlier decisions elsewhere in the catalogue.
If that distinction is missed, catalogue-level professional work can continue to be interpreted simply as additional effort attached to a succession of maintenance tasks.
When this happens repeatedly, the maintenance request stops being a reliable description of the work involved.
The requested change may still be small, but the agency can increasingly be required to resolve a wider catalogue condition around it.
The useful distinction is therefore between the change itself and the catalogue work required around the change.
In a coherent catalogue, those may be almost the same thing. As variation and inconsistency accumulate, more of the agency’s effort goes into understanding and reconciling the catalogue before the requested change can be made.
That is how the significance of catalogue-level work can be underestimated even while the agency continues to experience it as routine maintenance.
The client presents a task. The difficulty of completing it may be determined by something much larger than that task.
Agencies should not judge catalogue work only by the apparent size of a client’s request.
A small update may genuinely be a small update.
But when routine requests repeatedly require investigation, reconciliation and consistency management, the agency is dealing with a condition of the catalogue that is making those changes harder to perform.
That recurring effort is worth interpreting differently.
It should not be understood simply as more time attached to another maintenance task. It is evidence about the catalogue being maintained: its accumulated decisions, inconsistencies and the amount of professional judgement now required to change it safely.
Recognising that distinction does not determine how an agency should package, price or deliver Catalogue Optimisation services.
It establishes the more fundamental judgement that comes first.
When apparently routine catalogue work repeatedly requires the agency to understand and reconcile the catalogue before it can make the requested change, the significance of the work should be assessed at catalogue level, not only at task level.