> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/theme-settings/product-badges.md).
# Product Badges
Set up Volume product badges: three defaults (Sale, Sold out, Preorder) plus up to four custom badges via a custom.badge metafield with custom colors.
### Default Badges
The theme includes pre-set badges:
* Sale
* Sold out
* Preorder
***
### Custom Badges
You can add and customize up to four custom badges to your products. To enable custom badges, you need to create a product metafield specifically for badges:
1. Open your Shopify admin.
2. Go to **Settings → Custom data → Products**.
3. Click **'Add definition'**.
4. Enter **'Badge'** as the metafield name, resulting in the **custom.badge** 'Namespace and key' (important!).
5. Select the type **'Single line text'** with **'List of values'**.
6. Click **'Save'**.
Once the metafield for badges is created, you can proceed to add specific badges to each product:
1. Open the desired product.
2. Scroll down to the metafields section.
3. Enter the names of your badges into the **'Badge'** metafield.
4. Click **'Save'**.
***
### Remove Sale badge
You can remove the sale badge by adding the following code to your **Custom CSS** section in Theme Settings:
```css
.card__badges-item--sale {
display: none;
}
```
{% hint style="warning" %}
Please note that this code will remove the badge everywhere in the store.
{% endhint %}
If you'd like to remove it from the Collection page exclusively, please go to **Theme Editor → Collection page template → select the Collection page section** and add the code to the **Custom CSS** field.
---
# 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://staylime.com/docs/volume-themes/theme-settings/product-badges.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.
