Hi @diana_cheptene. Is the new Shopify admin Collection UI available for partner development stores? I am still seeing the old interface on my end. Could you let me know when they plan to release the new UI for dev stores? Thank you.
Yes, products are available in collection.product by virtue of them being in a collection, but can products be identified as being in an app-sourced list for a given collection? It would be helpful to expose this relationship in Liquid so that the theme or app embeds can act on it.
Thanks!
Hi @diana_cheptene. Is the new Shopify admin Collection UI available for partner development stores? I am still seeing the old interface on my end. Could you let me know when they plan to release the new UI for dev stores? Thank you.
Also would like to know more about the UI and merchant surfaced settings for this.
Still cannot see it anywhere, or add it as a feature preview on new dev stores.
Trying to create collections with the new API, just shows this:
It’s our responsability as app developers to not use the new API yet. Otherwise we will break collections for merchants and for other apps that haven’t migrated yet. A pretty annoying one as many apps will start breaking once other apps will use the new features 
Apps that havent migrated will start seeing 404 for collections using new features.
We started to rollout the new Collections UI experience to dev shops.
Cool, apps that are not using 2026-07 and the new API will start breaking as users will start playing with collections. @Luke you said it’s not a breaking update and we can stay on 2026-04, look at the facts,…
No need for the snide comments buddy. We’re all a community here 
@Luke I didn’t want to sound “snide”. I just wanted to bring the point as a fact. Sorry if the message didn’t go through as expected. Everyone seems to act like everything is nice and positive and it’s ok. But it’s not ok. We’ve obligations towards merchants and when things will start breaking because we didn’t have enough time to get everything right, we (partners) will be the ones handling the merchants with broken stores, and the communication is not getting better, we’re getting information randomly after people discover it.
This has already be mentioned in messages above but from the Admin API I cannot find a way to query which product variants are included in a collection or to which collections a product variant belongs to. This information is available for products and if product variants can now be included as well there should be a way to query this information.
Merchants need this information from a reporting point of view. Please consider adding this to the API.
Shopify staff is being vague on this cross-compatibility between APIs, I tried a few scenario crossing api version 2026-07 and 2026-04.
If you create a new collection, using 2026-07 and do not use any new feature - it’s still working on 2026-04. For example using the new add to selection alone and dont add filters, will still work on 2026-04.
If you use any new feature, such as using multiple sources, using a variant source, using the new filters - it breaks in 2026-04. You wont even see the collection at all.
I repeat what I said earlier - let’s be responsible for not breaking other apps that haven’t migrated yet. Please be sure to avoid using new features, because another app, or even a custom store development using the api would break until they’ve upgraded to 2026-07. Which has consequences on the store itself.
@diana_cheptene can you please confirm that we can have as many app-ownded sources as necessary. Because when we talked previously you said that there would be a limit of 50 app-owned sources per app. Did you change this since we last talked of it or was it a misunderstanding?
To follow up on previous notes about variants from @Mathieu_Nunez - it seems that even the collectionConditionsSources object has products but I couldn’t find a way to get individual variants included into the source: collectionConditionsSources - GraphQL Admin
On the Storefront API (2026-07), a variant-targeted collection scopes some product fields to the included variants but not others. Querying a collection where exactly one variant (XL) of a product is included:
| Field | Returns | Scoped? |
|---|---|---|
variantsCount.count |
1 |
yes |
variants(first: n) |
only XL | yes |
selectedOrFirstAvailableVariant |
XL | yes |
options.optionValues |
all 7 sizes | no |
encodedVariantExistence |
v1_0-6 (all 7) |
no |
encodedVariantAvailability |
all 7 | no |
The three unscoped fields are the ones you need to build a variant picker, which is what encodedVariantExistence is documented for. A picker built that way offers option values that aren’t in the collection, and if the customer selects one, variantBySelectedOptions returns a variant that isn’t a member. So swatches are not currently scoped for Storefront API consumers, even if they are for Liquid themes.
@diana_cheptene Is scoping options/optionValues and the encodedVariant* fields planned?
Getting quite a few issues with the new UI @diana_cheptene @Liam-Shopify
- This banner is always showing, the refresh button doesn’t work and on refresh the banner doesn’t go away - making the collection unusable.
2. Not sure why I’m getting so many error messages here, not sure what the ‘2’ in ‘2 errors with this collection’ refers to (it still says 2 if I select just one sub-collection source).
I’m assuming this is because this Yellow Variants collection is already a sub-collection, but the error message isn’t very merchant-friendly. Being a bit picky here, but the UI calls the source ‘Collection’ while the banner calls it a ‘sub-collection’, also it’s not clear what a ‘source’ actually is (it hasn’t been used anywhere on the UI until this banner). I don’t think merchants are going to easily understand what this means.
Matter of opinion, but shouldn’t it just be not possible to select a Collection source if this is a subcollection, rather than allowing you to select it but not allowing you to save it?
- When a collection hits the variant limit, we’re seeing the following:
- You add a new variant rule to add a product(s) the collection
- The newly added product(s) appears in the Collection items preview
- You click Save
- The product disappears from the preview and collection. No banner shows.
Just confirming, is that expected behaviour or a bug?
Did you try this one: query variants within a given collection
Please consult our documentation for the most up-to-date information. There are no limits on app-owned sources.
Thanks for flagging. We’re polishing those rough edges, including better error messages.
For variant-level collections, the behaviour is correct, but we are improving messaging in the UI.