FP-008
Open a category containing twenty similar products.
One product is missing its weight. Another records capacity as 1500 ml while its neighbours use 1.5L. A third contains an attribute in its description that neighbouring products present in the specifications.
None of the pages looks broken. Each product remains perfectly capable of being viewed and purchased.
These are the kinds of catalogue problems that are easy to dismiss when encountered one product at a time.
Then the same problem appears on another product.
And another.
Soon, what looked like one minor imperfection exists across an entire product range.
Look at any one of those products and the problem still appears small.
Look across the catalogue and it becomes harder to dismiss.
This publication investigates why seemingly small catalogue problems become significant when they are repeated across a catalogue.
Catalogue problems are usually discovered one product at a time.
A missing specification is noticed on one product page. An inconsistent title appears in a search result. An incomplete attribute becomes obvious while reviewing a category.
Viewed individually, each problem may appear minor.
That makes individual severity an understandable way to judge what deserves attention. A broken product page looks urgent. An incorrect price looks serious. One missing specification usually does not.
But catalogues repeat structures, information and conventions across products.
When a small problem is repeated with them, its significance changes.
A missing product weight on one item affects one product. The same information missing from 300 comparable products makes an entire range harder to compare by weight.
An inconsistent product name may create uncertainty once. When the same inconsistency appears throughout search results and category pages, customers repeatedly have to work out whether differently named products are genuinely different.
The individual problem may still be minor, but it can affect a much larger part of the catalogue.
Catalogue problems therefore cannot be judged solely by how serious they appear where they are first discovered. Their significance also depends on how widely they occur and how many customer decisions encounter their consequences.
Small catalogue problems become large catalogue problems through repetition.
Why do seemingly small catalogue problems become significant when they are repeated across a catalogue?
Open a product page and look closely.
The title is clear. The images are present. The price is correct. The description explains the product reasonably well.
Then you notice one missing specification.
Perhaps a dining table lists its assembled dimensions but not its weight. Perhaps a jacket gives its material but not the fabric composition. Perhaps a coffee lists its origin but not its roast level.
It is a genuine problem.
But compared with everything else that is correct, it hardly looks urgent.
It’s only one field.
That judgement makes sense while looking at one product.
Now open the next product in the range.
The same field is missing.
Open another.
Missing again.
Search the category and compare ten similar products. Eight of them lack the same information.
What appeared to be one incomplete product page now looks different.
Nothing about the missing field itself has changed.
What changed was the view of the catalogue.
That creates an important question:
— Small Problems Look Small When You Look at One Product. Product pages contain a lot of information.
Against everything that is present, one missing piece can be difficult to care about.
Consider a pair of riding boots.
The page contains six images. Available sizes are clear, the price is correct, and the description explains the construction and intended use. Colour options are available.
But the calf width is missing.
The page does not suddenly look broken. A customer can still see the product, understand what it is and add it to their basket.
From the perspective of that one page, the missing measurement appears minor.
The same thing happens elsewhere.
One kettle lists its capacity as 1.5L while a neighbouring product uses 1500 ml.
Neither page fails because of it.
That is precisely why these problems are easy to underestimate.
When we look at one product page, we naturally judge the problem on that product alone.
And at that scale, many catalogue problems genuinely do look small.
— The Same Problem Rarely Stops at One Product. Now stop looking at the individual product and look across the range.
The capacity inconsistency noticed on one kettle may appear across an entire appliance category:
1.5L
1500 ml
1.5 litre
And on several products, no structured capacity value at all.
Across the category, the same small inconsistency appears again and again.
Sometimes the pattern already exists in the supplier information behind the range.
Publish those products from the same information and the catalogue inherits it.
Nobody needed to create the same inconsistency product by product.
A catalogue of 5,000 products does not need 5,000 different problems to contain 5,000 problematic instances.
Sometimes it only needs the same small problem repeated 5,000 times.
— Customers Encounter the Repetition Too
Imagine a customer comparing four dining tables.
The first gives its dimensions in centimetres and includes the table height, width and length.
The second gives only width and length.
The third provides measurements in millimetres.
The fourth gives complete dimensions but places them inside the description rather than the specifications.
Every product page contains enough information to understand that a table is being sold.
Nothing is obviously broken.
But the customer trying to determine which table will fit a particular space now has to find the measurements, convert some of them and work out whether the products can actually be compared on the same basis.
What looks like a few small inconsistencies across individual products makes the range harder for the customer to compare.
Consider pack quantity.
One pet food product includes 12 × 400g in the title.
Another gives 400g × 12 in the specifications.
Another simply says Multipack.
The customer has to establish whether the products contain equivalent quantities before they can meaningfully compare price.
Customers encounter the same inconsistencies as they move between products and try to compare them.
Some catalogue problems announce themselves.
A product page returns a 404. A product has no image. The price is obviously wrong. A variation cannot be selected. The Add to Cart button does not work.
Nobody needs much persuasion that these problems deserve attention.
Their severity is visible in a single occurrence.
Small catalogue problems are harder to judge because each occurrence can remain individually tolerable.
One missing product weight may not prevent a purchase. One inconsistent attribute may not prevent a customer understanding the product.
That creates a natural assumption:
The bigger the individual problem, the bigger the catalogue problem.
But that judgement only tells us something about the individual occurrence.
It does not tell us how far the problem extends.
Search the catalogue for the capacity attribute.
The results contain 1.5L, 1500 ml, 1.5 litre, 1.5 litres and blank values.
Scroll down.
The pattern continues through hundreds of products.
No individual value looks catastrophic.
Yet this is no longer one untidy product page.
The individual problem is no more serious than before. It simply occurs across far more products.
Those two catalogue conditions are not equivalent.
In one, a product needs a small correction.
In the other, customers cannot rely on a consistent representation of capacity throughout the range.
The same thing happens with missing information, uneven attributes and inconsistent product titles.
Each occurrence can remain individually minor while the catalogue repeats it across dozens, hundreds or thousands of products.
None of these problems needs to be serious on its own. The problem is that the same small issue can occur across hundreds of products.
Perhaps, then, asking how serious the problem looks on one product is not enough.
We also need to know where else it occurs and what customer decisions depend on the information affected by it.
One missing field is still one missing field.
But its significance no longer ends with the product where it was first noticed.
A small catalogue problem does not need to become more severe to become more consequential.
It only needs to be repeated.
A missing product weight on one dining chair affects one product.
If the same field is missing from 300 furniture products, the missing information itself is no more serious than it was on the first product.
What changed is how much of the catalogue carries it and how many customer decisions encounter its absence.
This is the distinction that matters.
The size of the problem and the extent of its effect are not the same thing.
A problem can be minor on one product and still matter when the same problem appears across hundreds of products.
Product ranges often use the same attributes, structures, terminology and types of information. When the same problem occurs across them, the catalogue presents that problem again and again.
Customers encounter its consequences wherever that information is needed to understand or compare products.
Small catalogue problems become large catalogue problems through repetition.
This does not mean every small problem deserves the same attention as a broken page, incorrect price or unavailable purchase function.
It means we cannot judge its importance only by looking at one occurrence. We also need to know how widely the same problem appears across the catalogue.
A missing attribute on one product and the same attribute missing from an entire category may look identical when either product page is viewed alone.
They are not the same catalogue problem.
One affects a single product.
The other affects an entire part of the catalogue.
Once you begin looking for repetition, familiar catalogue reviews start to look different.
You find a dining table with no product weight.
Instead of simply correcting the product and moving on, another question becomes difficult to ignore:
Where else is this missing?
You find one kettle with capacity written differently from the rest of its range.
You can standardise the value.
But first it is worth knowing whether you found one inconsistent attribute or one example of several different conventions used across 600 products.
The first product is where the problem became visible.
It is not necessarily where the problem ends.
Catalogue practitioners still need to recognise serious individual problems. But they also need to notice when an ordinary problem is appearing repeatedly across the catalogue.
The question is no longer only how bad the individual product page is.
It is also how much of the catalogue has the same problem, and how many customer decisions are affected by it.
One missing attribute is easy to overlook. If the same attribute is missing from a thousand products, looking at each product separately can still make every occurrence appear minor.
Finding the problem on one product is only the starting point.
The next question is whether the same problem exists elsewhere in the catalogue.
Catalogue problems are usually discovered one product at a time.
That is also where their significance is easiest to underestimate.
One missing specification or inconsistent attribute may matter very little when it appears once. Repeat it across hundreds of products and the individual problem remains minor, but far more of the catalogue is affected.
More products carry it. More comparisons are affected. More customers encounter the same missing or inconsistent information.
How serious the problem looks on one product therefore tells us only part of the story.
The significance of a catalogue problem depends not only on what is wrong, but on how much of the catalogue keeps repeating it.
FP-008 has considered problems that are already visible in the catalogue.
But what about product information that appears perfectly good today?
The specifications are complete. The description is accurate. The attributes are consistent. Customers have the information they need.
Does that mean the information will remain good?
That is the question explored in FP-009 — Good Product Information Doesn’t Stay Good.