---
title: "How to Add an Additional Field to Your Feed"
description: "Additional fields let you extend any feed with extra attributes — either to meet a platform's requirements or to pass data that the default template does not include. Each additional field is built around a Case (condition) and a Result (the value to output)."
url: https://help.feedyio.com/en/articles/11764756-how-to-add-an-additional-field-to-your-feed
collection: "Product feeds"
updated: 2026-11-17
language: en
---

# How to Add an Additional Field to Your Feed

Additional fields let you extend any feed with extra attributes — either to meet a platform's requirements or to pass data that the default template does not include. Each additional field is built around a Case (condition) and a Result (the value to output).

There are two types of additional fields:

-   **Predefined field** — the attribute name is already known to Feedyio (e.g. `g:gtin`, `Bundle`, `mpn`) and supported by the marketplace
    
-   **Custom field** — you define your own attribute name for any platform-specific or non-standard field
    

## Option A: Adding a Predefined Field

Predefined fields use attribute names that Feedyio already recognises. A description of the attribute is shown at the bottom of the dialog to help you understand what value it expects.

### Step 1: Open the Additional Fields Section

1.  Open your feed in the Feedyio app.
    
2.  Scroll down to the **Additional fields** section.
    
3.  Click **Add field**.
    

### Step 2: Select the Predefined Attribute

In the **Attribute / Field** dropdown, select the attribute you want to add — for example `Bundle`, `g:gtin`, `mpn`, `g:sale_price`, and others.

> A short description of the selected attribute appears at the bottom of the dialog.

### Step 3: Configure the Case

Cases control **when** the field value is applied. By default, **Case 1** is set to **All products**, which applies the value to every product in the feed.

-   Change the condition to target a specific collection, product type, vendor, or other criteria.
    
-   Use **Must match: any condition / all conditions** to combine multiple conditions.
    
-   Click **Add case** to add a fallback for products that don't match earlier cases.
    

> Most use cases only need one case set to **All products**.

### Step 4: Choose the Source

Select where the field value comes from. See the [Source types](https://claude.ai/chat/54117973-3f9e-4975-b8e6-3bacfb2379d1#source-types) section below for a full description of each option.

### Step 5: Save

Click **Save**. To apply the field immediately, go to the Feeds page and click **Sync products with Shopify**.

> If the predefined field name matches an attribute already present in the template mapping, the additional field value takes priority

## Option B: Adding a Custom Field

Use a custom field when you need an attribute name that is not in Feedyio's predefined list — for example a platform-specific tag, an internal label, or any non-standard field required by a marketplace.

### Step 1: Open the Additional Fields Section

1.  Open your feed in the Feedyio app.
    
2.  Scroll down to the **Additional fields** section.
    
3.  Click **Add field**.
    

### Step 2: Select "Custom attribute"

In the **Attribute / Field** dropdown, select **— Custom attribute —**. A second input box appears — **Custom attribute name / field**. Enter the exact attribute name the platform expects, for example `internal_label`, `EAN`, `promo_text`, `delivery_time`.

### Step 3: Configure the Case

Same as predefined fields — set the condition under which this value should apply. In most cases, leave it as **All products**.

### Step 4: Choose the Source

Select where the field value comes from. See the [Source types](https://claude.ai/chat/54117973-3f9e-4975-b8e6-3bacfb2379d1#source-types) section below.

### Step 5: Save

Click **Save**. To apply the field immediately, go to the Feeds page and click **Sync products with Shopify**.

## Source Types

Regardless of whether you are adding a predefined or custom field, the **Source** dropdown determines where the value comes from. There are five options:

### Shopify value

Maps the field to any standard Shopify product or variant attribute.

1.  Set **Source** to **Shopify value**.
    
2.  In the **Shopify product value** dropdown, select the field you need — for example `Product ID`, `Variant Barcode`, `Variant SKU`, `Vendor`, `Product Type`, and more.
    
3.  Optionally, click **Add modifier** to transform the value (e.g. prepend a prefix, truncate, convert to lowercase).
    

> Use this for any data that already exists as a standard Shopify field.

### Metafield

Maps the field to a product or variant metafield.

1.  Set **Source** to **Metafield**.
    
2.  In the **Metafield key** field, enter the namespace and key separated by a dot — for example `global.text`, `custom.ean`, `reviews.rating`.
    

> You can find the namespace and key in Shopify Admin under **Settings → Custom data → Products**.

### Option

Maps the field to one of the product's variant options (e.g. Size, Color, Material).

1.  Set **Source** to **Option**.
    
2.  In the **Attribute value – Select Option** field, enter the exact option name as it appears in Shopify — for example `Color`, `Size`, `Title`.
    

### Custom

Outputs a fixed static value for all products that match the case condition.

1.  Set **Source** to **Custom**.
    
2.  Enter the fixed text value in the field that appears.
    

> Useful for constant attributes — for example `new` for a condition field, or a fixed shipping label.

### Liquid – Code Expression

Gives you full control using Shopify's Liquid templating language. Use this when the other source types are not flexible enough.

1.  Set **Source** to **Liquid – Code Expression**.
    
2.  Write your Liquid code in the **Code** editor. Use the **Liquid – Variables** and **Liquid – Filters** tabs to browse what is available.
    
3.  Use the **Preview code** section to test the output — enter a product ID, vendor, or title and click **Preview**.
    

**Example — output EAN from a metafield with a fallback to barcode:**

```javascript
{% if variant.metafields.custom.ean != blank %}{{ variant.metafields.custom.ean }}{% else %}{{ variant.barcode }}{% endif %}

```

**Example — combine brand and model from two metafields:**

```javascript
{{ product.metafields.custom.brand }} {{ product.metafields.custom.model }}

```

### Set Default Value

All source types except Liquid support a **Set default value** option. Click it to define a fallback that is used when the source field is empty for a product.

## Frequently Asked Questions

**Does an additional field override the value already in the template?**

Yes. If the field name matches an attribute already in the template mapping, the additional field value takes priority.

**Can I add multiple additional fields?**

Yes, there is no limit. Each field is configured independently with its own cases and source.

**My Liquid expression returns blank for some products — is that a problem?**

If the expression evaluates to an empty string, the attribute is omitted from the feed for that product. If the platform requires the field for all products, add a fallback using a Liquid `{% else %}` clause or use **Set default value**.

**Can I use additional fields in a predefined template?**

Yes. Additional fields work with both predefined and custom feed templates.
