> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/dynamic-product-recommendations/rankinggruppe/filter/preisdifferenz.md).

# Price Difference

{% hint style="warning" %}
This filter is a criteria filter. If set up, all other filters are based on the results returned by this filter.
{% endhint %}

{% hint style="info" %}
This filter is product-specific and therefore only works on a product detail page. On other pages, this filter will not provide any results.
{% endhint %}

This filter retrieves all products with a unit price within the price range you have set (applies to the product you are currently viewing).

**Example:** You are looking at a product worth 512€. With a price difference upwards from 25% and a price difference downwards from 5%, only products with a unit price between 486,40€ and 640€ will be displayed.

It is advisable to always configure this filter to effectively upsell and not show your shop visitors products that are a) far too cheap or b) far too expensive.

## Configuration

### Price Difference Up

Set a percentage. Only products that are below the specified price range (of the currently viewed product) will be displayed.

### Price Difference Down

Set a percentage. Only products that are above the specified price range (of the currently viewed product) will be displayed.


---

# 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://docs.codegiganten.de/plugin-documentation/en/apps/dynamic-product-recommendations/rankinggruppe/filter/preisdifferenz.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.