Tags
Learn how to import tags from the preset catalog or generate them with AI, and where tags actually change what shoppers see.
Tags are short labels you attach to products to describe a trait rather than a place — "waterproof", "clearance", "vegan".
A product sits at exactly one place in the category tree, but it can carry any number of tags. That is the whole point of them: tags describe the traits the tree does not.
They are not a second navigation system, though. A tag changes what shoppers find, not where they can go.
Adding tags
Tags live at Catalog → Tags. You browse, select the ones you want, and add them.
The page offers a catalog of standard tags in six groups:
Status
Quality
Style
Occasion
Audience
CollectionYou can also describe your store and have an AI provider suggest tags from that context. AI suggestions only appear when a provider is configured.
Either way the flow is the same — the page proposes, you select, and the selected tags are added in bulk.
A tag is stored as its slug alone
Tags have no separate display name and no description field.
The preset catalog shows a friendlier name while you browse, but what your store keeps is the slug. The slug is what search matches and what the storefront shows, so it is worth reading a tag as its slug before you add it.
Where tags change what shoppers see
Two places, both of them behind the scenes.
Search
Storefront search matches a shopper's words against tag names as well as product names, descriptions and categories.
An exact tag match is one of its strongest signals, so a well-chosen tag is close to a direct route to the product.
Related products
Two products sharing a tag score higher in the "you may also like" list than two that share only a category.
A tag is the finer signal of the two — a category says these products are the same kind of thing, a shared tag says they have a trait in common.
Tags do not have their own storefront page
There is no page listing everything with a given tag, and no rule that builds a collection from one. To sell a group of tagged products as a set, add them to a collection.
Tag, category, or collection?
Use a tag for a trait that cuts across the tree, and expect it to pay off in search results and related products rather than in navigation.
Use a category for where the product belongs — a product needs one before it can be published, and it gets a page of its own.
Use a collection when you want to sell the group as a set, because that is the grouping a customer can actually be sent to.
A tag is a signal, not a destination — if you need somewhere to link customers to, you need a collection.