Browse Your Catalog by Tag
Tagging a catalog is easy. Seeing what you tagged is the part that used to be impossible — and it's what makes tags worth trusting before a promotion goes out.
You run a spreadsheet import on a Friday afternoon. Four hundred SKUs, a Tags column, the spring promotion going live Monday. The import comes back clean — applied, nothing skipped — and you close the laptop.
On Monday a rep calls. A product that should be in the promotion isn’t. You open it in the admin, and sure enough: no tag. So you open another. That one’s fine. A third has SPRING-SALE where everything else says SPRING SALE, which is a different tag entirely as far as any system is concerned.
Now you have a question you can’t answer without opening every product in the catalog one at a time: how many did that actually hit?
Tags were only ever half a feature
We shipped product tags a few weeks ago: tag a product from its details page, bulk-apply tags from a two-column spreadsheet, and let reps browse by tag in the Sales App. That covered writing tags and using them.
What it didn’t cover was reading them. The admin could show you the tags on one product. It could not show you the tags in your catalog. There was no page that answered “what tags do we use?” and no way to go from a tag to the products carrying it — which meant there was no way to check your own work.
That’s a strange gap once you notice it. Categories have had this the whole time: a page listing them, a count against each one, click through to see what’s inside. Tags had a write path and no read path.
What we built
Nymble Admin now has a Tags page under Catalog. It lists every distinct tag in your catalog, each with the number of products carrying it. Click a tag and its products appear in a drawer; click any product and you’re on its details page.
It’s the same shape as the Categories page, on purpose. There’s no new interaction to learn — if you’ve drilled into a category to see what’s in it, you already know how this works.
What it changes is the Friday afternoon. After that import you open the Tags page and read the count next to SPRING SALE. If it says 400, you’re done. If it says 397, you know before your reps do. And if there’s a SPRING-SALE sitting one row below with a count of 3, you’ve just found all three in a single glance instead of hunting for them one product at a time.
Why the counts come from the server
There’s an easy version of this feature: fetch the catalog into the browser, loop over it, tally the tags. It works on demo data and quietly falls over on a real catalog — every page load pulling down every product to count strings.
So the count is a grouped query in the API instead. The database flattens each product’s tags, groups them, and returns one row per distinct tag with its total. Opening a tag runs a filtered product query, the same paging any other product list uses. The page asks for a tag list and gets a tag list; it never sees the catalog it was computed from.
That distinction stops mattering the moment it works, which is the point. A tag with 12 products and a tag with 40,000 cost the page the same.
One less thing taken on faith
The useful thing about tags was never the tagging. It was being able to say these products, this promotion, this season and have every surface agree — the admin, the reps’ app, the storefront.
That only holds if the tags are right. Until now, “the tags are right” was something you took on faith after an import, and found out about later through a rep. Now it’s a page you can look at.
Tags shipped as a way to organize your catalog. This is the part that makes them worth trusting.
Product tags and tag browsing are part of Nymble Admin. If you’re running a catalog that needs slicing by season, promotion, or lifecycle, book a demo and we’ll show you the whole flow — spreadsheet in, reps browsing by tag in the field.
