Update Shopify collection apps before 2026-07 hides new collections

Shopify has introduced a new 2026-07 Collections API model for the GraphQL Admin API. Confidence level: confirmed. The important operational detail is that older API versions can filter out collections that use new source-based features, so collection apps, merchandising tools, and custom integrations should migrate before merchants rely on the new model.

Caption: Shopify developer changelog social image. Source: Shopify.

What changed

Shopify's 2026-07 release replaces a collection's single legacy ruleSet shape with one or more CollectionSource objects. Sources can include typed product or variant conditions, manual selections, exclusion conditions, and sub-collections. Shopify Functions also gain variant-level collection membership fields on ProductVariant.

The migration warning is direct: in API version 2026-07 and later, the new collections are returned through collection queries. In earlier versions, collections using features the legacy shape cannot represent may be filtered out. Deprecated fields remain queryable in 2026-07 so developers can migrate incrementally.

Key takeaways

• Shopify is moving collections from a legacy rule shape to composable sources.
• Apps reading Collection.ruleSet should add Collection.sources.
• Apps writing collectionCreate(input:) or collectionUpdate(input:) should move to the new collection argument.
• Shopify Functions can now check variant-level membership with inAnyCollection and inCollections.
• Older API versions may not see collections that use the new source model.

Availability and access

The change is tied to Shopify API version 2026-07. Shopify says deprecated members remain queryable in that version, which gives developers room to migrate without a hard cutover on day one. The safe move is to update read paths first, then write paths, then Function logic where variant-level membership matters.

For commerce teams, this is not just a developer cleanup. Collection logic affects navigation, merchandising, discounts, bundles, storefront filters, and campaign pages. If an integration misses collections, the business symptom may look like bad merchandising data rather than an API-version problem.

Practical LinkLoot angle

Treat this as a pre-launch audit for every app that reads or writes Shopify collections. The most useful check is small: list collection queries, identify any ruleSet usage, add sources, then test a collection with multiple sources and variant targeting. That catches the failure mode before merchants create collections your app cannot see.

For broader store automation work, connect this to the LinkLoot guide on AI workflow automation: use agents to inventory GraphQL queries and generate migration notes, but keep schema changes and production rollout behind normal code review.

What to verify before you act

• Search your app code for Collection.ruleSet, collectionCreate(input:), and collectionUpdate(input:).
• Move test shops to API version 2026-07 and compare collection query results with older versions.
• Create test collections with multiple sources, exclusions, sub-collections, and variant targeting.
• Confirm Shopify Functions use product-level or variant-level collection membership intentionally.
• Update docs and support scripts so merchandising teams know which collection patterns your app supports.

Source check

Confirmed by: Shopify's developer changelog entry for the new Collection model and APIs, plus Shopify's changelog index.

Early signal / context: Shopify's developer community preview explains how the model changes what developers can build, including variant-accurate storefronts, self-maintaining collections, and nested navigation.