OP-007
An existing product can be represented correctly in the catalogue and still require attention later because something about the product changes.
A manufacturer revises a specification. A variant is withdrawn. Compatibility with another product changes. A dimension, capacity or technical characteristic is updated.
Sometimes the required catalogue change is straightforward.
If the packaged weight changes from 1.25 kg to 1.3 kg and that value appears in one structured attribute, the Operator can verify the new information, update the value and complete the task.
Other changes are less contained.
Suppose a manufacturer advises that an accessory previously described as compatible with Models A, B and C is now compatible only with Models A and B.
The obvious correction is to remove Model C from the Compatibility attribute. But compatibility may also be stated in the description. The accessory may be linked to Model C as a related product. A filter may use the same compatibility information.
The supplier has identified one change to the product.
The Operator still has to determine whether correcting the Compatibility attribute is enough.
When an existing product changes, how does the Operator determine what else in the catalogue needs to change with it?
Some changes genuinely are local, so the Operator does not need to inspect everything whenever a product changes.
But correcting the information identified in the latest supplier update does not by itself establish that the task is complete.
The question is how to determine the boundary of the product change within the catalogue.
Consider a product whose packaged weight is maintained as a structured attribute.
The manufacturer revises that weight from 1.25 kg to 1.3 kg.
The Operator establishes that the revised specification is reliable and checks how the information is used.
The value appears once. It does not affect compatibility, classification, variant structure, product relationships or maintained comparison information.
In this case, one attribute is affected and updating it accounts for the change.
Looking further does not reveal another consequence.
A product change does not therefore determine the size of the maintenance task by itself. The required work depends on what that change affects in the catalogue.
That becomes more demanding when one product fact is represented in several places.
Suppose an accessory has been maintained as compatible with Models A, B and C.
The manufacturer later removes Model C from the compatibility specification.
The Operator changes the Compatibility attribute.
That correction may be accurate in itself. But if the description still says that the accessory works with Models A, B and C, the description is now inaccurate.
If Model C still links to the accessory as a recommended related product, that relationship also needs reconsidering.
One changed fact can therefore affect several parts of the catalogue.
The Operator needs to understand where that fact is represented or used before deciding whether the first correction is enough.
But not every affected part of the catalogue will contain the previous wording or value directly.
Consider a product whose maximum supported load changes.
The old value may appear directly in a technical specification, making that correction easy to find.
But capacity may also affect how the product is classified or which other products it is associated with.
Those catalogue elements might not contain the old number anywhere. They can still require attention because the revised capacity changes whether the existing classification or relationship remains appropriate.
The same reasoning applies when a product change adds something that was not previously true.
Suppose a manufacturer expands compatibility so that an existing accessory now also supports Model D.
There is no obsolete Model D value to find because that compatibility did not previously exist.
Yet the new compatibility may justify adding Model D to a structured attribute, including the accessory in a relevant filter or establishing a product relationship that previously would have been incorrect.
Some catalogue information therefore states the changed product fact directly.
Other catalogue structures or relationships depend on what that fact means.
Finding every occurrence of the previous wording is not enough.
The Operator needs to establish which parts of the maintained catalogue should now be different because the product itself is different.
That gives the Operator a practical boundary.
There is no reason to reconsider every piece of information associated with the product. The task extends only to the catalogue information, classifications, filters, relationships or other maintained elements affected by what changed.
Sometimes that boundary is reached almost immediately.
The new packaged weight affects one attribute and nothing else.
Sometimes the change reaches further.
A compatibility change affects the structured compatibility value, a product relationship and descriptive information.
Sometimes the change introduces something the catalogue did not previously need to represent, such as a newly supported relationship or variant.
Some changes can also alter whether the item should continue to be represented as the same product. Where product identity, applicable identification requirements or the nature of the change requires a distinct product record, that question has to be resolved first. The reasoning here applies when the changed item continues to be maintained as the existing product.
There are also cases where no catalogue change is required. A manufacturer can alter something about a product that the catalogue does not represent and that has no bearing on any classification, relationship or other information being maintained.
Some affected outputs may update automatically. Changing a structured compatibility value might also update a filter that uses that same data. The Operator does not need to repeat the change manually, but still needs to establish that the filter now reflects the revised compatibility.
The extent of the task therefore follows what the product change actually affects in the catalogue.
Where the changed item continues to be maintained as the same product, the catalogue is affected wherever that change makes maintained information, classifications, filters, relationships or other catalogue elements inaccurate, incomplete or no longer appropriate.
The extent of the task is therefore determined by which parts of the catalogue the product change affects, not by the size or location of the update through which the Operator first encounters it.
A product change may require no catalogue change, one local correction or several connected changes.
The Operator cannot establish that extent merely from the number of facts supplied by the manufacturer or by locating every occurrence of the previous wording.
What matters is which parts of the maintained catalogue should now be different because something about the product has changed.
When an existing product changes, the Operator should first establish whether the item should continue to be maintained as the same product.
Where it should, distinguish the incoming update from what that update affects in the catalogue. First establish what is now true about the product. Then determine which catalogue information, classifications, filters, relationships or other maintained elements are affected.
For a contained specification change, that may confirm that one attribute update is enough.
For a compatibility change, it may reveal that a structured value, product relationship and descriptive information all require attention. Newly supported compatibility may require something to be added rather than an obsolete value to be removed.
The Operator does not need to reopen unaffected material.
Nor should every occurrence of related language be changed mechanically. The same underlying fact may legitimately be expressed differently in a technical attribute, a description or another part of the catalogue. What matters is whether each affected representation remains accurate and appropriate for what is now true of the product.
Where another output is generated from the information being changed, the Operator can establish that it has updated correctly rather than reproduce the same change manually.
This keeps the response proportionate to what the product change actually affects.
This gives the Operator a practical boundary for deciding when a product-change task is complete.
Completion is not determined by the size of the supplier update or simply by whether the first visible correction has been made. It depends on whether the parts of the catalogue affected by the product change have been accounted for.
That allows genuinely small changes to remain small.
If one attribute is the only thing affected, the Operator can change it and move on. Where several parts of the catalogue are affected, there is a clear reason to address them rather than encounter the remaining problems later as separate inconsistencies.
Products continue changing after their pages have been created, and those changes do not necessarily follow the boundaries of the field, page element or supplier record through which the Operator first encounters them.
The Operator does not have to assume that everything needs reconsidering. They also do not have to assume that one correction necessarily settles everything.
Where the affected information helps Shoppers find, understand, compare or choose products, accounting for the relevant changes can also prevent different parts of the catalogue from presenting outdated or incomplete information about the product.
For the Operator, the important gain is a more dependable basis for knowing how far a product change reaches and when the resulting catalogue task is complete.