Shopify collection rules are automated conditions that add products or variants to a collection whenever their attributes match what you set. Choose a Products or Variants source, add typed conditions, then pick Match all or Match any. Before you rely on them, turn on inventory tracking for stock rules and activate any metafield for collections.
TL;DR:
- A Products source pulls in the entire product when any variant qualifies; a Variants source includes only qualifying variants, keeping displayed prices and filters accurate.
- For numeric ranges, combine lower and upper bounds with Match all; because operators exclude endpoints, move each threshold slightly to include boundary values.
- A metafield appears as a collection condition only after its definition is created and activated; variant specific matching also requires a linked option.
- Stock conditions require inventory tracking, while each collection can have at most 60 conditions; stores on Starter must upgrade to Basic or higher.
- Exclusions override rules and manual picks, but they apply only to category, tag, type, and vendor; handle other removals through your inclusion logic.
Table of Contents
- How Shopify collections and rule-based sources work
- Supported condition types and operators you can use
- Metafields and advanced condition uses
- Match logic and building numeric ranges
- Step-by-step: create or edit an automated collection with rules
- Practical limits and quotas to plan for
- Troubleshooting checklist: symptoms, quick checks, and fixes
- Best practices and copyable examples
- Why structured product feeds make complex rules easier
- Skip the manual tagging with a collection-ready feed from JewelCloud
- FAQ
- Sources
How Shopify collections and rule-based sources work
A collection in the newer flexible model is built from one or more sources. A source can be Products, Variants, other Collections, or an app. Each source can carry inclusion conditions, manual selections, and exclusions, so you decide where the rules live and what overrides them. Shopify describes this composable model in its collections documentation, where a collection is assembled from conditions, manual picks, exclusions, or even other collections.
The practical change is that the old wall between manual and smart collections is gone. One collection can hold a rule that pulls in every ring under a set price and also include a handful of hand-picked pieces you want to feature. If your store has the new model, previous collections are converted automatically; stores without it keep working with manual and smart collections as before.
If you rely on custom code or apps, pay attention to the API side. The 2026-07 GraphQL Admin API replaces the legacy custom versus smart split with Collection.sources, and the old ruleSet gives way to typed conditions. Sources can mix inclusion, manual selections, and exclusions. Anything that reads or writes the older CollectionRule object will need updating, because the newer API exposes different mutation shapes.
Shopify also recommends automated collections for catalogs that grow, since conditions add or remove products dynamically as product data changes. That is the whole appeal: you set the logic once and the collection maintains itself.
Supported condition types and operators you can use
Think of conditions in three families: product attributes, variant attributes, and metafields.
Product attributes include title, type, vendor, tag, category, and status. Text-based ones typically offer operators such as equals, is not equal to, contains, starts with, and ends with. Shopify’s conditions reference lists what each attribute supports, and the typed inputs in the developer docs show that attributes like productTag, productTitle, productType, productVendor, and productStatus each define their own relation and value shape.
Variant attributes cover price, compare-at price, inventory, and weight. These are the numeric conditions: variantPrice, variantCompareAtPrice, variantInventory, and variantWeight. There are also pricing flags such as isPriceReduced, which is handy for a sale collection that fills itself when a markdown is applied.
Metafield conditions support several types, including boolean, integer, decimal, string, and metaobject references. Which operators you see depends on the type. A boolean gives you a simple true or false, while a decimal behaves like the other numeric conditions.
One constraint is easy to miss: exclusions are not available for every attribute. They apply only to category, tag, type, and vendor. If you want to keep a product out of a collection by some other attribute, you will need to structure your includes so it never matches, or exclude the product directly.
A quick way to plan: write your collection in plain words first (“gold rings under a set price that are in stock”), then map each phrase to an attribute on this list. If a phrase has no matching attribute, that is your cue to create a metafield for it.
Metafields and advanced condition uses
Metafields give you the most precise control, but they need setup before they show up. First create the metafield definition. Then activate it for collections. Only after that will it appear as a condition option. Shopify spells this out in its guide to collections with metafields, and skipping the activation step is the most common reason a metafield seems to be missing.
Variant narrowing adds one more requirement. Say you use a category metafield and want the collection to include only specific variants, such as a ring in size 7 rather than the whole ring product. The metafield has to be connected to the related product option, which Shopify calls a linked option. Without that link, the condition matches the whole product, so every variant of a matching product comes along for the ride.
Two practical constraints to plan around:
- Activation limit. Stores can activate only a limited number of metafield definitions for collections. Decide which attributes truly drive merchandising, such as material, gemstone, and metal finish, and activate those first.
- Deletion risk. Do not delete a metafield definition while collections still use it. Remove it from the conditions first, or those collections can lose their logic.
For jewelry catalogs, this is where structure pays off. A material metafield with a fixed set of values matches cleanly every time. Free-text tags drift: “14k gold,” “14K Gold,” and “yellow gold 14kt” all describe the same thing and will not match one rule. If you are mapping supplier data into these fields, our guide on how to map supplier catalog fields into shoppable sets walks through the approach.
Match logic and building numeric ranges
Match logic controls how multiple conditions combine. Match any includes an item that satisfies at least one condition. Match all requires every condition to be true. Use Match any for broad, themed groupings, like a “Gifts” collection that pulls anything tagged for birthdays or anniversaries. Use Match all when you are narrowing, like gold rings that are also in stock.
Numeric ranges trip people up because Shopify does not offer greater-than-or-equal or less-than-or-equal operators. The documented pattern is to add two conditions, a lower bound and an upper bound, and select Match all. This works for price, weight, and inventory alike.
For example, to build a collection of pieces between two price points, set one condition for price greater than your low value and another for price less than your high value, then choose Match all. If you left it on Match any, nearly everything would qualify, since almost any price is either above the low value or below the high one.
Boundaries need care. Because there is no inclusive operator, Shopify recommends offsetting your values to catch edge cases. To include a price exactly at your upper boundary in a “less than” rule, set the limit slightly above that price. Likewise, to include a lower bound, set the “greater than” value just below it.
Step-by-step: create or edit an automated collection with rules
Here is the admin path from start to finish.
- In your Shopify admin, go to Products > Collections.
- Click Add collection to start fresh, or open an existing collection to edit it.
- Add a name and description, then add a Products or Variants source.
- Click Add condition, choose the attribute, pick an operator, and enter the value.
- Add more conditions as needed, up to the per-collection limit.
- Set Match all or Match any so the conditions combine the way you intend.
- Add exclusions or extra sources if you need them, such as a manual pick or another collection.
- Save, then open the collection on your storefront and confirm the right products appear.
Pro Tip: Test with a deliberately narrow rule first, then loosen it. It is much easier to spot a wrong match in a small collection than in a very large one.
Shopify walks through this same flow, including use-case collections by type, sale, color, and season. If you are on the Starter plan, note that collections are not included, so you will need to upgrade to Basic or higher before any of this is available.
Practical limits and quotas to plan for
Hard limits shape how you design a catalog, so it helps to know them up front. A single collection can have a maximum of 60 selection conditions in total. That sounds generous until you build one giant “everything” collection; split it into focused collections instead.
Store-level caps apply too:
- Up to 5,000 collections that use conditions.
- Up to 50 collections that contain another collection.
- Up to 5 collections that exclude another collection.
- Up to 100 collections that contain manually or automatically added variants.
Plan nesting carefully. Collections-within-collections and exclusion-based collections have the tightest limits, so reserve them for the cases where nothing else works.
Sorting deserves a note as well. Shopify documents several sort options, including best selling, alphabetical, price, date, and manual. When storefront sorting by price, Shopify uses base prices rather than catalog or B2B prices to determine order, so a B2B-specific price list will not change how products rank.
Troubleshooting checklist: symptoms, quick checks, and fixes
When a collection misbehaves, work from the symptom to the likely cause.
- Conditions section is missing. Check whether your store has the new collections model. Feature availability can differ between collections, and a Shopify Community thread shows a real case where some collections display conditions and others do not. Also check whether the collection was created on mobile, where feature parity can lag.
- Inventory conditions do nothing. Confirm inventory tracking is turned on for the products and that the variants actually have inventory values. Shopify notes that inventory-based conditions require tracking to be enabled.
- Metafield is not an option. Confirm the definition exists, then confirm it is activated for collections. Both steps are required.
- Unexpected items appear. Recheck Match all versus Match any first, since a wrong setting is the usual culprit. Then look for manual selections or a second source adding products you did not expect.
- Products you sell are missing. Items that fall under Shopify’s prohibited products and acceptable use policies can affect whether they can be sold, and that in turn affects what shows up in a collection.
Best practices and copyable examples
Start with the data, because rules are only as good as the fields behind them. Favor structured metafields for material, gemstone, carat, and metal finish rather than inconsistent tags. A dropdown-style metafield matches every time; a typo in a tag does not.
A few patterns you can copy:
- Seasonal or promo collection: a dedicated tag plus a price range condition, with Match all.
- Hide out-of-stock items: add a condition for inventory stock greater than 0 and use Match all. Shopify’s guidance on hiding out-of-stock products notes that inventory tracking must be on first.
- Jewelry example: product type equals Ring, AND metafield material equals Gold, AND variant price less than 1000.
For catalogs that span many suppliers, keeping stock accurate across them matters as much as the rules. Our guide to using a master catalog to stop multi-supplier oversells pairs well with inventory-based conditions. Seller-tooling blogs such as SafeBay’s seller tips also show how inventory and listing automation plays out for large catalogs on other channels.
Why structured product feeds make complex rules easier
The weak point of any collection rule is not the rule itself. It is inconsistent data. A “contains” condition on a messy title field breaks the moment a supplier phrases something differently, and an “equals” condition on a metafield only works if every product has that field filled in. This is where I would put my effort first: fix the data pipeline, and the rules mostly take care of themselves.
Structured feeds populate metafields and variant fields the same way every time, which removes most manual tagging. That matters most for multi-supplier catalogs and high-variant categories, where hand-entering material and gemstone values does not scale. For a large jewelry catalog, a feed that standardizes those fields can make collection setup much faster.
— Anthony
Skip the manual tagging with a collection-ready feed from JewelCloud
If rules are only as good as your data, we built our product feed to fix the data first. We structure and standardize jewelry product information, so the fields your collection conditions depend on arrive consistent and ready to use.
Here is what you get from us:
- A structured JewelCloud® Product Feed built for the complexity of jewelry, including multi-variant products.
- Structured product data designed to support consistent catalog information.
- Integrations that keep your catalog current across multiple suppliers.
It suits retailers with many variants, several suppliers, or small teams that want collection-ready data without retyping it. To see how access and setup work, take a look at our Vendor Membership and book a conversation with our team about your catalog.
FAQ
How do I add a collection in Shopify?
In your Shopify admin, go to Products, then Collections, and click Add collection. Name it, add a Products or Variants source, and either pick products manually or add conditions so it fills itself. Save and check the result on your storefront, following the official collection steps.
What is the difference between Match all and Match any?
Match all requires every condition to be true, so it narrows a collection. Match any includes a product that meets at least one condition, so it broadens it. Use Match all when combining a range with other filters, as described in Shopify’s conditions guide.
Why can’t I see my metafield when building a collection rule?
The metafield definition must exist and be activated for collections before it appears as a condition option. To narrow a collection to specific variants, the metafield also has to be linked to the related product option, as explained in Shopify’s metafields for collections guidance.
How do I hide out-of-stock products from a collection?
Turn on inventory tracking, then add a condition for inventory stock greater than 0. When you combine it with other conditions, set the collection to Match all so every rule applies together.
Sources
The source type decides what a match actually pulls in.
A Products source includes the whole product if any one of its variants meets the condition. A necklace with several chain lengths and one priced under your threshold lands in the collection with all of its lengths.
A Variants source includes only the variants that match. The same necklace would appear with just the qualifying length, and the others stay out.
That difference matters on the storefront. Variant-scoped collections make filters, price ranges, and swatches reflect only the variants you included. If a shopper filters a “Rings under a set price” collection by price, a variant-scoped source keeps the displayed range honest, instead of showing a product whose cheapest size qualifies but whose default listing does not.
Manual inclusions can sit alongside either source type. Exclusions, though, always win. If a product or an entire collection is excluded, it stays out even when a rule or a manual pick says otherwise. That makes exclusions a reliable safety net for items you never want shown, like discontinued pieces.
For stores with very large variant counts, it is worth knowing your structural limits before you build variant-scoped collections everywhere. Our piece on Shopify’s variant limit for jewelers covers checks to run first.
- Migrate to the new collections model