> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/field-guides/collections-and-sales-channels.md).

# Collections and sales channels

Add products to or remove them from collections, and publish or unpublish them on sales channels.

## Collections

The **Collections** field has one edit method, **Leave and join collections**, with two pickers:

* **Join collections**: products will be added to these collections.
* **Leave collections**: products will be removed from these collections.

Click **Browser** next to either box to open Shopify's collection picker. Fill one box or both.

{% hint style="warning" %}
Only **manual** collections can be joined or left. Membership of automated collections is decided by their conditions in Shopify, so the task cannot change it.
{% endhint %}

Reverting the task removes the products from the collections they joined and adds them back to the collections they left.

## Sales channels

The **Sales channels** field has one edit method, **Publish and unpublish sales channels**, with two pickers:

* **Publish to**: products will be published on these sales channels.
* **Unpublish from**: products will be removed from these sales channels.

Click **Select sales channels** to pick from the channels installed in your store, for example Online Store, Shop or Point of Sale.

Reverting the task restores the previous publication state on the channels it changed.

{% hint style="info" %}
Publishing to a channel does not change the product status. A **Draft** product stays hidden until its status is **Active**. See [Status](/bulk-price-editor-sami/field-guides/status.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.samita.io/bulk-price-editor-sami/field-guides/collections-and-sales-channels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
