> 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/export-feeds.md).

# Export feeds

Export product, CMS, brand, and category feeds from the CLI or administration panel. Define additional entity types through `factfinder.data_export.entity_type_map` in `services.xml`.

### Use the CLI

Start an interactive export:

```bash
php [SHOPWARE_ROOT]/bin/console factfinder:data:export
```

Use non-interactive mode with a sales channel and optional language:

```bash
php [SHOPWARE_ROOT]/bin/console factfinder:data:export -n SALES_CHANNEL_ID LANGUAGE_ID
```

Upload the generated feed with `-u`. Add `-i` to trigger the FACT-Finder import after upload.

```bash
php [SHOPWARE_ROOT]/bin/console factfinder:data:export -n -u -i
```

Redirect output to a file when needed:

```bash
php [SHOPWARE_ROOT]/bin/console factfinder:data:export -n > export.csv
```

Set `APP_URL` for the target sales channel when image URLs need its domain.

```bash
APP_URL=http://saleschannel-domain.com php [SHOPWARE_ROOT]/bin/console factfinder:data:export
```

### Use worker export

From plugin version 7.3.0, use worker export for reduced memory usage:

```bash
php [SHOPWARE_ROOT]/bin/console factfinder:data:worker-export
```

It supports the same options as the standard export command.

### Export from administration

Open **Extensions** → **Feed export**. Select sales channel, language, and export type, then create the export.

The export message runs through the Shopware message bus. An admin worker or CLI worker processes it.

### Automate exports

Automatic export is disabled by default. Enable it and choose a sales channel and language.

The default interval is 48 hours. Override `ExportScheduledTask::getDefaultInterval()` to change it. The value is in seconds.

### CMS categories

Select categories through the **Include in CMS Export** custom field on each category edit page.


---

# 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/export-feeds.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.