Collections: curated groups with their own storefront pages

Collections are curated groups of products — "Summer drop", "Under $25", "New arrivals". Each collection becomes its own page on your storefront, rendered in your active theme, and collections themselves get an index page, so shoppers can browse your catalog the way you want it told. ## How to create a collection 1. Go to **Collections** and click **New collection**. 2. Enter a **title**. The **handle** (the URL slug) auto-generates from the title; edit it before the first save if you want something shorter — it becomes the page path. 3. Add a **description**. Themes render it as the intro text on the collection page. 4. Set a **cover image URL** — the wide banner image at the top of the collection page. A preview appears as soon as you paste a valid image link. 5. Pick products in the **product picker**: search or scroll your catalog and toggle each product in. A collection needs at least one product to be worth showing. 6. Set the **sort order** number. Lower numbers appear first on the collections index — use it to put your money-maker collection at the top. 7. Click **Save**. ## Manual grouping, automatic sync Grouping is deliberately manual: you choose what belongs together, which is what keeps curated collections trustworthy. What the platform automates is the bookkeeping — every save keeps each product's collection membership in sync on the product itself, so product pages, search, and the storefront can all list "which collections does this belong to" without you maintaining anything twice. Delete a collection and only the grouping is removed; the products themselves are never touched. ## How collections render on the storefront Every collection gets a real page, not a filtered table: 1. The index lives at /<storeSlug>/collections and lists all your collections in sort order. 2. Each collection lives at /<storeSlug>/collections/<handle> — for example /acme/summer-drop. 3. The active theme renders both pages with its own designs: cover image treatment, product card grid, and typography all come from the theme, and the page carries ItemList and Breadcrumb structured data for search engines automatically. 4. When you preview another theme (see the Themes tutorial), collection pages preview in that theme too, so restyling never surprises you. ## What happens next Link your collections from the homepage via the theme's navigation or banners, and point email campaigns at a collection URL instead of the home page — shoppers who land on a curated page convert better than shoppers who land on everything. New products added to a collection appear on that page immediately on the next view. ## Tips 1. Keep the number of collections in the low double digits. A shopper scanning twelve focused groups buys more than one scanning fifty overlapping ones. 2. Use sort order as merchandising: seasonal collections move to the top while they are relevant, then step down. 3. The cover image is the collection's first impression — wide, well-lit photos beat collages. ## FAQ **Can a product be in multiple collections?** Yes. Membership is tracked per product, and a product can carry several collections at once — "Summer drop" and "Under $25" can overlap freely. **Does deleting a collection delete its products?** Never. The confirmation you see says exactly that: only the grouping is removed, and products stay in your catalog. **Is there an auto-rule engine that adds products by conditions?** No. Grouping is manual by design, and the platform handles the syncing of membership everywhere else automatically. For rule-like behavior — "show everything on sale" — the Discounts system plus a well-named collection updated from the Spreadsheet Manager covers most needs.