> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/shopware6/fact-finder-web-components-for-shopware-6/plugin-settings.md).

# Plugin settings

### Advanced settings

Enable **Use Proxy** only when you need to modify FACT-Finder responses. Requests then pass through Shopware's `ProxyController`, adding latency.

Use **Add cart button** to show add-to-cart controls on product lists.

Add redirect mappings as one `query=url` pair per line. The first matching query wins. URLs can be relative or absolute.

Enable **Atlas AI support** to create and persist an Atlas AI user ID. This replaces existing logged-in user ID values.

### Server-side rendering

Enable SSR to render `ff-record-list` markup on search and category pages. This improves crawler visibility.

**Redirect to product detail page for single search result** requires SSR. It applies to SSR search and category results only.

{% hint style="warning" %}
Incorrect images or prices usually indicate incorrect field roles. Update them before troubleshooting templates.
{% endhint %}

### Feature settings

Disable components that require FACT-Finder modules your license does not include.

### Export settings

Choose product properties and custom fields to omit. Variant configuration properties remain exported.

Enable **Export prices for all currencies** to create one price column per currency, such as `Price_DE`. Otherwise, the feed contains only `Price`.

### Upload and import

Configure FTP or SFTP upload with server URL, port, credentials, and root directory. Port `21` is the default.

For SFTP, **Private Key Content** and **Passphrase** are optional.

Configure FACT-Finder dashboard credentials for automatic imports. Select the import types: Suggest, Search, or Recommendation. Save before using **Test Connection**.


---

# 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.fact-finder.com/shopware6/fact-finder-web-components-for-shopware-6/plugin-settings.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.