> 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-1.md).

# Export feeds

Export, upload, and import Shopware data for FACT-Finder.

FACT-Finder can export product, CMS, brand or manufacturer, and category feeds. Add further data types through `factfinder.data_export.entity_type_map`.

### CLI exports

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

Use `-u` to upload the generated feed. Use `-i` to trigger the FACT-Finder import after upload. `-i` requires `-u`.

Set a sales-channel image domain with:

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

From version 7.3.0, use the lower-memory worker flow:

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

It accepts the same options as the standard command.

### CMS and admin exports

Select categories for CMS exports using the category’s **Include in CMS Export** custom field.

Run an end-to-end export from `/admin#/ui/feed/export/index`. Select the sales channel, language, and export type. The form sends a message for an enabled admin worker or a CLI worker.

### Add feed fields

Implement `Omikron\FactFinder\Shopware6\Export\FieldInterface`. Provide `getName()`, `getValue(Entity $entity)`, and `getCompatibleEntityTypes()`. Register the service with autoconfiguration, or tag it as `factfinder.export.field`.

Only `CustomFields` and `ImageUrl` export from variants by default. Tag other fields with `factfinder.export.variant_field`. Add required variant joins through `factfinder.export.associations`, for example `children.cover`. Additional associations can slow exports.

### Export custom entities

For a new entity type, provide an `ExportInterface`, `ExportEntityInterface`, and `FactoryInterface`. Use `GenericEntityFactory` when no custom yielding logic is required.

Use `FieldInterface` for complex field values. Its compatible entity types control where it applies. Create and generate a feed with:

```php
$feed = $this->feedFactory->create($context, YourCustomEntity::class);
$feed->generate();
```

`$context` is a `SalesChannelContext`.


---

# 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-1.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.