> 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-card.md).

# Product Card

Global Volume product card settings: variant price updates on swatch click, pills for variants and linked products, color labels, sizes display, and media filtering.

### General Settings

#### Update Variant Price and Badge

When this setting is enabled, clicking on **Color swatch pills** displayed in the product card content will update:

* Badges
* Price
* Size (if displayed)

A linked-product swatch opens the other product. It does not change the price, the badge, or the size on this card. **Update variant price and badge** runs when the shopper selects a variant of this product.

#### Variant Options

* **Pills**\
  The **Pills: Variants / Linked Products / Both** setting allows you to configure how **Color pills** are displayed.
* **Color labels**\
  List the option names your store uses for colour, separated by commas — for example `Color, Shade`. The match is on the **whole name** and ignores case: `Color` matches `color`, but it does not match `Color family`. Once a name is on the list, the card treats it as the colour option, so options called **Shade**, **Finish** or **Farbe** get swatches too. Leave the field empty and the card falls back to the older rule, where the option name has to contain **Color** or **Colour**.
* **Available Sizes**\
  To display the available sizes for a variant within the product card content, fill in the **Size label** field with the option name that represents size.

***

### Media Settings

Enable **Display only media related to the chosen variant** to display only images of the selected variant in the product card.

{% hint style="warning" %}
**Important:** Additional setup is required — see [Display Only Media Related to the Chosen Variant](https://staylime.com/docs/volume-themes/collections-and-products/product-page/display-only-media-related-to-the-chosen-variant.md).
{% endhint %}

While that checkbox is on, a second one appears directly below it: **Show also general product media**. On product cards it is **off by default**. General media means any file whose alt text has no option value in parentheses. With the checkbox on, those files stay on the card next to the media tagged for the selected colour; with it off, the card shows only the media tagged for that colour, plus the image attached to the variant itself — that one stays on the card either way.

Below, you can configure the **Media ratio** and **Focal point** for product media.

If your product images have different aspect ratios and you want them to be fully visible without cropping, enable **Fit media inside container** and adjust the padding using the **Container inner spacing** range.

You can also set a **placeholder** for products without images.

***

### Product Content Styles

In addition to the default **style** for product card content, an additional **small** style has been added.

In some sections, such as **Card drawer**, product cards are set to **small** by default. However, in most cases, you can choose the display style using the **Content style: Regular / Small** setting in the section settings under the **Product card** heading.


---

# 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-card.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.
