OP-022
Catalogue problems do not always begin with incorrect product information.
Some begin when correct information is updated in one place but the consequence of that change is missed somewhere else.
An Operator may receive a confirmed update, correct the product specification and reasonably believe the task is finished. But the same product fact may already be used elsewhere in the catalogue.
Consider a bookcase listed as 28 cm deep. The supplier later confirms that the current version is 32 cm deep, so the Operator updates the specification.
The bookcase also has an Under 30 cm depth classification.
The product page now shows 32 cm, while the bookcase remains in the Under 30 cm depth classification.
The Operator has corrected the specification, but another use of the same product fact is now wrong.
That does not mean every product-information change has wider consequences. Sometimes one edit really is enough.
The practical difficulty is knowing when it is not.
When the Operator knows that a product fact has changed, what should determine how far that change needs to be carried through the catalogue?
A product fact does not have to appear as the same value everywhere it is used.
A dimension may appear as an exact specification and also determine which classification applies to the product. A compatibility fact may appear on the product page and also determine how the product is grouped in a comparison.
The difference is clear in the bookcase example.
Changing the depth from 28 cm to 32 cm clearly changes the specification. It also affects the Under 30 cm classification because that classification depends on the same depth.
The classification does not repeat 28 cm, but it is still affected by the change.
So the required update can extend beyond the places where the changed fact appears as an exact value.
Searching for the previous value can help find some affected information, but it cannot always establish the full extent of the change.
The bookcase classification does not contain 28 cm.
It says:
Under 30 cm
A search for 28 cm could find the old specification while completely missing the classification that has also become wrong.
The same issue arises whenever a product fact is used indirectly in a range, classification or comparison rather than repeated as an exact value.
Those uses can become incorrect without containing the previous value.
Finding the old information is therefore useful, but it does not define the boundary of the update. That boundary depends on how the changed fact is used and which of those uses remain correct.
When a product fact changes, the extent of the change depends on which existing uses are no longer correct.
A use can depend on the changed fact and still remain valid. Another can become incorrect without repeating the previous value.
What matters, therefore, is how the product fact is used, not simply where the old information appears.
When a confirmed product fact changes, the Operator should identify which existing uses no longer remain correct before treating the update as complete.
Consider an outdoor storage box whose confirmed width changes from:
118 cm → 123 cm
Before the update, the catalogue contains:
Product specification: 118 cm
Comparison value: 118 cm
Description: 118 cm wide
Width classification: 100–129 cm
The specification, comparison value and description all state the exact width, so each needs to change to 123 cm.
The width classification also depends on the product’s width, but 123 cm still belongs within the 100–129 cm range. That classification remains correct.
After the update, the catalogue contains:
Product specification: 123 cm
Comparison value: 123 cm
Description: 123 cm wide
Width classification: 100–129 cm
The Operator has changed the three uses that became incorrect and left the one that still represents the product correctly.
That is the practical change.
They do not need to change every related part of the catalogue. They need to identify the existing uses that the new product fact makes incorrect.
Where nothing else is affected, the task stays small. Where several uses are affected, they can be corrected as part of the same update.
When a product-information change is confirmed, useful context is already available.
At that point, the Operator already knows which product is affected, what the previous information was, what the new information is and why it changed.
That context may need to be recovered if an incomplete update is discovered months later.
An Operator who finds 32 cm on a product page and Under 30 cm in a classification may first have to establish which information is current. They may need to find the source of the change and establish why the information differs between the two parts of the catalogue. They must then determine whether anything else is affected.
Only after that investigation can the correction be made confidently.
Part of the later task is therefore spent recovering context that was already available when the original change was made.
Not every catalogue problem can be prevented this way. New products, new Shopper questions and new information can expose needs that could not reasonably have been identified earlier.
The opportunity is narrower: when the Operator already knows that a product fact has changed, they can deal with the affected catalogue information while the reason for the change is still understood.
For the Shopper, that reduces the chance of finding one measurement on the product page and conflicting information while filtering or comparing the same product.
For the Operator, resolving the affected uses during the update can avoid a later investigation into the same change. Resolving them while the reason for the change is still known is more direct than later having to establish what changed and what else it affected.