Introducing the New Collections API (2026-07) — Developer Preview

[ceri_waters]

I would like to raise once again that due to the numbered paging (whereas the React version was “Load More”) you cannot manually sort collections as you can’t drag items between pages.

[BeefyNachos]

Just wanted to bump this.

Due to this, it’s now not possible to sync with a shop via bulk operations. It seems variants in variant collections is the first instance, that I can think of, of a Shopify asset you cannot bulk query.

Is there anything on the roadmap that’ll allow bulk querying of variants on collections as you can with products on collections - as it’s becoming a significant blocker?

[diana_cheptene]

We’re working to improve that. In the meantime, you could us the bulk move (select products > move > set desired position).

[Tronquin]

Not a single part of this collection model update release seems to be working as intended.

We are moving our Shopify functions from Product level inAnyCollection to ProductVariant level as per the migration guide and we are getting this error:

│ Build step "Build Function" failed: Failed to build function. │
│ │
│ Command failed with exit code 1: npm exec -- graphql-code-generator --config package.json │
│ [FAILED] GraphQL Document Validation failed with 1 errors; │
│ [FAILED] Error 0: Cannot query field "inAnyCollection" on type "ProductVariant".

Our functions are on 2026-07 as well as the rest of our app, Shopify CLI is on latest version, our dependencies for functions are too, yet we get this error.

What are we supposed to do in this case?

[Paige-Shopify]

@Tronquin , it’s possible your local schema wasn’t regenerated after updating the Function to 2026-07. Can you try the following CLI command and see if that resolves the issue?
shopify app function schema
If your Function is written in JS/TS I also recommend running:
shopify app function typegen

[BeefyNachos]

The CollectionUpdate mutation made on version 2026-07 for multi-source collection does not work (returns “Collection does not exist”) if an input of type CollectionInput is used but works if an input of type CollectionUpdateInput is used.

Is this intended as the documentation doesn’t mention it.

[Tronquin]

Welcome to the club buddy

Collection returns null via collection(id:), node(id:), and handle search, but its products are queryable

Summary Using a public app’s offline Admin API token, one existing and published collection cannot be read through the Collection object: collection(id:) returns null node(id:) returns null collections(query: "handle:...") returns no results collections(query: "title:...") does not include it However, the collection: Exists in Shopify admin Is published to multiple sales channels Appears on the storefront Returns the expected products through products(query: "collection_id:...") The issue…

[BeefyNachos]

Confused, that doesn’t seem to be the same issue.

[Tronquin]

@Paige-Shopify

shopify app function typegen

I had already ran shopify app function typegen and it did not work

What worked was running shopify app function schema

[BeefyNachos]

@diana_cheptene @Paige-Shopify
Just wanted to bump this.

Introducing the New Collections API (2026-07) — Developer Preview

The CollectionUpdate mutation made on version 2026-07 for multi-source collection does not work (returns “Collection does not exist”) if an input of type CollectionInput is used but works if an input of type CollectionUpdateInput is used. Is this intended as the documentation doesn’t mention it.