FP-007
Open almost any established ecommerce catalogue and you will find an enormous amount of product information.
Sizes. Materials. Compatibility details. Answers to questions customers have asked over years of selling the products.
Much of that information was collected for a particular reason.
A specification was needed for a product page. An attribute was added for a filter. Compatibility information was included because customers kept asking about it. A description was rewritten because the supplier copy did not explain the product clearly enough.
The immediate job was completed.
But the information may still be useful elsewhere.
The same dimensions might help customers compare furniture. Knowing that one pair of boots is waterproof while another is not can help a customer choose footwear for wet conditions. Compatibility information can show which charger works with a particular laptop.
Much of this information already exists within the catalogue.
The question is where else that information could help the customer.
This publication investigates why product information becomes more valuable when it is organised and used beyond the product page it was originally created for.
Product information is often valued according to its most obvious purpose: describing the product on its page.
That is understandable.
Product pages need titles, descriptions, specifications, attributes, images and other information before customers can properly understand what they are buying.
Dimensions can describe a piece of furniture and help customers compare whether it will fit their space. A recorded shade can describe a cosmetic product and help customers filter the category to the colours they are considering. Compatibility information can explain which charger a laptop requires and help customers find the correct replacement.
This matters because customers do not experience product information only when reading individual product pages. They encounter it while searching, filtering, navigating categories, comparing alternatives, answering questions and deciding whether a product is right for them.
Product information becomes more valuable when the same knowledge can help customers discover, understand, compare, choose and ultimately buy products across the catalogue.
Why does product information become more valuable when it is organised and used beyond the product page it was originally created for?
A new product arrives from a supplier.
Someone downloads the images, cleans up the title and works through the description. Specifications are copied from a spreadsheet. Attributes are selected. Dimensions are checked. Compatibility information is added.
The page is reviewed.
Everything looks right.
The product is published.
At that moment, the product page appears complete.
The title identifies the product.
The description explains it.
The specifications provide the details.
The attributes classify it.
The compatibility information answers an important question.
That is how product information is commonly created: one requirement at a time, usually in response to the immediate needs of a product page.
But consider what happens afterwards.
A customer wants to compare this product with another.
Another wants to filter the category by one of its specifications.
Someone else wants to know which accessories work with it.
Suddenly, information collected for one purpose is needed for another.
The specification is still the same specification.
The compatibility fact is still the same fact.
The product has not changed.
Only the reason for needing that information has changed.
Which raises a larger question.
The Same Information Keeps Being Needed Again
A customer calls because they cannot decide between two wheelbarrows.
The salesperson barely hesitates.
One is lighter. The other carries a heavier load.
The distinction is obvious to someone who sells the products every day.
Yet open the two product pages and that same distinction may be surprisingly difficult for the customer to see.
The business can know something useful about the product that the catalogue hasn’t made easily accessible to the customer.
Product Pages Often Trap Useful Information
Open several outdoor lights from different suppliers that need to communicate water resistance.
One supplier calls the product waterproof.
Another provides an IP rating in a specification table.
A third records water resistance as an attribute.
To someone reading the three pages, the connection may be obvious.
Now try to build a filter for waterproof products.
Only one of those records may be ready to use.
The information exists across all three products.
But the information is not recorded consistently enough to use in the same filter.
The same problem appears elsewhere. Furniture dimensions may be recorded as individual attributes on one product and buried in a single text field on another. An electronics supplier may list compatible models while another says only that an accessory “fits selected models.”
The information may be there, but not recorded consistently enough to use elsewhere.
Customers Rarely Need Product Information Only Once
Follow a customer looking for a pair of walking boots.
They begin with more products than they can reasonably consider.
They filter the category to their size.
They remove boots that are not suitable for wet conditions.
The customer opens the remaining options.
Product descriptions explain how the boots are intended to be used. Specifications show differences such as weight and materials.
Eventually, only a few serious alternatives remain.
A comparison makes the differences clearer.
A buying guide helps the customer decide which pair best suits how they intend to use them.
Then they buy.
The customer’s size helped narrow the category before they opened a product page. Waterproofing information helped them remove unsuitable boots and remained useful when they compared the final options.
Complete the title.
Write the description.
Populate the specifications.
Select the attributes.
Add the images.
Publish the page.
Each field has a purpose, and each product has a page that needs completing.
There is nothing wrong with that approach.
A catalogue could not be built without it.
But working field by field can make each piece of information seem tied to that field.
A specification belongs in specifications.
An attribute belongs in attributes.
Compatibility belongs in the description or compatibility field.
Once the information is present and correct, the task appears complete.
Customers do not think about product information that way.
They do not care which field contains the answer.
They care whether they can find the information they need.
A customer already owns a cordless drill and needs another battery.
They open the battery category and several products appear suitable.
Somewhere inside one of those product records is a simple fact:
This battery is compatible with the drill they own.
If that fact exists only as a sentence buried inside the description, the customer may eventually find it.
But the catalogue may be unable to use the same information to narrow the category or remove incompatible batteries.
The same compatibility information could help narrow the category, remove incompatible batteries and help the customer choose one that fits their drill.
The information on a product page does not have to be useful only on that page.
The dimensions entered on a sofa product page can later help customers compare which sofas will fit their available space.
A shoe width recorded as an attribute can later help customers filter the category to products available in a wide fit.
Compatibility information showing which replacement filter fits a particular air purifier can help a customer find the correct filter for the model they own.
Product information becomes more valuable when the same knowledge can help customers discover, understand, compare, choose and ultimately buy products across the catalogue.
Open a product record and look at a completed specification.
The dimensions are there.
Nothing is missing.
Previously, that may have been enough to consider the job complete.
Now another question appears.
Can customers filter by those dimensions?
Can they compare them consistently across similar products?
The same questions can be asked of attributes, compatibility information and the answers to questions customers repeatedly ask.
Not every piece of information needs to be used in every part of the catalogue.
Completeness still matters.
A catalogue cannot use information it does not have.
But having all the required information does not mean it can easily be used elsewhere in the catalogue.
So instead of asking only,
“Do we have this information?”
we can also ask,
“Where else could this information help the customer?”
A product page brings together the information customers need to understand a product.
Dimensions describe its size. Attributes identify characteristics customers may need to filter by. Compatibility information tells customers what the product works with.
But those uses do not have to end on the product page.
The same dimensions can help customers compare products. The same attributes can help them narrow a category. The same compatibility information can help them find the right replacement or accessory.
Product information becomes more useful when it is available where customers need it to find, compare and choose products.
Its value grows when that information can be put to work for the customer.
A missing size attribute may appear to be one small omission.
An incorrect furniture dimension may look like one small discrepancy.
A battery incorrectly listed as compatible with a particular tool may seem like a problem with just one product.
Yet a problem that appears on one product page may also affect how that product is found, compared or understood elsewhere in the catalogue.
That raises the next question:
Why do seemingly small catalogue problems become significant when they are repeated across a catalogue?
That is the question explored in FP-008 — Small Catalogue Problems Don’t Stay Small.