> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/prism/catalog/collections.md).

# Collections

{% hint style="warning" %}
The collections sync feature is not enabled by default. If you plan to use it with a Merchant, you can use [this endpoint](/api-reference/merchants/configuration/toggle-merchant-configuration-global-feature-flag.md) to enable collection syncs for that Merchant.
{% endhint %}

Offer collections refer to curated groups or sets of offers that share common characteristics, themes, or purposes. Merchants often create offer collections to enhance the shopping experience for customers and to organize their inventory more effectively. These collections can be based on various criteria, such as product type, seasonality, trends, or specific themes.

Each `Collection` in Violet has a unique Collection ID, which allows for easy identification of individual collections. A `Collection` also has an `ExternalID`, which is the ID assigned by the e-commerce platform.

You can interact with our `Collection` model using our [Catalog APIs](/api-reference/catalog/collections/get-collection-by-id.md).

### Types

There are 2 types of collections:

#### CUSTOM

Manually curated by merchants. The merchant needs to select each offer inside the collection.

#### AUTOMATED

Automatically curated by the platform given a set of rules. The platform is responsible for selecting the offers inside the collection. Eg.: Offers that contain blue in the title.

### Supported Platforms

* Shopify

### Syncing Collections

Once a store is connected and collection sync is enabled, Violet will sync with the Merchant’s collections on a daily basis. This frequency can be adjusted as needed, by request.


---

# 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.violet.io/prism/catalog/collections.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.