A product count under a Shopify subcategory card can answer a useful question in one glance: “Is there enough here to explore?” But the same number can also create doubt. A card labeled Cast Iron Teapots (3) may feel curated and focused in a specialty tea store, while Summer Sale (2) may look neglected or nearly empty.
The decision is not simply “counts are good” or “counts are bad.” The better question is whether the count helps a shopper make the next navigation decision. This guide focuses on that decision: when Shopify subcategory product counts improve browsing confidence, when they add noise, and how to handle small, large, empty, sold-out, and seasonal collections without turning category navigation into a dashboard.
Quick Answer: Should Shopify Subcategories Show Product Counts?
Show product counts when the number helps customers compare category depth, confirm that a subcategory is worth opening, or distinguish between similar browsing options. Hide counts when the number is volatile, misleading, visually noisy, or likely to make a useful niche category look weak.
A practical default is:
- Show counts for stable category families where shoppers compare breadth.
- Hide counts for fast-changing sale, seasonal, editorial, or campaign collections unless the number has clear decision value.
- Do not use a single global rule without checking how counts behave across different collection types.
Before deciding, make sure the store already has a clear parent-child structure. Product counts cannot repair a weak hierarchy. For stores still designing the category model, start with a clear Shopify collection hierarchy and category tree, then decide whether counts add useful information to that structure.
What Does a Product Count Communicate to a Shopper?
A number beside a subcategory label is a small piece of interface copy, but shoppers can interpret it in several ways:
- Depth: “There are enough products here to browse.”
- Scope: “This subcategory is narrow or broad.”
- Availability: “There appears to be something here right now.”
- Comparison: “One branch has more choice than another.”
- Freshness: “This category may be active, depleted, or neglected.”
The problem is that the count may not actually measure all of those things. A collection can contain products that are sold out, unavailable in the shopper's market, hidden from a sales channel, or included through automated collection rules. Therefore, the UI meaning of “12 products” should be defined before the number is displayed.
This distinction is especially important in stores using automated or seasonal collections. If your catalog relies heavily on rule-based grouping, the broader discussion in Shopify smart collections and breadcrumb SEO is useful because dynamic membership can affect navigation context as well as counts.
The Show-or-Hide Decision Matrix
| Subcategory type | Show count? | Why | Primary risk |
|---|---|---|---|
| Stable catalog category | Usually yes | Helps shoppers compare category depth | Count may become stale if caching or filtering logic differs |
| Small specialist category | Depends | A small count can signal curation, but may also look weak | Shopper interprets “small” as “poor selection” |
| Very large category | Often yes | Confirms breadth and helps comparison | Large numbers can dominate the label visually |
| Seasonal category | Often no | Counts change quickly and may expose depletion | Low late-season counts reduce confidence |
| Sale or campaign collection | Usually no | Campaign intent matters more than assortment size | Volatile counts create noise |
| Empty category | No | “0” is rarely a useful browsing invitation | Creates a dead end |
| Mostly sold-out category | Only with careful logic | Total product count may overstate available choice | Count and actual purchasable inventory disagree |
This matrix is intentionally contextual. It avoids the common mistake of treating product counts as a universal conversion tactic. Counts are navigation metadata; their value depends on whether they reduce uncertainty for the current browsing task.
When Product Counts Help Shopify Subcategory Navigation
1. When customers compare sibling subcategories
Consider a parent collection called Tea Equipment with subcategories such as Teapots, Tea Infusers, Tea Caddies, and Matcha Tools. A shopper who is browsing broadly may benefit from seeing relative assortment size:
Teapots (42) · Tea Infusers (18) · Tea Caddies (11) · Matcha Tools (27)
The counts provide orientation without forcing the shopper to open every category. This works especially well when the categories are siblings in the same level of the tree and the numbers are measured consistently.
For broader guidance on helping customers move from a broad page into narrower branches, see the broad-to-specific Shopify subcategory journey guide.
2. When a large category needs confidence signals
A label such as Outdoor Rugs (128) tells a shopper that the category is substantial. For stores with deep catalogs, the count can reduce uncertainty before the click. It is particularly useful when several subcategories have similar names and the shopper wants to understand where most of the assortment lives.
However, large categories still need a sensible hierarchy. A count of 600 beside one broad collection may simply reveal that the category is too broad. In that case, improve the collection tree before adding more interface metadata. The collection hierarchy SEO priorities guide explains why structural issues should be fixed before smaller navigation details.
3. When counts support a deliberate comparison task
Counts are useful when the shopper is expected to compare category breadth. For example:
- Rings (86)
- Bracelets (31)
- Necklaces (74)
- Earrings (112)
Here, the numbers function as lightweight decision support. They do not tell the shopper which category is “better”; they help set expectations about the amount of choice behind each link.
When Product Counts Distract or Reduce Confidence
1. Small categories where the number looks like a weakness
A specialist collection may be intentionally narrow. Japanese Cast Iron Teapots (4) could represent four carefully selected products, but the number may be interpreted as limited choice.
In these cases, the label, image, collection description, or merchandising context may communicate more value than the count. A small count should be shown only when “small and focused” is consistent with the brand and the shopper's expectation.
2. Seasonal collections that shrink during the campaign
Seasonal categories behave differently from evergreen taxonomy. At launch, Holiday Gifts (84) may look healthy. Near the end of the season, Holiday Gifts (7) may make the collection feel depleted even if those seven items are strong sellers.
Seasonal navigation should therefore have its own policy. The guide to seasonal Shopify collection navigation explains how campaign collections can coexist with more stable category paths without becoming the permanent taxonomy.
3. Sale collections where availability changes too quickly
Sale collections often have volatile membership and inventory. A count can change frequently, and the number may have little relationship to the shopper's actual filterable or purchasable choices. In this case, a strong collection label and clear product grid are usually more useful than a fluctuating number beneath every subcategory card.
4. Mobile layouts where numbers compete with labels
On desktop, a product count can sit quietly below a subcategory title. On mobile, the same count may create wrapping, uneven card heights, or visual competition with the category name.
If subcategories appear in a horizontal slider or compact card grid, test the count as a secondary line rather than appending it to the label. The Shopify subcategory mobile layout guide covers card density and mobile presentation, while the mobile breadcrumb UX guide is useful for keeping the broader navigation layer readable on smaller screens.
Empty Collections: Do Not Turn “0 Products” Into a Navigation Feature
An empty child collection creates a different problem from a small one. Displaying Accessories (0) usually asks the shopper to click into a dead end.
Better options include:
- hide the empty subcategory from the current navigation block;
- keep the collection available elsewhere if it is being prepared for launch;
- replace the card with a meaningful adjacent category;
- show a temporary merchandising message only when there is a real customer reason to visit the empty page.
The important principle is to separate catalog administration state from customer navigation state. A collection may need to exist in Shopify before it deserves a prominent link on a live parent collection page.
Sold-Out Products: Decide What Your Count Actually Counts
A count can be technically correct and still be misleading. Suppose a subcategory contains 18 products, but only five are currently purchasable. Showing “18” may overstate the customer's available choice.
Before exposing a number, define the counting rule:
- all products assigned to the collection;
- products published to the relevant sales channel;
- products currently available for purchase;
- products visible after market or localization rules;
- products remaining after collection-page filters are applied.
There is no universal answer for every store. The critical requirement is consistency: the number should mean the same thing across sibling cards.
Small vs Large Categories: A Better Rule Than a Hard Threshold
It is tempting to create a rule such as “hide counts below 5” or “show counts above 20.” Hard thresholds are easy to implement but can produce strange results. A category with four high-value handmade products may be perfectly healthy, while a category with 40 nearly identical low-stock variants may not offer meaningful breadth.
A better rule uses three questions:
- Does the number help the shopper compare options?
- Is the number stable enough to remain trustworthy?
- Will the number improve confidence rather than expose a merchandising weakness?
If the answer is yes to all three, show the count. If only one is yes, the interface probably does not need it.
Product Count Placement: Label, Secondary Text, or No Count?
| Pattern | Example | Best use |
|---|---|---|
| Inline | Teapots (42) | Compact text lists |
| Secondary line | Teapots 42 products |
Image cards and mobile layouts |
| Count badge | Teapots · 42 | Dense admin-like interfaces; use cautiously in storefront UX |
| No count | Teapots | Editorial, seasonal, luxury, or visually led category navigation |
Do not let a count overpower the category label. Clear category naming remains more important than numeric metadata. For naming decisions, the Shopify breadcrumb label examples guide offers useful principles that also apply to category navigation labels.
A Practical Show/Hide Decision Guide
Use this sequence before enabling counts globally:
- Classify the subcategory: evergreen, specialist, seasonal, sale, campaign, or editorial.
- Define the count meaning: assigned, published, available, or otherwise.
- Check volatility: will the number change so often that it becomes distracting?
- Check confidence effect: will a low number feel curated or weak?
- Check sibling consistency: are all visible subcategories counted by the same rule?
- Check mobile layout: does the number remain secondary to the label?
- Test edge states: empty, sold-out, newly launched, and end-of-season categories.
How Breadcrumbs and Subcategory Counts Should Work Together
Subcategory counts help with the next choice. Breadcrumbs help with orientation. They serve different jobs and should not compete visually.
For example, on a parent page:
Breadcrumb: Home > Tea > Teapots
Child cards: Glass Teapots (18) · Japanese Teapots (12) · Cast Iron Teapots (7)
The breadcrumb explains where the shopper is. The cards explain where the shopper can go next. A good implementation keeps both layers aligned to the same category tree. For deeper guidance on constructing that relationship, see the article on creating and displaying Shopify subcategories on collection pages.
Implementation Options Without Turning This Into an App Pitch
Stores can manage subcategory counts through theme logic, custom development, or an app workflow. The right option depends on how the category tree is maintained and how often the catalog changes.
If the store needs a visual category tree, breadcrumb paths, and subcategory display managed from one structure, Breadcrumbs & Categories is one practical option. For setup details, theme blocks, and configuration behavior, use the implementation documentation rather than duplicating configuration instructions across theme templates.
The architectural goal is more important than the tool choice: category relationships, breadcrumbs, and subcategory cards should not be maintained as three unrelated systems.
SEO, AEO, and GEO: What Product Counts Can and Cannot Do
SEO: Product counts are not a ranking shortcut. Their main value is UX and navigation clarity. The underlying collection hierarchy, crawlable internal links, and page quality matter more. For a broader view, see the guide to Shopify breadcrumbs and internal linking.
AEO: Clear category relationships and concise labels make store structure easier to explain in answer-oriented content. Counts may add factual context, but only when they are accurate and stable.
GEO: Consistent entity relationships matter more than decorating every category with a number. If the site describes a collection as a child of one parent in navigation, another parent in breadcrumbs, and a different context in structured data, the count does not solve that inconsistency.
This is why the store should first establish a coherent hierarchy and then decide whether counts improve the shopper's decision at each category level.
Product Count QA Checklist
- Is the count definition documented?
- Do sibling subcategories use the same counting rule?
- Are empty collections hidden or intentionally handled?
- Are sold-out products included or excluded consistently?
- Have seasonal and sale collections been reviewed separately?
- Does the count stay visually secondary to the category label?
- Does the layout work on narrow mobile screens?
- Does the category tree align with the visible breadcrumb path?
- Have category changes been tested after catalog updates?
For a broader launch process, combine this checklist with a Shopify breadcrumb theme-launch QA checklist so category navigation and breadcrumb behavior are verified together.
Conclusion
Shopify subcategory product counts are useful when they reduce uncertainty. They are distracting when they expose volatility, exaggerate availability, create mobile clutter, or turn a curated niche category into a number that looks weak.
The best policy is not “always show” or “always hide.” Classify the collection, define what the count means, test edge states, and decide whether the number helps the shopper choose the next path. When product counts, subcategory cards, and breadcrumbs all reflect the same category structure, the storefront becomes easier to browse without adding unnecessary noise.
