> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/buy-and-install/create-required-metafields/metafields.md).

# Metafields

Metafields are the per-product fields Vélare reads to show content that changes from one product to the next. You create each definition once in your Shopify admin under **Settings > Metafields and metaobjects > Metafields > Products**, then fill in its value on each product that needs it.

### The four metafields in this section <a href="#the-four-metafields" id="the-four-metafields"></a>

| Metafield                                                                                                                 | Namespace and key                                                   | Type                         |
| ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ---------------------------- |
| [**Short Description**](/velare/buy-and-install/create-required-metafields/metafields/short-description.md)               | `custom.short_description`                                          | Single line text - One value |
| [**Use Variants Image Group**](/velare/buy-and-install/create-required-metafields/metafields/use-variants-image-group.md) | `custom.use_variants_image_group`                                   | True or false                |
| [**Custom Product Badge**](/velare/buy-and-install/create-required-metafields/metafields/custom-product-badge.md)         | `custom.custom_product_badge`                                       | Single line text - One value |
| [**Complementary products**](/velare/buy-and-install/create-required-metafields/metafields/complementary-products.md)     | `shopify--discovery--product_recommendation.complementary_products` | List - Product               |

### How to work through them <a href="#how-to-work-through-them" id="how-to-work-through-them"></a>

Follow the table from top to bottom. That is the order used throughout this section. Each page is self-contained: it opens with the exact name, namespace and key, and field type to enter, then shows where the value appears in the product settings and what it looks like on the storefront. Most pages also include a short video.

{% hint style="info" %}
Copy the name, namespace, and key exactly as written on each page, including capitalisation and underscores. Shopify treats a different key as a different metafield, so a typo leaves you with a field the theme is not reading.
{% endhint %}

### Related <a href="#related" id="related"></a>

* [Create Required Metafields](/velare/buy-and-install/create-required-metafields.md): how metafields and metaobjects fit together
* [Metaobjects](/velare/buy-and-install/create-required-metafields/metaobjects.md): the reusable filter definitions to set up after these


---

# 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://uxsmart.gitbook.io/velare/buy-and-install/create-required-metafields/metafields.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.