How to Configure Merchant Feed Adapter?

This document provides a comprehensive guide for configuring and managing Merchant Feed Adapters within the Omnitron, an essential tool for exporting structured product data to external platforms.

Merchant feeds are used to display products on comparison shopping engines, search engines, or affiliate platforms—allowing users to view product details, prices, and availability without visiting the brand’s actual e-commerce site. To support this, Omnitron enables merchants to generate and customize XML feed files based on their own schema requirements, language preferences, pricing lists, and filtering logic.

Whether you are creating a feed for a single market or managing a complex multi-language, multi-region catalog, this tutorial walks you through:

• Setting up new feed adapters through the Omnitron

• Structuring feed content using schema_data

• Mapping product attributes with flexible rule-based logic

• Filtering the feed by SKU or base code using uploaded files

• Managing multiple feeds by language and pricing combinations

• Manually or automatically triggering feed generation

• Accessing the final XML output via a generated file URL

By the end of this guide, you will be able to confidently configure and launch feeds that are optimized for your sales channels, meet third-party specifications, and scale across multiple locales with ease.

Add Merchant Feed Adapter in Omnitron

To begin creating a Google Merchant Feed Adapter, follow the steps below.

Navigate to the Feed Adapter Section

1

Go to Sales Channels > Content Management > Google Merchant Feed Adapter.

2

From this page, you can view existing adapters, edit them, or add new ones.

3

Click on “+ New Goggle Merchant Feed Adapter” to open the adapter creation form.

Fill in Basic Adapter Settings

1

At the top of the page, you’ll see a set of core fields to define the adapter:

Field

Description

Name

A unique name for the feed adapter. This is used to distinguish between different feeds, especially in multi-language or multi-region setups. Example: insider, google_feed_en, feed_ar_uae

Adapter Type

Defines which adapter class will handle feed generation. Select base unless your project includes a custom implementation.

Status

Set this to Active to allow the adapter to be used during scheduled or manual feed generation. If set to Passive, it will be ignored by automatic processes.

One time

Check this box if you want the feed to only be triggered manually. This disables scheduled executions.

File URL

This field is automatically filled after feed generation. It provides a direct link for the generated XML file.

Choose File

(Optional) Upload a filter file in .csv or .xls format. The system will convert it to base64. The file should contain sku or base_code headers to restrict which products are included in the feed.

2

If you're generating feeds for multiple markets, it's a best practice to name the adapter accordingly (e.g., google_feed_ar_ksa) and define separate adapters per language/price list.

Configure Feed Schema (config field)

Once the basic adapter is settings is filled, the next critical step is configuring how the feed will be generated. This is done through the config field, which is a JSON object that defines the structure, behavior, and formatting rules for the XML file that will be generated.

This configuration directly determines:

• Which product attributes are included

• What the output file is named

• How images, categories, and language-specific values are handled

• Whether out-of-stock products are shown

• How visual content (like cropped images or additional images) is formatted

Example Configuration:

{
  "chunk_size": 100,
  "schema_data": [
    {
      "tag": "description",
      "attr_type": null
    },
    {
      "tag": "g:gender",
      "attr_type": null,
      "default_value": "Default"
    },
    {
      "tag": "title",
      "attr_type": null,
      "default_value": "title"
    }
  ],
  "EXTRA_IMAGES": true,
  "feed_filename": "insider/insider-feed_en.xml",
  "IS_ALL_SMALL_IMAGE": true,
  "url_attribute_data": null,
  "THUMBNAIL_CROP_TYPE": "Center",
  "extra_image_configs": [
    {
      "tag_name": "g:image_link",
      "tag_option": {
        "crop": "Center",
        "width": 1080,
        "height": 1080
      }
    }
  ],
  "IS_REQUIRED_SMALL_IMAGE": true,
  "category_attribute_data": [
    "category_name_en-us"
  ],
  "include_stock_out_products": true,
  "price_list_id": 1,
  "stock_list_id": 3,
  "category_name_translate_key": "category_name_en-us",
  "MERCHANT_FEED_VISILABS_IMAGE_TAG": "g:additional_image_link",
  "MERCHANT_FEED_VISILABS_IMAGE_SIZE": {
    "crop": "Center",
    "width": 1080,
    "height": 1080
  }
}

Explanation of Key Fields:

Upload Filter Files (Optional)

To include only specific products in the feed, you can upload a filter file—CSV or XLS—containing product identifiers. Filter files help reduce feed size or tailor feeds to campaign-specific product lists. For example, if you want to export only a selection of SKUs for a seasonal collection, use a filter.

"filter_arguments": {
  "is_listable": true
}

Save and Generate the Feed

Once you’ve completed the Basic Adapter Settings, added your config JSON, and optionally uploaded a filter file, it’s time to save the adapter:

• Click “Save”.

• If your config field is valid and includes a schema_data section, the page will reload and reveal a new section called Mapper Settings.

• This section allows you to define the transformation logic for each XML tag listed in your schema_data.

Attribute Mapping with Rules and Actions

After configuring your feed schema using the config field, the next crucial step is to define how each XML field (tag) retrieves its data from the product catalog. This is done using the Mapper Settings section in the adapter interface.

Each XML tag listed under schema_data must have a corresponding mapper, which includes:

• A rule that determines when the mapping should be applied

• An action that defines how to fetch or transform the data

Together, these enable complex conditional logic, localization, and formatting for your feeds—ensuring data consistency and compatibility with platforms like Google Merchant Center.

Each mapper is a JSON object with two main parts:

1. rule: When should this mapping be applied?

Defines the condition that must be true for the action to run.

2. action: How should the value be retrieved or constructed?

Specifies how to fetch, format, or combine values.

Rule Types (When)

Action Types (How)

Basic Example: Simple Attribute Getter

This mapper fetches the description field from the product data and maps it directly to the <description> XML tag.

{
  "rule": {
    "rule_type": "always"
  },
  "action": {
    "action_type": "attrgetter",
    "action_kwargs": {
      "input_key": "description"
    }
  }

Example: Formatting Gender Using Output Dictionary

If your internal values for gender are stored as M, F, and U, but Google requires male, female, and unisex, use this:

{
  "rule": {
    "rule_type": "always"
  },
  "action": {
    "action_type": "outputdict",
    "action_kwargs": {
      "input_key": "gender",
      "mapping_dict": {
        "M": "male",
        "F": "female",
        "U": "unisex"
      }
    }
  }
}

Combine Multiple Attributes

Use this action when you need to generate a value from multiple fields (e.g., combining brand + title + size).

{
  "rule": {
    "rule_type": "always"
  },
  "action": {
    "action_type": "multiattrformatter",
    "action_kwargs": {
      "input_keys": ["brand", "title", "size"],
      "format_string": "{0} - {1} ({2})",
      "delimiter": " "
    }
  }
}

Output Example: Nike - Air Max (42)

Handling Localized Fields

When generating feeds in multiple languages, you need to retrieve the correct language-specific values from product data. The format of your input_key inside the mapper's action_kwargs will vary depending on:

• Whether the feed is for the default language

• Whether the field is a text or dropdown attribute

For Default Language Feeds

If you're generating a feed in your default language, product attribute values can be accessed using this structure:

"input_key": "attributes__{{attr_code}}"

This directly pulls the attribute from the product's default data.

For Localized Feeds (Non-Default Languages)

For other languages (e.g., Arabic, Turkish, English (US)), you need to reference localized fields. The structure depends on the type of attribute.

For text fields:

Use localized_attributes for retrieving translated text fields such as title, description, or long_name.

Pattern:

localized_attributes__{{language_code}}__{{attribute_code}}

Example:

[
  {
    "rule": {
      "rule_type": "always",
      "rule_kwargs": {}
    },
    "action": {
      "action_type": "attrgetter",
      "action_kwargs": {
        "input_key": "localized_attributes__en-us__l_name"
      }
    },
    "shared_kwargs": {}
  }
]

For dropdown fields:

For dropdown attributes that have translated options (e.g., brand, material, gender), use the attributes_kwargs structure to access the translated label.

Pattern:

attributes_kwargs__{{attribute_code}}___translations__{{language_code}}__label

Example:

[
  {
    "rule": {
      "rule_type": "always",
      "rule_kwargs": {}
    },
    "action": {
      "action_type": "attrgetter",
      "action_kwargs": {
        "input_key": "attributes_kwargs__brand___translations__ar__label"
      }
    },
    "shared_kwargs": {}
  }
]

Triggering and Monitoring Feed Generation

Once your Merchant Feed Adapter is configured and saved, it's time to generate the actual XML feed file. Omnitron provides both automated and manual triggering methods for this purpose. You can also track the status of the generation process and retrieve the final file URL programmatically.

Automatic vs. Manual Triggering:

Trigger Feed Generation Manually (API)

To manually trigger feed generation for a specific adapter:

Endpoint:

POST /api/v1/remote/1/google_merchant_feed_adapter/{adapter_pk}/trigger_task/

Replace {adapter_pk} with the ID of the adapter you want to trigger.

Example Request:

curl --location --request POST 'https://your-commerce-url/api/v1/remote/1/google_merchant_feed_adapter/268/trigger_task/' \
--header 'Authorization: Token your_token_here'

Example Response

{
  "cache_key": "6c27bc5a8f06442f96044302e6168d7a"
}

Monitor Progress of Feed Generation

You can track the progress of the feed task using the returned cache_key.

Endpoint:

GET /api/v1/remote/1/google_merchant_feed_adapter/{adapter_pk}/trigger_status/?cache_key={cache_key}

Example Request:

curl --location 'https://your-commerce-url/api/v1/remote/1/google_merchant_feed_adapter/268/trigger_status/?cache_key=6c27bc5a8f06442f96044302e6168d7a' \
--header 'Authorization: Token your_token_here'

Example Response:

{
  "completed_tasks": 1,
  "data": [
    {
      "progress": [1, 1],
      "completed": true,
      "chunk_count": 1
    }
  ],
  "progress_count": 1
}

Get Feed File URL

Once the task is completed, the file will be available at the adapter’s detail endpoint.

Endpoint:

GET /api/v1/remote/1/google_merchant_feed_adapter/{adapter_pk}/

Example Request:

curl --location 'https://your-commerce-url/api/v1/remote/1/google_merchant_feed_adapter/268/' \
--header 'Authorization: Token your_token_here'

Example Response:

{
  ...
  "file_url": "https://cdn.akinoncloud.com/google/insider-feed_en.xml"
}

You can now use this file URL in your Google Merchant Center, comparison shopping platforms, or campaign tracking tools.

Error Handling

If a feed task is already in progress and a new one is triggered:

Example Response:

{
  "non_field_errors": "Google Merchant Feed task is already running. Please wait until the current task is completed before starting a new one.",
  "error_code": "google_merchant_feed_adapter_100_2"
}

Triggering Feed Manually via Omnitron

In addition to using API calls, you can also manually trigger feed generation directly from the Omnitron interface—with just a few clicks.

1

Select the Feed Adapter(s):

Use the checkbox on the left to select the adapter(s) you want to run. You can select one or multiple rows.

2

Open the "Select Action" Dropdown:

At the top of the list, open the Select Action dropdown.

3

Click “Trigger Task with Selected Items”:

This option will immediately initiate the feed generation task for the selected adapters.

4

Click “Apply”:

The task will be queued and executed via Celery. You can monitor the task’s status using the API or check the file URL once generation is complete.

Feed URL Usage

Once the feed generation is complete, the XML file becomes accessible via the provided file_url. For example, you can access the generated feed directly at:

You can now use this URL to upload the feed to Google Merchant Center or share it with external platforms that support scheduled product feed imports.