> ## Documentation Index
> Fetch the complete documentation index at: https://dokumentation.websale.de/llms.txt
> Use this file to discover all available pages before exploring further.

# Display any product

> How to output a single product on any template in WEBSALE V8s using PR-AdvData and PR-LoadData.

Product data is normally only available where the shop has already loaded a product, that is on the product detail view and in product lists. With the `PR-AdvData()` bracket, you fetch a specific product onto any other template, for example a promotional product onto the home page or an article onto an information page.

## Basic principle

Inside the bracket, the specified product counts as the active product. All product data tags therefore behave exactly as they do on the product detail view.

```html theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
{PR-AdvData(Prod-Index)}

   Tags der Produktdaten

{/PR-AdvData(Prod-Index)}
```

As an argument, you pass the product index. It is automatically assigned by the WSPManager or by the connected ERP system.

> [!NOTE]
>
> If no product exists for the given index, the bracket outputs nothing. You therefore need no additional safeguard for deleted or not yet imported products. Conversely, this means: if the area remains empty, check the index first.

The content of the bracket is treated as a single product, not as a list. A `{@PR-Data}` loop is therefore neither necessary nor possible.

Reference: PR-AdvData() 

## Taking the product index from a tag

Instead of a fixed value, you can take the value from another tag. Enclose the tag in `$` signs, and the shop resolves it before the product search.

```html theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
{PR-AdvData($EinTag$)}
   ~PR-Name~
{/PR-AdvData($EinTag$)}
```

> [!WARNING]
>
> In this notation, the resolved value is searched for as a **product number**, not as a product index. Both values are only identical if your ERP system assigns them the same way.

## Load a product via product number or an alternative number

`PR-AdvData()` only knows the product index. If you have the product number or one of the alternative numbers instead, use `PR-LoadData()`. The bracket otherwise works identically, but expects a second argument that specifies the type of the entry.

```html theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}}
{PR-LoadData(4711,1)}
   ~PR-Name~
{/PR-LoadData(4711,1)}
```

| Second argument | Meaning of the first argument |
| - | - |
| empty or `0` | product index |
| `1` | product number |
| `2` to `6` | alternative number 1 to 5 |

Optionally, a third argument follows with the category index. Without this specification, the shop determines the product's category itself.

Here too, all arguments can be taken from other tags via `$` signs.

Reference: PR-LoadData() 

> [!NOTE]
>
> When the product is loaded via a product number or an alternative number, the shop additionally loads the associated dependent variant. You thereby directly get the specific version and not the base product.

## Related topics

* Guide: Displaying the selected product


## Related topics

- [Display a category](https://dokumentation.websale.de/en/v8s/kategorien/kategorie-anzeigen.md)
- [PDF display of the product detail view](https://dokumentation.websale.de/en/v8s/produkte/pdf-anzeige-der-produkt-detailansicht.md)
- [Products of a category](https://dokumentation.websale.de/en/v8s/kategorien/produkte-einer-kategorie.md)
- [Product display](https://dokumentation.websale.de/en/ws-search/integration-in-die-templates-storefront/webcomponents/template-placeholder/produktanzeige.md)
- [Display dependent variants as select lists](https://dokumentation.websale.de/en/v8s/abhaengige-varianten/abhaengige-varianten-als-auswahllisten.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.