A strong category page answers three questions quickly: Am I in the right place? What are my meaningful options? Which product should I inspect next? It does not need a long introduction or a complicated control panel. It needs a specific purpose, a concise orientation, sensible groups, a deliberate product order, and cards that expose the same decision-making facts in the same places.
Design it as a place to choose, rather than a shelf for everything that shares an internal label. You decide what belongs on it and which differences matter; the design makes those differences quick to scan.
Give each category page one selection job
“Candles” is a set. “Candles for small rooms” suggests a decision involving size, scent strength, and burn context. “Desk lighting” suggests a comparison involving footprint, light direction, and controls. The page does not have to put that full phrase in its title, but its content and ordering should serve that job.
Write the purpose down as an internal sentence before you design anything:
Help a shopper choose a [product type] for [situation or need] by comparing [two or three decisive differences].
If the sentence needs several unrelated situations, the page may be trying to do too much. Revisit the underlying category assignment with the guide to organizing products and categories. That guide covers catalog structure. Here, the category already exists and the job is helping someone choose from it.
Check that purpose against the promise in the link, search result, or campaign that brings someone here. If the entry point promises compact desk lamps, the opening choices should make compactness and desk use easy to assess. A broad lighting grid with those products scattered among floor lamps leaves the shopper to reconstruct the selection you promised.
The purpose also keeps decoration in check. A campaign image may suit the brand, but if it pushes the products and their key differences below the first scroll, it’s working against the page.
In Setka, the category’s description is part of the catalog context the store is generated from. A description that states the selection job in shopper-facing words gives the generated page its purpose before you refine anything.
Open with a concise orientation
The introduction should confirm scope and reveal the basis for choosing. Two short sentences are usually enough:
Everyday ceramic mugs in three capacities, from a compact coffee cup to a larger desk mug. Compare size, handle shape, and finish to find the one that fits your routine.
Shoppers learn what’s here and what to compare, with no brand essay or generic definition standing between them and the products. Supporting material can come further down.
Match the help to what shoppers know and what they are choosing for. A newcomer may need a plain explanation of the comparison criteria; someone familiar with the products may want to scan the actual values immediately. A gift buyer can be either. Keep the common facts visible, then offer concise suitability guidance or deeper detail through real product and supporting-content destinations. Do not make every visitor read the beginner explanation before seeing the range.
Use the terms customers use, and don’t invent distinctions to make the introduction sound helpful. Every product claim on the page should come from product data you’ve checked.
Group products only when the grouping changes the decision
Grouping can clarify a mixed category, or it can chop a simple grid into arbitrary shelves. Use it only when the label gives shoppers a real shortcut: by use, form, audience, or another factual difference.
For example, a bag category might use “For the daily commute,” “For short trips,” and “For minimal carry” if the products genuinely support those uses. “Collection one,” “Collection two,” and “Other” expose the merchant’s filing system instead. Before adding a group, ask whether its label helps someone rule products in or out, whether the distinction is factual, and whether every product has an understandable place. If not, keep one grid and use ordering to express priority.
Order the products with an explicit rationale
Shoppers can re-sort a Setka category page, but most will start with the order you give them, and that order reads as a recommendation. Decide what the first row is for.
For a focused range, a practical sequence is often:
- Best orientation product: the item that makes the category easiest to understand.
- Main alternatives: products that show the most important trade-offs.
- More specific choices: products for narrower needs or tastes.
- Exceptions: items that need extra explanation or appeal to a smaller audience.
Treat it as a starting pattern. A launch, a seasonal range, or an entry-price path can justify a different sequence. Whatever the logic, look at the first four to six products together instead of inheriting the order of a spreadsheet: do they show the range, or suggest more of the same? For deeper assortment planning, use e-commerce merchandising for small catalogs.
Use consistent cards to make comparison possible
A category page is a comparison repeated card after card. Make each one cheap to read: image, name, price, and the comparable facts in the same positions and formats every time.
The deciding fact might be capacity, dimensions, material, or intended use. Pick one or two that help at listing level, and don’t squeeze the product page into the card.
Product-card comparison
| Card element | Hard-to-compare version | Selection-friendly version | Why the change helps |
|---|---|---|---|
| Image | Mixed crops and changing subject scale | Shared aspect ratio and comparable product scale | Differences belong to the products, not the photography treatment |
| Name | “The Essential,” “No. 4,” “Classic” | “Essential mug — 250 ml,” “Classic mug — 400 ml” | The name carries a real distinction without becoming a sentence |
| Price | Different positions or hidden until hover | Same visible position on every card | Shoppers can compare without guessing or interacting |
| Key fact | A different claim on every item | The same factual field, such as capacity or material | Repetition creates a usable comparison axis |
| Copy | Three lines on one card, none on another | A consistent short line, or no summary across the set | Card heights and information density remain predictable |
| Decoration | Unsupported “popular” and “best” badges | No badge unless its meaning and evidence are real | The page does not manufacture urgency or proof |
A stable frame is what lets the real differences in image, name, facts, and price stand out. The product-card design guide takes this component further.
Offer subcategory paths only where they help
Some categories benefit from narrower paths. A “Lighting” page might point to “Desk,” “Floor,” and “Portable.” These paths move shoppers from a broad question to a specific one.
Plan them as a simple map:
Lighting
├── Desk lighting — compact, directed light
├── Floor lighting — room-scale ambient or task light
└── Portable lighting — movable, rechargeable use
Each path needs its own purpose and a real destination. Don’t add near-duplicate routes to make the catalog look bigger. Keep labels parallel and coordinate them with the store’s e-commerce navigation design so the category page and header agree.
Setka builds category pages and the shared navigation from your categories and product assignments. Menus range from a few categories to multi-level mega-menus, and a product can sit in several categories, so the store can follow a tree like the one above. You define the groupings; check the generated pages and menu paths together in preview.
An annotated category-page wireframe
| Page zone | Example content | Annotation |
|---|---|---|
| 1. Context | Home / Drinkware / Mugs | Breadcrumbs keep the shopper oriented; Setka stores show them. |
| 2. Title + orientation | Mugs · “Three sizes for espresso, everyday coffee, and long desk sessions.” | Confirm scope and name the main comparison without delaying the products. |
| 3. Optional paths | Espresso · Everyday · Large capacity | Add only when each path represents a useful destination, not a cosmetic subgroup. |
| 4. Opening comparison row | [image] 250 ml · [image] 350 ml · [image] 450 ml | Show representative alternatives early so the range becomes legible. |
| 5. Continued grid | Repeated cards with name, price, capacity, material | Keep fields and visual rhythm stable; let product differences do the work. |
| 6. Supporting help | “How to choose a capacity” | Answer a real remaining question after shoppers have seen the products. |
| 7. Next path | View all drinkware | Provide a logical way onward without competing with the primary selection task. |
Every zone has to earn its place. Shrink paths that overpower the category, move essential help up, and rework an opening row that hides the range.
Design mobile as a scanning sequence
On a narrow screen, category design becomes an order-of-information problem. Fewer products appear at once, long text creates uneven rows, and a large opening image can hide every choice.
Run this mobile pass:
- Keep the title and orientation visible before extended brand content.
- Make optional subcategory paths compact and easy to distinguish from products.
- Use a grid density that preserves readable names, prices, and the chosen key fact.
- Keep image ratios and card heights predictable; never rely on hover for essential information.
- Check long real product names, not tidy placeholder names.
- Scroll with one hand, then open representative products to verify the card promise against the product page.
Don’t fix mobile density by removing what shoppers need to choose. Cut secondary copy first. An image with no visible price or distinguishing fact turns the category into a gallery.
Generate the page with the rest of the store
Category cards have to agree with product data, paths have to agree with navigation, and the visual rhythm has to match the rest of the store. In a page-by-page theme workflow, keeping those in line is the merchant’s job, along with the theme code that connects them.
Setka generates category pages and product-card templates as part of the whole store, from your brief and catalog, so the category shares one direction with the homepage, product pages, navigation, and cart. Breadcrumbs and sorting are built in, and checkout and orders run in the same platform. To refine a category page, open it and describe the change, for example “put the orientation above the banner image and keep the first row of products visible on a phone.” Edit exact wording, such as the orientation sentence, directly. A described change can reach beyond the part you named, so check the whole page in preview on desktop and mobile before you publish. There’s no theme code for you to maintain.
You decide the categories, what sits in each one, and what it should help a shopper choose; Setka builds and runs the pages. Product filters aren’t available yet. They’re coming soon, and if your range needs them for launch, tell us at contact@getsetka.com: requests go straight to the people building Setka.
Rebuild one category around one decision
Pick the category that matters most. Write its selection job, choose the two or three facts shoppers need to compare, and put representative alternatives first. Standardize the cards, test every group label, and scan the result on a real phone.
Come back to it when the range changes. A new size, a discontinued product, or a seasonal push can make yesterday’s orientation and first row misleading, so revise them and check that the facts on the cards still match the product pages.
Generate your store in Setka, then review the category draft against your real products before you publish.