Shopify Collections Gets Its Biggest Redesign Yet: Merchandising Turns from 'Lists' into an 'Operations System'

Source: Shopify Enterprise Blog

Shopify Collections Is No Longer Just Product Grouping

In July 2026, Shopify shipped a major upgrade to Collections.

According to “Collections now support multi-source and variants”, published on the Shopify Changelog on July 16, 2026, Collections now support multiple sources, variant-level collections, and nesting and reuse of collections, and can be used in more business flows such as discounts and taxes.

This means Collections—previously playing mainly the role of a “product list”—are being upgraded into a piece of operational infrastructure that works much more like a “merchandising rule engine.”

For Shopify merchants, DTC operators, cross-border service providers, and developers, this change is far more than a few new buttons in the admin: how products are organized, how marketing is configured, and how apps stay compatible will all need to adjust.

Collections in the Past: Automated Rules or Manual Picks

Under Shopify’s traditional collection system, merchants typically created a Collection in two ways: automatically, based on conditions, or by manually picking products. The former suits rules on tags, prices, titles, and inventory; the latter suits curated pages, campaign pages, and hand-picked scenarios.

That model was good enough for basic merchandising, but more complex operational scenarios kept hitting its limits:

• A campaign collection needed to combine multiple product rules at once
• Some products matched the conditions but had to be excluded
• You wanted to show only a specific color or size variant, not the whole product
• You wanted an existing collection to become part of another collection
• Storefront display, discounts, and taxes used different scopes, so operations had to maintain them repeatedly

In the past these problems were usually solved by duplicating collections, adding extra tags, manual maintenance, or third-party apps. The new Collections model tries to pull these capabilities back into Shopify’s native system.

New Capability 1: One Collection Can Have Multiple Sources

Source: Shopify Enterprise Blog

The new Collections support multiple sources. Merchants can combine several source types inside a single Collection: automated conditions, manually selected products, exclusion conditions, other Collections, and sources coming from apps.

The operational implication is direct: a collection no longer maps to one simple rule—it can carry a far more complex product strategy.

For example, a “Summer Sale” collection can include products tagged summer, key new arrivals added manually, products pulled in from another “high-margin products” collection, and at the same time exclude items that are out of stock in some sizes or not part of the campaign. Configurations like this used to be split across multiple collections or tag systems; now more of those rule combinations can be done at the Collection level.

New Capability 2: Variant-Level Collections

Source: Shopify Enterprise Blog

The other key change is variant-level collections. Shopify now lets you build collections around specific variants—say, a size, a color, or a specification—instead of only placing whole products into collections.

This matters a lot for apparel, footwear, beauty, and consumer-electronics accessories.

Take a T-shirt that comes in black, white, and gray. In the past, if you only wanted the black version in a “black outfits” feature page, the storefront would still display it at the product level, and operations had to work around it with theme logic, tags, or apps.

With variant-level collections, a collection can be built directly around a particular variant. Shopify’s official notes say these variants appear on collection pages, in filters, and across the supported sales channels, including Online Store and POS. The granularity of merchandising thus moves from “product level” down to “SKU / variant level.”

New Capability 3: Collections Can Become Building Blocks

The new Collections let one Collection serve as a source for another. That gives collections a “building block” quality:

• “New arrivals” is a base collection
• “High-margin products” is a base collection
• “Summer highlights” can reference both, then add extra rules on top
• When the base collections change, the upper-level collection updates along with them

For stores with large SKU counts this is more reliable than copying product lists. Operations can accumulate base collections and reuse them across campaigns, channels, regions, and seasons.

It will also change how service providers design product architecture for merchants. Collections are no longer just part of storefront navigation; they can become reusable units of product strategy.

New Capability 4: The Same Collection Can Feed Discounts, Taxes, and Other Flows

Shopify notes that the new Collections can be reused in supported business workflows, such as discounts and taxes, including variant-level collections.

This is especially relevant for cross-border stores. In the past, storefront display, discount rules, and tax rules were often maintained with different conditions. Operations teams had to define product scopes in multiple places, and the scopes easily drifted apart:

• The page showed product scope A
• The discount rule covered product scope B
• The tax or compliance rule used product scope C

Once Collections become reusable business objects, the same collection logic can support multiple flows, cutting duplicated configuration and reducing the risk of rule mismatches at campaign launch.

Admin Experience: From List Management to Visual Merchandising

The update also includes a redesigned collections admin UI. The official list of changes includes a visual grid, drag-to-reorder, bulk moves, list view, and control over the customer-facing sort order.

In other words, operators can drag to reorder products in a visual grid, move products in bulk, keep the list view for details, and control the ordering customers see on the collection page.

The product order on a Collections page is often not just “by date” or “by sales.” Operators adjust the first screen based on inventory, margins, launch cadence, ad spend, and conversion rates. Visual sorting lowers the cost of that work.

Shopify also says Sidekick supports creating and updating Collections, in both the admin and on mobile. That means some collection setup may eventually be done in natural language—for example, asking Sidekick to create a campaign collection or adjust its rules.

Impact on Merchants: Product Operations Get More Centralized

For Shopify merchants, the main value of this upgrade is fewer detours. Scenarios that used to require third-party apps, complicated tag systems, or duplicated collection maintenance can now be handled more often inside native Collections.

Operational scenarios likely to be affected include:

• Campaign feature pages
• New arrivals, best sellers, and clearance collections
• Features around specific colors, sizes, or specifications
• BFCM, holiday sales, and seasonal promotions
• Unifying product scope across POS and Online Store
• Product scoping inside discount, tax, and compliance rules

Merchants should revisit their existing Collections architecture: which collections are only storefront navigation, which ones carry campaign rules, and which ones can be abstracted into reusable base modules.

If a store has few SKUs, the short-term impact may be limited; if it has a large SKU count, multiple markets, and multiple sales channels, Collections design becomes significantly more important.

Impact on Operations Teams: Treat Collections as Rule Assets

Stronger Collections also bring new management requirements. A collection may now consist of multiple sources, multiple conditions, exclusion rules, and sub-collections. It carries more meaning than before—and needs naming conventions and maintenance discipline to match.

1. Set Collection Naming Conventions

Distinguish storefront navigation collections, campaign collections, discount collections, tax or rule collections, and base reusable collections. Once Collections feed more business flows, messy naming directly raises the risk of misoperations.

2. Control Nesting Depth

Collections can reference other collections, but that doesn’t mean nesting without limits. Deep dependency chains make it hard to tell why a product entered or left a collection. When service providers design solutions, they need to balance reusability against explainability.

3. Document What Key Collections Are For

If a Collection is used simultaneously on a storefront page, in a discount rule, and in a tax rule, the team needs to be clear about its business meaning. Otherwise, changing its conditions later can ripple into several flows.

Impact on Developers: The GraphQL Admin API Model Has Changed

The developer-side changes are more concrete. “New Collection model and APIs now available”, published on the Shopify developer changelog on June 17, 2026, states that in the 2026-07 GraphQL Admin API, Collections use a multi-source model that replaces the previous single ruleSet model.

The key new field is Collection.sources. It returns one or more CollectionSource objects backing that Collection.

Two concrete types currently implement the new CollectionSource interface: CollectionConditionsSource and CollectionSubCollectionsSource. CollectionConditionsSource can include products through typed inclusion conditions and manual selections, and exclude products through exclusion conditions.

Every source must specify a target: PRODUCTS or VARIANTS. Condition matching is controlled by CollectionConditionMatchType: ANY means any condition suffices, ALL means all conditions must match.

This model is closer to a composable rule structure than the old ruleSet, and it can express things the legacy shape couldn’t: multiple sources, exclusion conditions, sub-collections, and shareable sources.

collectionCreate / collectionUpdate Need Migration Too

In the 2026-07 API, collectionCreate and collectionUpdate accept the new input. The Shopify developer changelog notes that collectionCreate supports a new collection argument mapped to CollectionCreateInput, and collectionUpdate supports a new collection argument mapped to CollectionUpdateInput.

CollectionUpdateInput provides sourcesToCreate, sourcesToUpdate, and sourcesToDelete, so developers can update sources incrementally instead of replacing the entire collection definition.

The old collectionCreate(input:) and collectionUpdate(input:) are marked deprecated but still work in 2026-07, giving developers room for a gradual migration. If both the old input and the new collection argument are passed, the new collection argument takes precedence.

Older API Versions Won’t See Some New Collections

This deserves special attention from app developers. Shopify states explicitly: in API version 2026-07 and later, collections using the new sources model are returned through collections queries, collection(id:) lookups, and any other field that returns a collection.

But in earlier API versions, collections using the new capabilities are filtered out, because the old ruleSet structure cannot represent them.

That means if an app is still pinned to an older API version, a real risk appears: the merchant has already created new-model Collections in the admin, but the app can’t query them or manage them correctly. For apps that depend on Collections, this goes beyond a field upgrade—it directly affects data visibility.

Shopify Functions Adds Variant-Level Collection Checks

The developer changelog also mentions that the ProductVariant type in Shopify Functions gains inAnyCollection(ids: [ID!]!) and inCollections(ids: [ID!]!) fields, used to check variant-level collection membership.

The existing Product.inAnyCollection and Product.inCollections remain for product-level checks. The difference: a variant counts as a member of a variant-level collection only when the variant itself has been included in it.

This has potential impact on discount, pricing, tax, shipping, and validation Functions. Developers must be clear whether a rule checks a product or a variant, and avoid applying product-level membership to variant-level scenarios.

Impact on Apps and Service Providers: Check Collection Compatibility Now

If an app touches any of the following, it needs a 2026-07 API compatibility check as soon as possible:

• Reading Collections
• Creating or updating Collections
• Building discounts, recommendations, filtering, or sync on top of Collections
• Adding or removing products from collections
• Reading Collection.ruleSet
• Writing input.ruleSet
• Checking collection membership inside Functions

Migration priorities: move from Collection.ruleSet to Collection.sources; move from the old collectionCreate(input:) / collectionUpdate(input:) to the new collectionCreate(collection:) / collectionUpdate(collection:); support both PRODUCTS and VARIANTS targets; support ANY / ALL matching; handle CollectionConditionsSource and CollectionSubCollectionsSource; and detect the cases where older API versions filter these collections out of query results.

For cross-border service providers this is also an upgrade of delivery standards. When building Shopify stores for merchants going forward, Collections design should be part of the product operations architecture, not just menu and page configuration.

Existing Collections Don’t Need to Be Rebuilt

Shopify’s notes also answer the compatibility question merchants care about: existing collections keep working and are automatically updated to the new admin experience—no need to delete or recreate anything.

The change introduces no breaking changes for existing collections. However, if a store uses third-party or custom apps that interact with Collections, Shopify recommends having the developers update to API version 2026-07 to support the new capabilities.

The Core of This Redesign

The Collections upgrade can be understood on three levels.

First, richer expression of product scope. Collections are no longer limited to a single automated rule or a manual product list; they can combine multiple sources, exclusion conditions, sub-collections, and app sources.

Second, finer merchandising granularity. Variant-level collections let operations organize products around colors, sizes, and specifications.

Third, Collections become reusable business rule objects. The same collection can drive storefront display as well as discounts, taxes, and other flows, reducing duplicated maintenance in multiple places.

For merchants, this is an operational efficiency gain; for developers, an API model migration; for service providers, a change in how store product architecture gets designed.

Shopify Collections used to be mostly a product-grouping tool. Now it is taking on the role of a connective layer between merchandising, campaign rules, and reusable business flows.

Sources

• Shopify Enterprise Blog: “Introducing a brand new Collections experience”, 2026; Shopify Changelog: “Collections now support multi-source and variants”, 2026-07-16.
• Shopify developer changelog: “New Collection model and APIs now available”, 2026-06-17.