AP-021
An agency can leave a client with a genuinely better catalogue.
Comparable products follow a clearer structure. Important attributes are handled consistently. Product information has been corrected. Shoppers now have more of the information they need to understand and choose.
Then ordinary business resumes.
New products arrive. Suppliers change specifications. Shopper enquiries reveal questions that keep recurring. Someone needs to introduce information that the existing catalogue never had to accommodate.
None of this means the earlier catalogue improvement failed.
Even a good catalogue has to change as new products, information and requirements arise.
The difficulty appears when those changes create situations the established catalogue approach does not already resolve.
Someone has to decide whether a new supplier specification belongs in an existing attribute or requires another one. A recurring shopper question may justify adding information across a product group. A new product may genuinely need to be handled differently from the products around it.
The individual decision can be perfectly reasonable.
But once decisions like these accumulate, the resulting catalogue can reflect a combination of local decisions that nobody intended as an overall approach.
Consider a catalogue where comparable products already follow an established specification structure.
A supplier introduces a new product and includes an important specification the catalogue has never represented before.
Someone has to decide what to do with it.
Perhaps the specification belongs naturally within an existing attribute. Perhaps it requires a new one. Perhaps it matters only to this particular product type and should remain limited to that part of the catalogue.
Any of those answers could be correct.
The existing approach may not provide a complete answer for a situation that has not arisen before.
A similar problem appears when shoppers repeatedly ask the same question about a particular group of products.
The existing product information may still be accurate. It simply leaves something unexplained that the business now knows shoppers need to understand.
Adding that information is a sensible response.
But again, another decision follows.
Should the new information appear only on the products generating enquiries? Should it become an expectation for every comparable product? Does it belong in the description, an attribute or another part of the catalogue?
These are not examples of people ignoring an established catalogue approach.
They are situations where the existing approach does not provide a complete answer.
Someone must make a judgement.
Once that judgement appears in the catalogue, it can become an example for the next person facing something similar.
As decisions like this accumulate, the catalogue can begin to contain several plausible precedents for similar situations.
The same thing can happen with terminology, compatibility, product relationships, descriptions or category treatment.
Each individual choice may have made sense when it was made.
The problem only becomes visible later, when another person has to decide which precedent should govern the next product.
At that point, the catalogue contains more than product information.
It also contains the consequences of earlier decisions.
If those decisions were made independently, the next person may have to choose between several plausible answers.
The issue is therefore not simply whether each change can be justified on its own.
It is whether individual catalogue decisions continue to fit a dependable approach as they accumulate.
A clear catalogue standard gives the team a dependable basis for routine decisions.
Where the next product fits an established situation, the team should be able to follow the existing structure, terminology and information requirements without reconsidering them every time.
That is exactly what a dependable standard should make possible.
But a standard records the current conventions and information requirements.
Future products, supplier changes and shopper requirements will not all be covered by the existing standard.
A manufacturer may introduce a specification that did not previously matter.
A new product type may not fit the existing attribute structure cleanly.
A pattern of shopper enquiries may show that technically correct information is no longer sufficient for confident choice.
In these situations, insisting that the existing standard must always be followed can create a different problem.
The catalogue may remain consistent with an old decision while becoming less appropriate to the current reality.
Good catalogue practice therefore cannot mean preserving every established convention indefinitely.
Sometimes the correct response is to retain the standard.
Sometimes a genuine exception is required.
Sometimes the new situation shows that the standard itself should change.
Those are different decisions, and most catalogue changes do not require reopening them.
Most routine catalogue changes already have an established basis.
If an established attribute clearly applies to the next comparable product, use it.
If the existing category logic clearly applies, follow it.
If a supplier update simply replaces one confirmed specification value with another, make the change.
The situation is different when the established answer stops being sufficient.
A new attribute affects more than the current product if comparable products should now carry the same information.
A new exception matters beyond one page if the same question could arise when later products are added.
A change to terminology can affect existing products if the new term is intended to replace the old convention.
Those decisions determine more than what happens to the product currently being edited.
They influence what should happen next.
At that point, routine maintenance is no longer enough.
A standard tells people what to do when the answer is already known.
Good catalogue governance includes a dependable basis for making catalogue decisions, particularly when the answer is not already known.
The standard colour names might be Red, Blue and Black.
A supplier then introduces Ocean Mist.
The standard covers the existing colours. Governance is needed to decide whether Ocean Mist should map to one of them or become a new colour.
The same applies to size.
The established sizes might be S, M and L.
A new supplier uses 1, 2 and 3.
The standard covers the established sizes. Governance is needed to decide how 1, 2 and 3 should be handled and whether that decision changes the existing approach.
Who decides whether a new attribute becomes part of the established structure?
What happens when a supplier source conflicts with information already confirmed elsewhere?
When should an exception remain limited to one product group, and when should it alter the wider catalogue approach?
Who can decide that a convention which once made sense no longer does?
Good catalogue governance does not have to be complicated.
It does need a dependable basis for resolving these questions.
What matters is that important decisions are not left to whichever person happens to encounter the next unusual product.
Maintaining catalogue quality therefore requires more than making individual updates correctly.
It requires a dependable way to govern the decisions through which the catalogue continues to change.
Treating every catalogue edit as a decision requiring formal approval would make governance unnecessarily burdensome.
Most routine changes should remain routine.
Where an established standard already gives a clear answer, the team should be able to act on it.
With good governance, people understand which decisions have already been made and which situations genuinely require another judgement.
The need becomes greater when the team encounters an unresolved case, a meaningful exception or a change that could establish a new precedent.
The governance arrangement may be relatively simple. The client’s ecommerce lead may own decisions affecting the standard. The agency may identify issues requiring a wider decision. Routine changes may be clearly delegated while structural changes require review. Significant exceptions may need to be recorded so the next person understands why the normal convention was not followed.
Where one knowledgeable person manages a small catalogue, very little formality may be needed.
Where several internal teams, agencies, suppliers or integrations change a larger catalogue, responsibilities and decision rules may need to be much more explicit.
The exact arrangement can differ.
The objective is not more control for its own sake.
It is enough control to prevent important catalogue decisions from becoming a series of unrelated local answers.
Most catalogue changes an agency handles can follow an established standard.
But sometimes a routine change reaches a point where the existing standard does not sufficiently resolve what should happen.
At that point, the agency should recognise that the question is no longer simply how to apply the standard. Someone needs to decide whether the existing approach should still be followed, whether the situation requires an exception or whether the standard itself should change.
That does not mean every unresolved situation requires a formal governance programme, nor does the agency necessarily need to make the decision.
The client’s team, the agency, another provider or a combination of them may hold responsibility for different catalogue decisions.
What matters is that responsibility for the decision is clear and that there is a dependable basis for making it rather than allowing the next local answer to become an unintended precedent.
For agency practice, the important distinction is therefore between a catalogue change that can follow an established decision and one that requires a new decision.
When catalogue activity crosses that boundary, the agency should recognise the governance question rather than treat it as routine maintenance.