AP-022
An agency can research, correct and approve a client’s product information properly and still find months later that some of it has fallen behind.
Nothing necessarily looks wrong with the page.
The title is still there. The specifications are still populated. The description has not been altered. The information may be exactly what the agency approved when the product was first prepared.
Yet something relevant may have changed elsewhere.
A supplier has revised a specification. A new model has been released that affects an existing product’s compatibility. The client’s support team has answered the same shopper question often enough to realise that the current information does not explain something shoppers repeatedly need to understand.
None of those changes necessarily alters the catalogue by itself.
The page can therefore remain untouched even though something the information depends on has changed.
That does not mean every older product page needs constant review.
Sometimes nothing relevant has changed and the information remains completely accurate, complete and useful.
The maintenance question is:
What should cause an agency to reconsider previously good product information when the changes that matter may happen outside the catalogue?
Consider a product specification that lists a width of 50 cm.
The agency checked the supplier information when the page was prepared. The product was 50 cm wide, the catalogue was correct and the value was approved.
Months later, the supplier revises the product and the current version is now 52 cm wide.
The catalogue still contains 50 cm.
Nothing has failed inside the catalogue. Nobody has accidentally edited the value. The agency did not publish the wrong specification.
The reality the specification describes changed afterwards.
Looking only for visible catalogue errors would therefore miss the reason the information deserves another look.
The important event occurred somewhere else.
Many catalogue changes begin with an explicit request.
A client asks the agency to update a specification, add a product or remove a discontinued item.
The requested change gives the agency something concrete to act on.
But not every relevant change arrives as a catalogue instruction.
A supplier specification may change without the agency receiving a specific catalogue request.
The client’s support team may see shoppers repeatedly ask how a product fits without those enquiries becoming a product-information request.
The agency can therefore maintain every request it receives correctly while information affected by changes outside those requests is never reconsidered.
An explicit request is a useful maintenance trigger, but it is not a complete basis for deciding which existing information deserves another look.
Different kinds of product information remain current for different reasons.
A product’s dimensions remain current while the physical dimensions remain unchanged.
Compatibility information remains current only while it continues to reflect the relevant products, models or systems the item is compatible with.
Fit guidance may remain technically accurate while repeated shopper questions reveal that the existing explanation is not sufficient to help people choose confidently.
These are different dependencies.
The catalogue may contain all of them on the same page, but the events that could make each one worth reconsidering are not the same.
That matters because a maintenance approach focused only on the page cannot reliably reveal changes in those underlying conditions.
Nothing in the dimensions field indicates that the manufacturer has revised the product.
Nothing in the existing compatibility list indicates that another supported model has entered the market.
Existing sizing guidance does not automatically change because support staff have learned more about where shoppers become uncertain.
If the agency wants previously good information to remain useful, the question is not simply whether the page has changed.
It is whether something the information depends on has changed.
Because those dependencies differ, the age of the information is not an equally reliable basis for deciding when each piece deserves reconsideration.
A simple way to manage ageing information is to review it periodically.
Every six months, for example, an agency could review the product information again to check whether it is still current.
That may be operationally useful.
It can create a regular opportunity to find things that would otherwise remain unnoticed.
But elapsed time does not tell the agency whether the information has actually fallen behind.
Take two pieces of information approved on the same day.
A product dimension may remain accurate for three years because the product itself has not changed.
A compatibility list for an electronics accessory may need attention within six months because the manufacturer has released several new devices that the accessory supports.
Both were approved at the same time, but one may remain current much longer than the other.
What matters is what has happened to the reality each piece of information depends on.
Periodic review can therefore be a useful safety net without being a reliable basis for deciding when information needs reconsideration.
Review too infrequently and meaningful changes may remain unnoticed for months.
Review everything too frequently and the agency spends time repeatedly checking information whose underlying conditions have not changed.
Neither problem is solved simply by choosing a better number of months.
The more useful question is:
What would have to change before this information deserved another look?
For dimensions, the answer might be a product or supplier specification change.
For compatibility, it could be the arrival or removal of related models.
For fit guidance, it might be repeated questions, returns or other evidence that shoppers need an explanation the current information does not provide.
The trigger follows from what the information is there to represent.
A client organisation can know that something has changed without that knowledge reaching the product information affected by it.
The supplier team receives a new specification file.
The client’s support team sees the same question repeatedly.
A member of the client’s buying team learns that an accessory is being replaced.
Each change may be well understood by the team that encounters it.
That knowledge does not alter the catalogue unless someone uses it to reconsider the relevant information.
This is the missing link.
Previously good product information can fall behind when changes that could affect it are not connected back to that information for reconsideration.
The agency does not need every event occurring around every product.
It needs a dependable basis for recognising the kinds of change that could mean previously approved information should be reassessed.
How that connection is created can vary.
One client may have dependable supplier change notices. Another may need periodic checks of information that is likely to change frequently. Another may have useful support-team feedback.
Different clients and catalogues may justify different mechanisms.
The professional requirement is more basic than the mechanism.
Relevant changes need some path back to the information they may affect.
Connecting change back to product information does not mean reopening the entire catalogue whenever something happens.
If a manufacturer changes one product dimension, the likely question is whether that dimension appears anywhere that now needs correction.
There is no automatic reason to revalidate unrelated care instructions or rewrite the full description.
If a new device becomes compatible with an existing accessory, the compatibility information may deserve reconsideration. That does not mean its material, physical dimensions and warranty information also require reassessment.
If shoppers repeatedly misunderstand how to measure for a particular boot, the useful response may be to reconsider the sizing guidance for that product or comparable products.
The scope should follow the plausible effect of the change.
Sometimes that effect will be very narrow.
Sometimes one change will affect several products or several pieces of information.
The point is not to minimise the response or expand it automatically.
It is to connect what changed with the information that could reasonably depend on it.
That allows the agency to maintain current information without treating every change as a reason for another full catalogue audit.
Previously approved product information should not require attention simply because time has passed.
Nor should the agency assume that it remains good until somebody finds a visible error or asks for a specific correction.
Neither provides a complete basis for deciding when existing information should be reconsidered.
The relevant change may occur outside the catalogue.
Agencies maintaining product information should therefore establish a dependable basis for connecting changes that could affect existing information back to that information for proportionate reconsideration, rather than relying on visible errors, elapsed time or explicit client requests alone.
Relevant changes may include changes to the product itself, supplier specifications, compatibility, related products or what shoppers repeatedly need help understanding.
The exact mechanism can differ between clients and catalogues.
The response can then remain proportionate to what changed and what it could reasonably affect.
Good product information does not need constant rewriting.
It needs a way to be reconsidered when the reality that made it good no longer stays the same.