OP-023
After a catalogue goes live, the Operator repeatedly encounters situations they have dealt with before.
Another product needs to be added to an established range. A supplier changes a specification. A discontinued item needs to be removed. New compatibility information arrives for several existing products. A product page needs to be updated because something about the product has changed.
Familiarity helps. The Operator does not need to approach every one of these situations as though they have never seen it before.
But familiarity creates another problem. When a task feels routine, important actions can start depending on what the Operator happens to remember that day.
Suppose a supplier changes the packaged dimensions of an appliance. The Operator updates the dimensions in the specification table because that is the obvious place to make the correction.
The same dimensions are also used in the delivery information.
If the Operator remembers that second use, both are updated. If they do not, the catalogue now contains two different values for the same product.
They may already know that both places need attention. The problem is not necessarily a lack of knowledge. All the necessary updates simply did not happen on this occasion.
That matters because much of catalogue operation after launch is made up of situations that occur again and again. If important actions have to be remembered or reconstructed every time, the quality of the result can vary even when the Operator understands what good practice requires.
Good catalogue operation therefore depends not only on knowing what to do. It also depends on making the right actions dependable when familiar situations return.
When the same kinds of catalogue situations keep recurring after launch, what should determine which Operator actions become consistent habits?
Not everything an Operator does repeatedly deserves to become a habit.
Some actions are repeated simply because that is how the previous product was handled. Others remain appropriate because the same catalogue requirement genuinely applies each time.
The difference matters.
A repeated behaviour is useful only when there is a dependable reason for repeating it.
Consider an Operator adding products to an established footwear range.
The existing products use the same core attributes: size, colour, material, gender classification and product type. After adding enough products, the task becomes familiar.
The Operator may copy the previous product and replace the obvious values. That can be efficient. But suppose the previous shoe was available only in standard width and the new model comes in standard and wide fittings. Copying the previous treatment can leave that important difference unrepresented.
The behaviour was consistent. That did not make it dependable.
A more useful habit is to check which requirements apply to the new product, confirm the information needed, and reuse only the treatments that still fit.
Most products may fit the existing pattern. When one does not, the difference becomes something to investigate rather than something to force into the previous treatment.
This is why a good habit cannot be reduced to doing the same thing every time.
The value is that, when the familiar situation occurs, the Operator reliably checks what is already known to matter. If something does not fit, they recognise the difference and decide what to do about it.
A useful catalogue habit connects a recurring catalogue situation with a dependable response.
It means important actions do not have to be remembered or reconstructed from the beginning every time the situation occurs.
But repetition alone is not enough.
If an existing treatment is incomplete, outdated or inappropriate, repeating it consistently only reproduces the weakness. A habit is useful when there is a dependable reason for repeating the behaviour and the Operator still checks whether the current situation is different in a way that matters.
This gives habits a specific role in catalogue operation.
With a useful habit, the Operator can preserve what has already been established without assuming that every occurrence will be identical.
The Operator can repeatedly apply the parts that are known to matter and direct fresh judgement towards the part that is new, unusual or unresolved.
That is different from following precedent blindly.
It is also different from relying entirely on experience and memory.
A standard can define the requirements that apply to the catalogue. Operator knowledge can explain why those requirements matter. A system may support or automate parts of the response.
A good operating habit helps make sure the relevant action actually happens when that recurring situation appears again.
Consider a catalogue of electric kettles.
It already contains a standard 1.7-litre stainless-steel kettle, a 1.7-litre glass kettle and a 1.7-litre kettle with variable temperature control and a keep-warm function.
Now another kettle is being added.
It has a 1.7-litre glass body, but it also has variable temperature control and a keep-warm function.
The Operator has added kettles many times before.
They have also developed a habit.
Whenever a new kettle arrives, they find the most similar existing product, duplicate its page and replace the information that is different.
For this product, the glass kettle looks like the obvious starting point.
The Operator duplicates that page.
The title changes. The images change. The price and SKU change. The capacity is already correct. The glass body is already correct. The page quickly looks like the new product.
But the product on the copied page does not have variable temperature control or a keep-warm function.
Those differences have to be noticed.
If the Operator sees them in the supplier information, they may add them to the description. If they remember that temperature control is also recorded as a catalogue attribute, they may update that too.
If they do not, the new kettle can be published without everything that distinguishes it from the ordinary glass kettle.
The Operator has followed their habit perfectly.
The habit has made an important part of the result depend on what the Operator notices afterwards.
Under this habit, the Operator starts with the previous product and has to notice everything that needs to change.
Now consider a different habit.
Whenever a new kettle enters the catalogue, the Operator first confirms the product information already used in the catalogue to distinguish and compare kettles.
Capacity.
Body material.
Temperature control.
Keep-warm function.
Automatic shut-off.
Only after those details are confirmed does the Operator choose an existing page to reuse.
The same new kettle arrives.
This time, before duplicating anything, the Operator records:
1.7 litres.
Glass.
Variable temperature control.
Keep-warm function.
Automatic shut-off.
The Operator can still duplicate the existing glass-kettle page. There is no reason to rebuild everything from the beginning.
But now the differences are already visible before anything is copied.
The glass body and capacity can carry across.
The missing temperature-control and keep-warm treatments cannot.
They add those values in the relevant catalogue fields and treatments, then check that the Shopper can see and use them in the same way as on other kettles with those features.
In both versions, the Operator uses a habit and reuses an existing product page.
The difference is what becomes dependable under each habit.
With the first habit, duplication is dependable, but noticing important differences still depends on memory.
With the second, the important checks happen first. Duplication comes only after those facts are established.
That is what makes the second habit useful.
The Operator still has to establish what every new kettle contains. Under this habit, they establish the things that matter before they overlook a difference because the previous product is familiar.
The Operator should not have to rediscover every established catalogue requirement whenever a familiar situation returns.
Where the same kind of catalogue activity happens repeatedly, useful habits can carry forward the actions that have already proved necessary.
That makes day-to-day catalogue operation more dependable without turning it into mechanical repetition.
The kettle example reduces that difference to two operating patterns:
Ineffective Habit: previous product → copy → notice differences.
Effective Habit: establish relevant facts → compare → reuse what remains applicable.
The important qualification is that the Operator still has to understand what the habit is for. A repeated action should have a dependable basis, and it should be reconsidered when the products, information, catalogue requirements or operating conditions change.
Good habits therefore do not remove judgement from catalogue operation.
They reduce the need to repeatedly reconstruct what is already established, leaving the Operator better placed to notice and deal with what is different.
A good catalogue depends on both: dependable behaviour for what is already understood, and Operator judgement when the familiar pattern no longer fits.