How to create collections in Shopify

A collection is a group of products with its own page and URL. Products → Collections → Create collection. The only real decision is manual or automated, and it's worth getting right because one of them maintains itself and the other doesn't.

Manual vs automated

Manual — you pick the products by hand. Right for a small curated set that won't change: a founder's picks, a specific campaign edit, a lookbook.

Automated — you write conditions and Shopify keeps the collection current as products are added and changed. Right for essentially everything else.

For any catalogue past a couple of hundred products, use automated collections or accept that the store goes stale. A manual collection is a list somebody has to remember to update, and nobody does.

Conditions that actually work

Automated collections match on product type, vendor, tag, title, price, weight, inventory stock or variant options. You can require all conditions or any.

Useful patterns:

• Category collections: product type is Chairs.
• Attribute collections: tag is outdoor AND product type is Chairs.
• Sale: compare-at price is greater than 0.
• New in: tag is new (added by whoever loads products, removed on a schedule).
• Under £50: price is less than 50.

The conditions are only as good as the data behind them, which is why the tag vocabulary has to be agreed and written down before products are loaded — store structure and navigation. One person typing Blue and another typing blue-ish produces two collections where you wanted one.

Shopify has no nested collections

An important limitation. Collections are flat — there's no parent/child hierarchy natively.

What you do instead: create a collection per level and build the hierarchy in the menu. "Furniture" is a collection; "Chairs" is a collection; the menu nests Chairs under Furniture. Automated conditions do the work — Furniture matches a broad condition, Chairs a narrower one.

That gives customers a hierarchy without Shopify having one, and it keeps each level as a real page that can rank.

Sort order

Each collection has a sort order, and the default is a merchandising decision disguised as a setting.

• Best selling — sensible default for an established catalogue.
• Newest — right where novelty is the draw.
• Manual — good for a small curated collection, unmaintainable for a large one.
• Alphabetical — the theme's default in many cases, and it serves nobody.

Check what your collections are actually sorted by. It's often alphabetical because nobody changed it.

The fields people leave blank

Description. Real text at the top of the collection page. It's a ranking asset and it tells customers what the group is. A collection page with no description is a grid with a title.

Image. Used by themes on collection tiles and by some sharing previews.

SEO title and meta description. Under "Search engine listing". Write them — collection page SEO.

Handle. The URL. Set it deliberately; changing it later needs a redirect.

Which collections deserve to exist

A collection is a page competing for search traffic. Too few and customers can't narrow; too many near-identical ones and they compete with each other.

The rule: create a collection for a grouping people actually search for or browse to. "Outdoor dining chairs" — yes. "Chairs, blue, under £200, in stock" — that's a filter, not a collection, unless there's real demand for that exact phrase.

The distinction and its SEO consequences are covered in collection pages and filtering.

Bulk work

Adding products to collections one at a time is slow. Use conditions instead — that's the whole point — and for tagging, use the bulk editor on the products list to tag many products at once.

A manual collection is a promise to maintain something. An automated one is a rule that maintains itself. Choose the second unless you have a specific reason.