← All postsHow-to

Product catalog: how to structure one people can actually shop

A product catalog is a navigation problem before it is a design problem. Get the categories, the attributes and the naming right and everything downstream — search, filters, feeds — starts working.

How-toP

A product catalog is usually treated as a list of things to photograph. It is really a structure: how items are grouped, what attributes they carry, and what each one is called. Get that wrong and no amount of design fixes it — search returns nothing useful, filters do not narrow, and the same product appears under three names in three places.

The work is unglamorous and mostly happens in a spreadsheet before anything is published.

What a product catalog has to carry

  • A stable ID per product — an SKU that never changes, even when the name, price or photo does. This is what every other system will match on.
  • A name written the way customers say it, not the way the supplier's invoice says it.
  • One category per product, from a category tree you can state out loud. If an item genuinely belongs in two, use tags for the second.
  • Attributes that vary within a category — size, colour, material, capacity — as structured fields, never buried in the description.
  • Variants tied to one parent product, so a blue medium and a red large are not two unrelated listings.
  • Price, tax treatment and currency, plus availability. "Out of stock" is information; a missing product is a dead end.
  • One clear photo per variant that differs visually, and consistent framing across the catalogue.
  • A description that answers the three questions people ask before buying, rather than repeating the name.

The test of a category tree: can a stranger place ten of your products into it without asking you a question? If not, the tree is describing your business's internal logic rather than how customers look for things.

Naming and attributes decide whether search works

Search and filters are built on the fields you filled in, not on the pictures. A catalogue where size lives in the description cannot filter by size, and no search box will rescue it. This is the single most common reason small shops feel unbrowsable at a few hundred items.

Keep attribute values controlled. "Blue", "blue", "navy blue" and "Blue (dark)" are four filter entries for one colour, and cleaning them up later means touching every product. Decide the allowed values once and put them in the sheet.

Building it in the right order

  1. Start in a spreadsheet: SKU, name, category, attributes, variants, price, stock. Do not open a builder until this is clean.
  2. Write the category tree first and test it on someone who does not work for you.
  3. Fill attributes for one category completely before moving on — a half-filled catalogue produces filters that hide products.
  4. Standardise photos: same background, same angle, same crop. Consistency reads as professionalism more than any single good photo.
  5. Import, then walk the site as a customer would: category page, filter, product page, add to basket. Fix what stops you.
  6. Keep the spreadsheet as the source of truth for bulk edits, and re-import rather than editing hundreds of items by hand.

In Ettex Sites, store templates and 70+ sections cover the storefront itself, a live canvas edits it visually, themes control fonts, colours and spacing in one place, forms feed a built-in leads inbox, custom domains connect with certificates issued automatically, and SEO fields with an auto-generated sitemap are part of the builder rather than an add-on. Built-in analytics show visits, referrers and page stats, so you can see which category pages people actually reach. The builder works offline and publishes when you are ready.

Catalogue mistakes that cost sales

  • Categories named after internal departments rather than what the item is.
  • A search box that only matches exact product names, so a typo returns nothing.
  • Variants listed as separate products, splitting reviews, stock and search relevance.
  • Prices without tax clarity, which produce basket abandonment at the last step.
  • No availability signal, so customers find out an item is gone only after they care about it.

Frequently asked

How many categories should a small catalogue have?

Enough that no category holds more than about thirty items and none holds two. For most small shops that is five to twelve top-level categories, one level deep.

What is the difference between a category and a tag?

A product belongs to exactly one category — that is its place in the structure. Tags are cross-cutting labels like "sale" or "waterproof" and a product can carry many.

Should variants be separate products?

No. Group them under one parent so stock, reviews and search relevance stay together, and let the customer pick size or colour on the product page.

How long should product descriptions be?

Long enough to answer what it is, what it fits or suits, and what is in the box. Two short paragraphs beats a page of copy nobody reads.

What should I export from a catalogue?

Everything, as CSV, keyed by SKU. Marketplaces, ad platforms and accounting all want a feed, and they all match on the stable ID.

A good product catalog is boring in the best way: predictable categories, controlled attributes, one ID per product that never changes. Do that and search, filters and feeds come almost for free.

MI
Written by Maria I.

Part of the Ettex team — writing about product, engineering and the future of work.

More posts
Get the best of the Ettex blogProduct news, guides and tips — straight to your inbox, no spam.