Customers Can't Find Products? Fix the Catalogue First

• When customers can't find products you list, the catalogue is usually the problem, not the theme.
• Customers shop by fit, use, size, occasion and brand. Stock systems often name them by supplier code and department.
• Collections and filters can only be as good as the product data underneath them. Record the attributes first.
• Before spending anything, read three sources: searches that return nothing, "do you carry" emails and collection pages people leave.
• A new theme is the answer when it can't display the structure you've built. Find that out last, not first.

Another email asks whether you carry something you've stocked for years. It's on the website. The customer couldn't find it, and they're one of the few who bothered to ask. The rest left.

When that happens often enough, the natural conclusion is that the store looks dated and needs a new theme or a redesign. Sometimes it does. But a theme decides how products are displayed. It doesn't decide what they're called, which group they sit in, or which details are recorded about them. If customers can't find products, those three things are where to look first, and none of them change when the theme does.

This is common in established retailers with long histories. The catalogue grew one supplier delivery at a time, named the way the stock system or the buyer needed, and the online store was built on top of that data. Nobody made a mistake. It's what happens when the system that counts the stock also becomes the system that sells it.

A stock system needs a unique, countable name for every item. A customer needs a way to narrow down. Those are different jobs, and a store that only does the first one makes the customer do the second in their head.

Illustrative example. A family-run kitchen store, made up for this guide. It doesn't describe a client.

Every phrase in the middle column is a search the store can fail, and each one points at a fact the product record doesn't hold. If nobody recorded which pans work on induction, no search box, filter or theme can sort by it.

This isn't a small-store problem. Baymard Institute's 2026 search benchmark of more than 170 sites and apps found 56% fail to adequately support users' search needs. Searches by feature, such as material or size, caused issues on 39% of sites, and searches by use case, such as a spring jacket or a wedding gift, on 43%. Baymard notes that use-case searches often need the catalogue tagged by use, and that in its testing, people whose search for a specific product failed were quick to conclude the site didn't carry it. That's your "do you carry" email.

1. Searches that return nothing

Your search box records what customers type. On Shopify, the Search & Discovery app has a report of searches with no results, alongside searches that returned results nobody clicked. Its in-app view covers the last 30 days, and other date ranges sit under Analytics, then Reports. Other platforms and search apps keep an equivalent.

Sort the zero-result terms into three piles. Things you sell under another name. Things you sell but never described that way. Things you genuinely don't stock. The first two piles are your renaming and attribute list. The third is a conversation for whoever does the buying.

2. The "do you carry" emails and calls

Your inbox and the person who answers the phone hold better research than any survey. For a month, have them note every question about whether you stock something: the words the customer used, and whether the answer was yes. Every yes is a product the store failed to show. The customer's wording is the label it should have had.

3. Collection pages people leave

In your analytics, find the collection pages people land on and leave without opening a product. A long collection with a high exit rate often means the shopper couldn't narrow it: two hundred pans on one page with no way to choose by material, size or hob. That's a filter and attribute problem wearing a design problem's clothes.

Work through one category at a time, in this order, because each step depends on the one before it. The examples use Shopify's terms, since many established retailers run on it. The steps are the same on any platform.

1. Decide the attributes customers choose by

For each category, list the three to five facts a customer uses to rule products in or out. For pans that might be material, size, hob compatibility and brand. For aprons it's something else entirely. These become fields on every product in the category, filled in consistently, not a pile of free-text tags. On Shopify, things a customer picks usually live as product options, such as size or colour, and facts about the product live in metafields.

2. Build collections from the attributes, not by hand

A collection someone curates by hand is out of date the day the next delivery arrives. A collection built from a rule, every pan where hob compatibility includes induction, fills itself as products are added, as long as the attribute is filled in. Shopify's automated collections can use product data, including metafields, as their conditions. Plan collections around how people shop: by use, by occasion, and by brand where brand is how your customers actually choose.

3. Turn the attributes into filters

Filters let a shopper narrow a long collection by the facts you recorded. Shopify’s filter documentation lists what a filter can draw on: availability, category, price, product type, vendor, tags, product options and metafields. A filter only knows what the products carry, so an attribute filled in on half the category hides the other half the moment someone uses it. Shopify also doesn't display filters on a collection of more than 5,000 products, which is one more reason to split a sprawling catalogue along the lines people shop.

4. Rename in the customer's words

Product titles should describe what a customer is looking for. Keep the supplier code in the SKU field, where your staff need it. Take the words from your zero-result searches and your inbox, then fix the navigation labels the same way. The department name the business uses internally isn't always the word a shopper scans for.

This is the part of a store rebuild that rarely shows up in a theme demo. When we worked with Wei's Western Wear, a third-generation family-run retailer, on their Shopify rebuild, the work included reorganizing their SKUs into collections a customer can navigate. Whatever the platform, that's the work we'd want settled before anyone picks a theme.

Sometimes the data is good and the store still can't show it. These are real reasons to change the theme:

• It can't display filters. Shopify's filters need a compatible theme. You can set them up and customers still won't see them.
• The menu can't hold the structure. The categories customers shop by don't fit, or the mobile menu buries them.
• Product pages hide the attributes. A shopper filters by induction and can't see the detail on the page that confirms it.
• Collection and search pages are slow on a phone. People leave before the products load.

And sometimes it's the platform. If the way you sell doesn't look like a cart, such as made-to-order work priced by quote, rentals or a marketplace, a new theme won't fix it. We explain where Shopify stops fitting separately. If you do move platforms, the product and collection addresses customers and search engines already know need a plan, which is what a planned rebuild and migration covers.

Pick the category behind the most "do you carry" emails. Write down the attributes customers choose by, fill them in for every product in it, rebuild its collections from those attributes and switch on the filters. Rename the products using the words from your inbox. Then read the zero-result searches again a month later.

If the emails about that category slow down, you've found the real project, whether or not a new theme comes later. If the theme can't display what you've built, you'll know exactly what to ask the next one for. When you're there, this is how we approach website design and development.