> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/en/userguide/library/oepn_sidebar/tap_shop.md).

# Shop Player tab

Add a product banner to activate the Shop Player.

## Add a product banner

{% hint style="info" %}
The Shop Player link becomes active only after you add a product banner.
{% endhint %}

<figure><img src="https://1857767629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo7CC5HKFh1guYnGcyftj%2Fuploads%2F2VcOEu3MFzdct7HL257S%2Ftap_shop-1-en.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1857767629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo7CC5HKFh1guYnGcyftj%2Fuploads%2Fnaar6H1f8bemPhyPnRvH%2Ftap_shop-2-en.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1857767629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo7CC5HKFh1guYnGcyftj%2Fuploads%2Fc8S23CZpKjHrTCnysrPG%2Ftap_shop-3-en.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1857767629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo7CC5HKFh1guYnGcyftj%2Fuploads%2FpwZECBXIaHCtJmw6C3E2%2Ftap_shop-4-en.png?alt=media" alt=""><figcaption></figcaption></figure>

1. In the video list, go to the \[Banners] row and click **\[Add banners]**.
2. The sidebar opens, showing the preview and editor for the Shop Player tab.
3. Enter the product details under **\[Add Banners]**: the link the banner opens, the thumbnail image URL, the product name, and the price (optional). Then click **\[Add]**.
4. The new product banner appears in the list. You can add up to 30 banners.\
   The first product banner in the order is shown as the main product.\
   To change the order of the banners shown on the Shop Player, drag the banner blocks under \[Order of banners].
5. In the sidebar's Shop Player tab, click **\[Save and Update]** to show the new product banner in the preview.

## Change player settings

### Autoplay

{% hint style="danger" %} <mark style="color:red;">**When Autoplay is on, the video plays muted.**</mark>
{% endhint %}

* Autoplay on: the video starts as soon as the page loads, without viewers clicking play. It plays muted.
* Autoplay off: the video plays only when viewers click play, even after the page has loaded.

### Loop

* Loop on: when the video ends, it starts again from the beginning without stopping.
* Loop off: the video stops when it ends. Viewers need to click play to watch it again from the beginning.


---

# 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://support.charlla.io/en/userguide/library/oepn_sidebar/tap_shop.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.
