A Feed is a stream of data – in our case Product data from a channel – presented in a fixed format using e.g. JSON syntax. Feeds are typically used to make it possible for an external service, like an app or a marketplace tool, to fetch up-to-date information at all times.

A feed consists of:

  • A query which selects the subset of your products you want to publish in the feed
  • A context section which allows you to select shop, currency & language values and pass them to the query
  • A format section where you select which data to include in the feed and how to format it

Each of these components are are explained below.

When you create a feed the first thing you have to do is select a query and configure it (Figure 2.1).

Figure 2.1 Selecting a query

For all intents and purposes you can select any index query, but you should note that if you plan to use the Context section to set the language, currency & shop context the query should be configured to receive the values passed from the feed. This can be done by creating two parameters:

  • languageId
  • shopId

And, of course, creating the expressions using them (Figure 2.2).

Figure 2.2 This query uses the values passed from the feed to filter products from the feed

The context section of a PIM feed definition is used to, well, define the feed context (Figure 3.1).

You can select the following:





Select the Ecommerce language(s) to include in this feed

The query used should have a languageId parameter and an expression using it to filter out products in order for this selection to have an impact on the feed content.


Select the currency you want the feed to use



Select the shop/warehouse/channel

The query should have a shopId parameter and an expression using it to filter out products in order for this selection to have an impact on the feed content.


I most cases you want to select a channel with a structure that corresponds to the service you’re integrating with.


Select a user to pass to the webapi

This is typically used to fetch customer-specific prices on solutions using the price matrix.

Include VariantInfo on Variants

Use to enable/disable VariantInfo parameter on ProductViewModel on variants

Disabling adding VariantInfo can lead to performance improvements.

As described, two of the parameters – Language and Shop – require you to create corresponding parameters on the selected query. The other parameters are used when looking up prices and variants.

The Format section is used to control two things – which data to include in the feed and how to render it. In practice this is done by selecting a feed provider and configuring it:


Used for


Template feed provider

Generating custom feeds using a ViewModel template

To use: 

  1. Select or create a template for generating the feed
  2. Specify a content type
  3. Select the data you want to include in the feed
  4. Save

An URL to the feed will be generated, and can be visited/used externally.

XML feed provider Generating XML feed data - and (optionally) transforming this data using an XSLT stylesheet.

To use:

  1. Select the data you want to include in the feed
  2. Select an XSLT stylesheet which transforms the XML to your desired format
  3. Save

When you save a feed, one or more API URLs to the feed will be generated (Figure 5.1) - click these to review the current feed output in a new tab. Each URL is listed with their selected options, which the feed is based on.

Figure 5.1 Feed API URLs

The API URLs can be extended with custom parameters, provided that the repository query is set up to receive them. Simply add the parameter to the querystring and pass values to it:


You can also set up a scheduled task which saves the contents of a feed in a file - see here.