Feature request: ability to transform a smart collection to a manual collection

Hello,

Context

we have an app that manages which products go in a given collection. The app uses manual collection and will add and remove products based on some rules.

We also allow users to reuse their existing manual collections instead of forcing them to create new ones. This avoids generating a new collection ID, which could break existing references (for example in metafields, themes, or other integrations). While this approach is somewhat hacky, it works well in practice (ideally we’d like having a “app-managed” collection that can’t be edited manually and that is not a smart collection either).

Problem

We are seeing an increasing number of users who want to reuse their existing smart collections with our app.

Currently, the only way to convert a smart collection into a manual collection is to delete and recreate it. This generates a new collection ID and can break existing references and configurations tied to the original collection

Feature Request

We would like to know whether it would be possible to support converting a smart collection into a manual collection without changing its ID.

Is this something that could potentially be supported in the GraphQL API in the future?

Thank you

Thanks for the feature request @Soufiane_Ghzal! This has been raised internally before and there’s existing feedback on record for the ability to toggle between smart/manual on an existing collection without changing its ID. I’ll add your use case to that feedback. No ETA on if or when something like this might land, but it’s definitely on the radar.

1 Like