> 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/avante-themes/theme-settings/product-badges.md).

# Product badges

Set the colors of Sale, Sold out, Pre-order and custom product badges in Avante, and choose whether the Sale badge shows a word or a percentage.

{% hint style="info" %}
**Theme Editor → Theme settings → Product badges**
{% endhint %}

### Badges that sell before customers read a word

A product badge is a silent salesperson. "Sale", "Sold out", "New" — each one changes how a customer sees a product in under a second. Used well, badges create urgency, set expectations, and guide people through your catalog without any extra effort from you.

***

### What you configure here

This panel is about **colors**, not wording. It has four sections — Sale, Sold out, Pre-order and Custom badges — and each of the first three offers a text color and a background color. For the full setup guide, including the metafield behind custom badges, see [**Product badges**](/docs/avante-themes/features-and-advanced-setup/product-badges.md).

{% hint style="warning" %}
**There are no label fields here.** The words "Sale", "Sold out" and "Pre-order" are theme translations, not settings. To reword them, go to **Shopify Admin → Content → Translations** and edit the theme strings, or use the Translate & Adapt app.
{% endhint %}

***

### Badge style (Sale)

The one setting here that changes content rather than color. The Sale badge can show either a word or the actual discount:

| Option         | What the badge shows                                                                 |
| -------------- | ------------------------------------------------------------------------------------ |
| **Text**       | The translated Sale wording — the default                                            |
| **Percentage** | The discount as a rounded number with a minus and a percent sign, for example `-20%` |

The percentage is calculated from the variant's Compare-at price, so it keeps itself up to date as prices change. Discounts under half a percent keep one decimal instead of rounding away to nothing.

Percentages work best when the discounts are deep enough to impress — a `-5%` badge rarely sells, while `-40%` does the selling for you.

***

### Custom badges (Badge 1–4)

Four name-and-color slots. Type a badge name into **Badge 1–4** and the theme paints any badge with that name in the colors you set next to it.

{% hint style="info" %}
**These slots don't create badges and don't limit them.** The badges themselves come from the `custom.badge` metafield on the product or variant, and a product can carry more than four. Anything that doesn't match one of the four names still appears — just in the theme's default dark style.
{% endhint %}

{% hint style="success" %}
**Capitalization doesn't matter.** `New`, `new` and `NEW` all match the same slot — the theme compares the names in lower case. Spelling and spacing still have to match.
{% 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://staylime.com/docs/avante-themes/theme-settings/product-badges.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.