> 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/konfiguration.md). # Configuration ## Loading Mode 1. Default Recommendations are loaded while the page is loading. The cache for the sales channel pages is **completely deactivated** for this purpose. It is recommended to [empty the cache daily with a cronjob](https://docs.shopware.com/en/shopware-6-en/configuration/caches-indexes#empty-cache-automatically) to avoid problems with a full cache. Experience shows that the cache will grow by a few gigabytes during the course of the day. 2. Asynchronous Recommendations are loaded via AJAX requests in the background after the page has loaded. With this loading method, the cache remains intact, the visitor sees a loading animation for a few seconds until the recommendations have been loaded. ## Paid Order Status Define the status for paid orders, which are required for some filters. ## Assign Gender to Categories With this setting you can improve the training of the "Narrow down to gender" function. Define your categories for the genders man, woman and child, which are assigned to the products in your shop in the background. If you leave these fields empty, standard search terms such as "Man", "Men", "Male" or "Woman", "Women", "Lady", "Female" etc. will be used to assign the products. --- # 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/konfiguration.md?ask=&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.