Shopify’s new collections model lets merchants build one collection from multiple sources, include individual product variants, reuse another collection as a source, and exclude selected products or groups without rebuilding the underlying rules. Existing collections are converted automatically, but the new flexibility can change which products, variants, prices and filters customers see. Audit every important collection, navigation link, market, app integration and collection template before treating the migration as complete.
This is more than a renamed manual or automated collection. It is a merchandising model in which sources create the candidate set, conditions narrow it, manual additions fill exceptions and exclusions remove unwanted results. Used carefully, it can reduce duplicate collection logic and make size-, color- or material-specific landing pages far more precise.
Last reviewed: August 30, 2026. Shopify is rolling this model out through the admin and the 2026-07 API. Limits and app support can change, so confirm the current options in your own store before a large catalog migration.
What Changed in Shopify Collections?
The old Shopify model encouraged merchants to think in two separate types: manual collections and automated collections. A manual collection contained products selected by a person. An automated collection included products that matched conditions such as vendor, tag, price or product type.
The new model combines these ideas. A collection can start with one or more sources, apply conditions, accept manual additions and contain exclusions. A source can be the store’s products, selected variants, another collection or a compatible app. This means a merchant can express more realistic merchandising logic without copying the same rules across several collections.
| Old mental model | New mental model | Practical effect |
|---|---|---|
| Manual collection | Product or variant sources plus manual additions | Keep curated exceptions without abandoning rules |
| Automated collection | Sources plus conditions | Build a candidate set, then filter it |
| Separate duplicated collections | An existing collection used as a source | Reuse a maintained product group |
| Workarounds with tags | Explicit exclusions | Remove exceptions without changing product data |
| Product-level inclusion | Product- or variant-level inclusion | Merchandise only the relevant size, color or style variants |
Shopify says existing collections are converted automatically and that merchants should not experience a breaking change from the conversion alone. Treat that as a starting point, not a substitute for storefront testing. Theme code, search-and-filter apps, feeds, recommendation tools and custom integrations can make assumptions that the native collection page does not.
Sources, Conditions, Additions and Exclusions
The clearest way to design a new collection is to separate its four building blocks.
1. Sources define what can enter
A source provides the initial pool. Depending on the collection and store configuration, that can include products, product variants, existing collections and compatible app-managed sources. Multiple sources let one collection combine groups that previously required duplicated tagging or manual maintenance.
2. Conditions decide what qualifies
Conditions narrow the candidate pool using product or variant data. Write the intended logic in plain English before configuring it: for example, “products in the Summer Essentials source where the product type is Shirt and the price is below $80.” Then reproduce that logic in Shopify and inspect the resulting items.
3. Manual additions handle exceptions
A collection may need a sponsored product, a new arrival awaiting complete metafield data or a deliberately featured item that does not match the normal rule. Manual additions make that exception visible rather than hiding it inside a misleading tag.
4. Exclusions remove unwanted results
Exclusions are useful for recalled items, products reserved for a different campaign, incompatible variants or merchandise that technically matches a broad rule but should not appear. Document why each exclusion exists. Otherwise a future catalog manager may re-add the item or leave an obsolete exclusion in place.
A practical governance rule is to use product data for durable facts and additions or exclusions for merchandising exceptions. If “organic cotton” is a permanent product attribute, store it as reliable product data. If one organic-cotton shirt must be absent from a weekend campaign, use an exclusion.
How Multi-Source Shopify Collections Work
A multi-source collection combines more than one maintained input. Imagine a retailer with separate collections for Trail Running, Hiking and Waterproof Footwear. A campaign collection called “Wet-Weather Outdoor Shoes” can reuse those groups, apply a waterproof condition and exclude clearance-only items instead of rebuilding the full logic.
Before using multiple sources, decide whether the relationship is effectively OR or AND. Multiple sources normally expand the candidate set: an item can enter from source A or source B. Conditions then narrow that set. Do not assume that adding two sources automatically means a product must belong to both.
A safe configuration sequence
- Name the commercial purpose and customer intent.
- List the source groups that should be eligible.
- Add the smallest necessary set of conditions.
- Review edge cases and duplicated products.
- Add documented manual exceptions.
- Exclude products or groups that must not surface.
- Preview the collection on the storefront, not only in admin.
More sources are not automatically better. A collection that depends on many upstream collections can be difficult to explain and debug. If a merchandiser cannot answer “why is this item here?” within a few minutes, simplify the logic or document the dependency chain.
How Variant-Level Collections Work
Variant-level targeting lets Shopify include particular variants rather than treating every version of a product as equally relevant. This matters when color, size, material, finish or another option defines the collection’s intent.
For example, a product called Classic Linen Shirt may have ten colors. A “Coastal Blues” collection should not imply that the red and black variants belong to the same visual story. Variant-level inclusion can point the collection toward blue variants, supporting more accurate swatches, displayed pricing and product discovery.
Where variant targeting is useful
- color-led campaign and trend collections;
- size-specific availability pages;
- material or finish collections;
- variant-level price ranges;
- regional or compliance-based assortments;
- bundles or campaigns that apply only to selected configurations.
Where it can create customer confusion
A collection page may visually lead with an eligible variant, but the product page can still expose the full product. The theme must preserve the correct selected variant when the shopper clicks through. Test deep links, swatches, quick-add, predictive search and cart drawers. If Shopify adds the wrong size or color, use the troubleshooting steps in our guide to fixing the wrong Shopify variant being added to cart.
Also verify price presentation. A collection card that displays the cheapest product-level price can contradict the price of the eligible variant. If customers see an old or unexpected amount, work through the checks in our Shopify stale-price guide.
How Nested and Reusable Collections Work
Using an existing collection as a source creates a reusable hierarchy of merchandising logic. It is similar to nesting, but it should not be confused with navigation. A parent menu item and a source dependency are separate things. Changing the menu does not change the collection’s items, and changing a source can affect a downstream collection even if the menu remains untouched.
Good use: one maintained foundation
A retailer may maintain a trusted “Full-Price Womenswear” collection. Seasonal pages such as “Autumn Office Edit” and “Weekend Layers” can use that maintained group as a source, then add their own conditions and exclusions. When a product leaves the foundation, dependent collections update without repeating the removal everywhere.
Risk: hidden dependency chains
If Collection C depends on Collection B, which depends on Collection A, an edit to A can change C. Keep a simple dependency register with the source collection, consuming collections, owner and expected effect. Avoid circular or needlessly deep designs, even if the interface prevents some invalid combinations.
Risk: a reusable collection becomes too broad
A source collection should describe a stable business group. “Products we might promote someday” is not stable. “Active full-price footwear available online” is measurable and maintainable. The clearer the foundation, the safer every collection that reuses it.
Current Shopify Collection Limits to Plan Around
Shopify documents different limits for collections that use particular features. At the time of review, a store can have up to:
- 5,000 collections with conditions;
- 100 collections with variants;
- 50 collections that use another collection as a source;
- 5 collections that exclude another collection.
These are design constraints, not targets. Reserve the more limited collection types for cases where they materially improve merchandising. Do not consume a variant-level collection for every ordinary category page if product-level rules already produce the right customer experience.
Before migration, export or document the planned architecture and count how many collections need each capability. Leave headroom for future campaigns, markets and seasonal work.
Migration Checklist for Existing Shopify Stores
Step 1: Inventory important collections
Start with collections linked from primary navigation, paid campaigns, search results, email templates, landing pages and high-traffic organic pages. Record the collection handle, purpose, current logic, template, owner and downstream integrations.
Step 2: Capture a baseline
Save the item count, representative products, sorting order, visible filters and screenshots of key pages. Baselines make silent differences easier to detect after conversion or editing.
Step 3: Identify duplicated logic
Look for several collections that repeat the same vendor, tag or product-type rules. A stable upstream collection may replace that duplication, but do not restructure everything in one release. Migrate a small family first.
Step 4: Clean unreliable product data
Conditions are only as accurate as the catalog. Normalize product types, vendors, tags, option names, metafields, status and availability. Do not compensate for inconsistent data with dozens of exclusions.
Step 5: Test a representative subset
Include products with one variant, many variants, sold-out variants, compare-at prices, subscriptions, bundles and market-specific availability. Check the first page, pagination, sorting and filters.
Step 6: Monitor after release
Watch collection sessions, product clicks, add-to-cart rate, zero-result filters, search terms and support reports. A technically valid collection can still perform poorly because the shopper’s intent is unclear.
SEO, Navigation and Storefront Filters
The new collection model changes membership logic, not the fundamentals of collection-page SEO. Preserve a useful URL where the search intent remains the same. Avoid creating several indexable collections that answer the same query with nearly identical products and copy.
Keep one primary page per intent
A “Blue Linen Shirts” collection can be valuable when shoppers search and filter that way. Separate pages for “Navy Linen Shirts,” “Dark Blue Linen Shirts” and “Midnight Linen Shirts” may compete with one another unless each serves a genuinely distinct demand and assortment.
Write for the resulting assortment
Collection title, description, metadata and internal links should match what the logic actually returns. Do not promise “all sizes in stock” if the collection includes products with only one eligible size. Our Shopify keyword guide explains where to place search terms without forcing them into every element.
Test filters against variant membership
Variant-level collections can support more precise prices and swatches, but theme and filter behavior still need verification. Test combinations that should return products and combinations that should return zero. Confirm that clearing a filter restores the intended collection rather than a stale cached state.
Update navigation deliberately
Creating a collection does not make it discoverable. Add it to the appropriate menu, contextual links and campaign pages. Remove links to obsolete duplicates only after redirects and analytics annotations are ready.
Shopify App and API Compatibility
Shopify introduced app support for the new model through the 2026-07 API. An app that reads only traditional product-level collection membership may not understand multi-source, exclusions or variant-level intent in the way a merchant expects.
Audit apps that manage search, filters, recommendations, feeds, discounts, subscriptions, bundles, translations, inventory, merchandising and analytics. Ask each vendor which API version it uses, whether variant membership is supported and how excluded items are handled.
Remove redundant tooling only after confirming that the native model covers the real workflow. If the store already has overlapping apps, the process in our Shopify app-audit guide can help identify cost, conflict and performance risks.
For custom integrations, test against a development or low-risk collection before updating production logic. Log the API version and collection assumptions in the integration documentation.
Pre-Publish QA Checklist
- Collection title, handle and purpose are documented.
- Every source is intentional and has an owner.
- Condition logic matches the plain-English requirement.
- Manual additions and exclusions have recorded reasons.
- Representative products and edge cases appear correctly.
- Eligible variants remain selected on product pages and in quick-add.
- Prices, compare-at prices and availability are accurate.
- Sorting and storefront filters behave as expected.
- Theme, search and merchandising apps return consistent results.
- Navigation, campaign links and canonical URLs are correct.
- Obsolete URLs have a redirect plan.
- Analytics can identify the new or changed collection.
If you want an independent review of collection logic, variant behavior and storefront UX, SmallDeskApps can help audit the Shopify setup before a high-traffic campaign or catalog migration.
Frequently Asked Questions
Did Shopify remove manual and automated collections?
Shopify replaced the old split with a more flexible model based on sources, conditions, additions and exclusions. Existing collections are automatically converted, but merchants should still test important pages and integrations.
Can one Shopify collection use multiple sources?
Yes. A collection can combine multiple eligible sources and then apply conditions and exclusions to the resulting candidate set.
Can a Shopify collection contain only selected variants?
Yes. Variant-level collections can target relevant versions of a product. Test theme cards, swatches, price display, product links and cart behavior so the eligible variant remains clear.
Can I use another collection as a source?
Yes, within Shopify’s current limits. This can reduce duplicated logic, but it creates a dependency that should be documented and tested.
Will existing collection URLs change automatically?
The automatic conversion is intended not to break existing collections. Editing a title or handle is a separate decision. Preserve established URLs unless a planned information-architecture change justifies a redirect.
Do all Shopify apps support the new collection model?
Do not assume so. Confirm support for the 2026-07 API, multi-source logic, exclusions and variant membership with each critical app or integration vendor.
