AP-017
An agency takes on an established ecommerce catalogue and quickly finds things that need changing.
Some attributes are inconsistent. Product descriptions follow several different conventions. Specifications have been recorded differently across similar products. Compatibility information appears in some records but not others.
The required changes are easy to recognise.
Clean up the attributes. Rewrite the descriptions. Standardise the specifications. Rebuild the structure where necessary.
All of that may be exactly right.
But the existing catalogue contains more than the problems the agency has been asked to correct.
It may also contain years of accumulated knowledge about the client’s products.
A compatibility statement may be there because shoppers repeatedly bought the wrong accessory. A particular specification may have been added because shoppers kept asking the same question. A distinction between two similar products may exist because someone inside the client’s business learned that the difference matters when shoppers are choosing.
By the time the agency sees that knowledge, it may look like nothing more than another field in the catalogue.
That creates a professional problem.
If the agency judges product information only by the field or page where it currently appears, it can underestimate what has already accumulated in the client’s catalogue.
Not all product information enters the catalogue in the same way.
Some comes directly from suppliers. Some is researched when a product is first added. Some is rewritten because supplier information does not explain the product clearly enough. Other information appears only after the retailer has spent time selling the product and answering questions about it.
Consider compatibility.
A retailer selling replacement parts may know exactly which models a particular component fits. That information could have come from manufacturer documentation, internal product knowledge, previous shopper enquiries or experience resolving incorrect purchases.
Once recorded in the catalogue, the result might be a short list of compatible models.
The field itself may be simple even when establishing the knowledge behind it was not.
The same is true of specifications that have become important over time.
A retailer may discover that shoppers repeatedly ask about load capacity, internal dimensions or whether a product works under a particular condition.
Eventually that information makes its way into the catalogue.
When the agency later encounters it, that history may be invisible.
The team sees information to copy, standardise or move.
It does not necessarily see the supplier documents that were checked, the shopper questions that exposed the need for the information or the judgement required to decide how it should be expressed.
This does not make every existing field important.
Catalogues also contain obsolete values, duplicated information, outdated terminology and decisions that no longer serve any useful purpose.
But the visible simplicity of a field does not tell the agency what useful knowledge may sit behind it.
That distinction becomes more important once the original task has been completed.
A product specification may originally be added because the product page needs it.
The task is completed once the correct value appears in the right place.
But completing that task does not necessarily exhaust the usefulness of the information.
The same specification might later help shoppers compare similar products.
An attribute initially added to describe a product might later help narrow a category.
Compatibility information originally included to answer a question on the product page might also help connect the product with the right replacement part or accessory.
The same product information can become more useful when it is organised so it can help shoppers in more than one part of the catalogue.
For the agency, the important point is what follows from that principle.
The task that first required the information can finish while the usefulness of the information continues.
This changes how the agency should understand the value of the information it is handling.
If an agency records a product attribute correctly, the immediate deliverable may be one completed field.
But the client’s catalogue may now contain a reliable piece of product knowledge that can be used again when the catalogue develops.
That does not mean every specification needs to become a filter or every attribute needs to appear in a comparison.
Some information may only ever serve one purpose.
Its usefulness cannot always be judged from the task that originally required it.
A field can be complete without the information inside it having reached the end of its value.
This matters when an agency begins changing an established catalogue.
Suppose several related products use inconsistent specification structures.
One product records dimensions as separate values.
Another places them in a single text field.
A third includes part of the same information inside the description.
The inconsistency needs correcting.
A cleaner structure may make the catalogue easier to maintain and the information easier to use.
But the agency has two different decisions to make.
The first concerns the structure.
What should the improved catalogue look like?
The second concerns the information.
What useful knowledge in the current catalogue still needs to survive the change?
Those are not the same decision.
A badly structured compatibility note may still contain a correct relationship between two products.
A duplicated attribute may reveal a distinction that shoppers genuinely need.
A description the agency intends to replace may contain the only recorded answer to a common product question.
The existing implementation can therefore be poor while some of the information inside it remains valuable.
If the agency treats everything inside a poor structure as equally disposable, cleaning the catalogue can remove useful knowledge along with the inconsistency.
Sometimes that knowledge is easy to recover.
A current supplier specification may provide the answer immediately.
In other situations, recreating it may require finding old documentation, asking someone inside the client’s business or rediscovering why the information was recorded in the first place.
Some knowledge may no longer be recoverable with confidence at all.
The professional requirement is therefore not to preserve everything.
It is to distinguish between what is wrong about the current catalogue and what useful information should still be carried forward.
Look across a mature catalogue and the cumulative effect becomes easier to see.
The client’s catalogue may contain knowledge about which products are compatible, which specifications distinguish similar models and which questions shoppers repeatedly need answered.
That knowledge may be distributed across many individual records.
Its sources can include supplier information, the client’s own product expertise and answers developed through recurring shopper enquiries.
Seen field by field, it can look like ordinary catalogue content.
Seen together, it is a body of accumulated product knowledge.
That is why useful product information deserves to be treated as more than material required to finish individual pages.
Its value does not come only from the fact that effort was spent creating it.
Nor does every piece of information automatically become valuable simply because it already exists.
Its importance comes from what reliable product knowledge allows the catalogue and the client’s business to continue doing.
Reliable product knowledge can help the catalogue explain products, preserve useful distinctions between them and help shoppers find and evaluate suitable options.
And because the same knowledge can remain useful as the catalogue changes, its value can continue long after the particular task that first introduced it has finished.
The agency handling an established catalogue is therefore not always starting with raw content.
Part of what it has inherited may already be a reusable client asset.
When an agency takes responsibility for changing an established catalogue, it should not begin from either of two assumptions.
The first is that existing product information must be preserved because the client already has it.
The second is that existing information can be discarded freely because the agency is replacing the structure around it.
Both can lead to poor decisions.
The more useful question is what knowledge the catalogue already contains and which of it still needs to be carried forward.
That judgement matters whenever an agency materially changes existing product information.
Before removing or restructuring product information, the agency may need to understand what it means, what useful purpose it currently serves and whether the proposed change should preserve that usefulness.
The right outcome may be to preserve the information, correct it, standardise it, move it into a structure where it can be used more effectively or deliberately remove it because it no longer serves a useful purpose.
The important change is that the decision becomes deliberate.
An agency is no longer looking only at fields that need cleaning up or pages that need completing.
It is also considering the product knowledge already accumulated in the client’s catalogue and deciding how that knowledge should survive, improve or be retired as the catalogue changes.
That is a different level of responsibility from simply completing the next catalogue task.