> 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/label-groups/label-groups-condition.md).

# Label groups condition

**Label group condition** helps you manage where the label group can be displayed in the front store. A label group is a container for the labels/badges you add to it: you configure **one shared condition for the whole group**, using the same condition engine as individual Badges & Labels. That condition has **two parts** — Manual and Automate — that work together.

**1. Manual conditions:** control the general display rules for the group:

* **Device**: show on all devices, desktop only, or mobile only.
* **On pages**: choose which pages the group can appear on (product page, collection page, or other specific pages).
* **Show on all images / first image only**: available on certain plans, this controls whether the group displays on every product image or just the first one.
* **Exclude on custom block**: enter a CSS selector to hide the group from a specific block/section.
* **Priority**: set a value from 0–100 to control which group takes precedence when more than one could display on the same product.

<figure><img src="/files/Lzw7Z9nOqHms6qDYcMkp" alt=""><figcaption></figcaption></figure>

**2. Automate conditions:** control which products the group shows on. Choose one of 3 modes:

* **All products** – the label group shows on every product.
* **Specific products** – manually pick the products to show the label group on.
* **Products matching conditions** – build rule-based conditions using fields such as:
  * **Product**: title, type, vendor, variant price, compare price, sale price, option, tag, weight, created date, published date, inventory, metafield
  * **Variant**: variant, variant inventory, variant metafield
  * **Collection**
  * **Customer**: customer, customer tag, order count, total spent, purchase, company name
  * **Page**: index, collection, product, article, blog, cart, search, or multiple URLs
  * **Language**
  * **Country**

<figure><img src="/files/MWvg4F4ETP43FHYU6Zra" alt=""><figcaption></figcaption></figure>

Since the group uses one shared condition, all labels/badges you added to the group will display together whenever that condition is met — there is no separate condition per individual label inside the group.<br>

<figure><img src="/files/VqVYN4eoVVLC7rqtnmrL" alt=""><figcaption></figcaption></figure>

***Choose “any condition” if you have more than 1 condition under Products matching conditions:***

<figure><img src="/files/a3qohnLn4MsaCuGjQwYC" alt=""><figcaption></figcaption></figure>

This is the result in the front store when using this condition:

<figure><img src="/files/i4QOCjGRgsaGkPn5cTVo" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Import, export, duplicate, and bulk-update actions are also available for label groups, the same as for individual badges/labels.
{% endhint %}

{% hint style="success" %}
**Friendly reminder!**

If you do encounter any difficulty while proceeding with these steps, don’t show any hesitation to contact us promptly via the email address [support@samita.io](https://help.samita.io/support@samita.io)

We are always willing to help with all sincerity!
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.samita.io/label-groups/label-groups-condition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.