> 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/status.md).
# Status
Set products to Active, Draft or Archived in bulk.
The **Status** field switches products between Shopify's three product statuses. There is no edit method; pick the new status.
Status
| Status | Meaning in Shopify |
| ------------ | ------------------------------------------------------ |
| **Active** | Available on your sales channels. |
| **Draft** | Hidden from all channels; still editable in the admin. |
| **Archived** | Hidden and marked as no longer sold. |
## Common uses
* **Hide a seasonal collection.** Select **Collections**, pick the collection, choose **Draft**, and schedule the revert for the day the season starts. The products become **Active** again automatically.
* **Publish new products at a set time.** Use **Match conditions** with **Status is Draft** and **Created at is after** a date, choose **Active** and **Schedule the edit**.
* **Archive discontinued items.** Use **Match conditions** with **Product tag equals** `discontinued` and choose **Archived**.
Reverting the task restores the previous status of each product.
---
# 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/status.md?ask=&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.
