> For the complete documentation index, see [llms.txt](https://docs.themeware.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themeware.design/additional-features/extensions/product-short-description.md).

# Product short description

The product short description is managed via a custom field in the corresponding product.

You can choose via the theme configuration whether the content should be displayed on category and/or product pages.

<div><figure><img src="/files/tgNbPEEvS3bfZi84QhY9" alt=""><figcaption><p>ThemeWare® "Product short description" (Categories)</p></figcaption></figure> <figure><img src="/files/RxMzOZzgcTCtPyKmQoLA" alt=""><figcaption><p>ThemeWare® "Product short description" (Produkt pages / Buybox)</p></figcaption></figure></div>

{% hint style="info" %}
**Note**: A description in categories is only available in listing CMS elements with the "Standard" layout type! This also applies to the ThemeWare® short description.
{% endhint %}

***

## Configuration

### **Theme configuration**

#### **Categories**

1. Go to the tab "**Category pages**"
2. Expand the block "**Product box (Layout type "Standard")**"
3. Scroll to the section "**Basic configuration**"
4. Enable the configuration "**Show short description**"
5. Save your changes after editing

#### **Product pages**

1. Go to the tab "**Product pages**"
2. Expand the block "**Buybox**"
3. Scroll to the section "**Basic configuration**"
4. Enable the configuration "**Show short description**"
5. Save your changes after editing

### **Content**

1. Switch via the main navigation to the "**Product managment**" (1) (2) ("Catalogues" => "Products")
2. Choose the product you want to edit (3)
3. Switch to the tab "**Specifications**"
4. Scroll to the section "**Custom fields**" (4)
5. Select the custom field set of your theme (5)
6. Enter the desired text in the custom field "**Short description**" (6)
7. Save your changes (7)

<div><figure><img src="/files/0nbIbh7zxQhKMvatkBDA" alt=""><figcaption><p>Shopware 6 product managment</p></figcaption></figure> <figure><img src="/files/6KYXVVX22h4D16QKpOyO" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note**: You can find more information about the corresponding custom field in the article [Short description](/additional-features/custom-fields/products/general/short-description.md).
{% endhint %}

{% hint style="success" %}
**Tip**: If a change does not affect the storefront, just clear the Shopware cache: [Clearing / warming up the Shopware cache](https://knowledge.themeware.design/knowledge-base/tutorials/miscellaneous/clearing-the-shopware-cache)
{% endhint %}

***

## Summary

#### Theme configuration

* Tab "Category pages" => Block "Product box (Layout type "Standard")"
* Tab "Product pages" => Block "Buybox"

#### Custom field

* [Short description](/additional-features/custom-fields/products/general/short-description.md)


---

# 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.themeware.design/additional-features/extensions/product-short-description.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.