Some collections show "conditions" section and some don't

[davidculbertson]

Hi Community,

I'm working on a website for a client and adding new collections. I've discovered that for some of the collections that I am adding, the backend page shows "conditions" and "products" but some collections only show "products." I really like the speed of rollout with the "conditions" section. Why would it sometimes show and sometimes not? The same default template is being used for all of the collections.

- David

[KevinMorris]

Hi David,

The reason you're seeing the "conditions" section for some collections but not others is likely due to the type of collection setup. In many platforms, collections can either be automated (using conditions to automatically pull in products) or manual (where products are added individually). If a collection is set to "manual," the "conditions" option won’t appear, as the collection isn't dynamically generated based on specific criteria.

Since you mentioned that you're using the same template, you could change the collection type to "automated" for those that don't have the "conditions" section. This way, you’ll have a consistent setup across all collections, and the rollout speed should be faster.

Let me know if that helps!

[davidculbertson]

I did not explain myself properly. It took me a couple of tries before I discovered what's happening: When I create a new collection, enter some text (like description) and then press "save," the automated option disappears. Watch this Loom to see this happening. Once I've hit save before doing anything with the automation section, that section vanishes.

https://www.loom.com/share/23993105587240a7aab79d9450e90de8?sid=f5d3ecee-5b64-4062-81c4-d1865a1b5954

[tim]

Because you need to make this decision from the start whether collection will be manual or auto.

In your loom you've simply created manual collection.

Just make a type selection before hitting save.

If you change your mind, you need to remove and recreate collection.

[davidculbertson]

Thanks, Tim, but this seems like a bug. Oh well, such is life.