Docs · 06 Feed Export

Feed Export · automatic URL feeds with templates, profiles and filter presets

Via the Feeds tab you provide automatically updated URL feeds — for Google Shopping, price comparison portals or ERP connections. With built-in templates, your own profiles, filter presets and token authentication.

What is a feed?

A feed delivers your product data under a unique URL — automatically updated, no manual export. The recipient is typically an external system: Google Shopping, idealo, Billiger.de, an ERP system or an analytics pipeline. The URL is tokenised — without the token you see nothing.

Create feed from template

At the top of the Feeds tab you find the "Create feed from template / profile" selector. With one click you create a new feed from a built-in template:

Master data — SKU, name, EAN, manufacturer, active status
Prices & stock — all price fields, stock, base price, purchase price gross/net separately
SEO — meta data in all active languages
Images — cover + gallery as URLs
Variants — master articles + all variants with parent reference
Full export — all available fields

When creating, the following happens automatically:

A saved export profile with the template's field selection is created (name e.g. "Master data (Feed)")
The feed is activated
A unique token is generated
The feed URL is immediately retrievable

Feed from existing profile

Have you already saved your own export profile in the export tab? It can be directly activated as a feed — no detour through "save in the export tab first, then activate somewhere". The profile is offered in the selector, one click → feed is live.

Filter presets in the feed

When creating or editing a feed, you pick a saved filter preset — the same one you also use in the listing or for bulk-edit. The feed then delivers only the products matching this preset:

Example: filter preset "Active articles without images" → a feed only with products that need an image
Example: filter preset "Topsellers sales channel DE" → a feed for your German Google Shopping campaign
Example: filter preset "Stock < 5" → a feed for your supplier as a re-order indicator

No more simple checkboxes: Earlier simple filter checkboxes (with/without variants, only active products) are gone — filter presets are more powerful and consistent with the rest of the plugin.

Feeds as a list with pencil editing

All active feeds appear as a list — each feed has a pencil icon for editing. Via an own storage key (exportFeeds) feeds are decoupled from the underlying export profile:

Rename only affects the feed name, the source profile remains unchanged
Delete only removes the feed entry (incl. token), the source profile remains
Fields copied: on creation, the field selection is copied into the feed profile — later changes to the source profile don't automatically affect existing feeds. The feed stays stable.

Migration of old feeds

Automatic & non-destructive: If you previously had feeds attached directly to an export profile (with token/URL), these are automatically migrated into the new list on first load. Existing feed URLs in your ERP, Google Shopping account or at price comparison portals remain valid — no re-configuration required.

Token and URL format

Each feed gets a unique token. The URL has the format:

https://your-shop.com/staw-pim/feed/{token}.xml
https://your-shop.com/staw-pim/feed/{token}.csv
https://your-shop.com/staw-pim/feed/{token}.json
https://your-shop.com/staw-pim/feed/{token}.tsv

Regenerate token

The regenerate token button creates a new token — the old URL becomes invalid. Useful when a feed link has been leaked publicly or partner access needs to be revoked.

Backend & performance

Feeds are now read by the backend (controller + scheduled task) from the own storage key exportFeeds — no longer from the export profiles. This makes feeds independent of profile changes and enables clear URL stability.

Feeds are rendered live from the Shopware database on request
Caching controllable via HTTP headers (1 hour by default)
Token validation happens before every data query — no data access without a valid token

Security

Don't share tokens publicly: Feed URLs are tokenised and not publicly indexable (no entry in sitemap.xml, noindex header). Anyone who knows the token sees the product data of the feed — so don't post in public repositories or tickets.