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
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.
Open your feed in the Feedyio app.
Scroll down to the Additional fields section.
Click Add field.
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.
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.
Select where the field value comes from. See the Source types section below for a full description of each option.
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
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.
Open your feed in the Feedyio app.
Scroll down to the Additional fields section.
Click Add field.
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.
Same as predefined fields — set the condition under which this value should apply. In most cases, leave it as All products.
Select where the field value comes from. See the Source types section below.
Click Save. To apply the field immediately, go to the Feeds page and click Sync products with Shopify.
Regardless of whether you are adding a predefined or custom field, the Source dropdown determines where the value comes from. There are five options:
Maps the field to any standard Shopify product or variant attribute.
Set Source to Shopify value.
In the Shopify product value dropdown, select the field you need — for example Product ID, Variant Barcode, Variant SKU, Vendor, Product Type, and more.
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.
Maps the field to a product or variant metafield.
Set Source to Metafield.
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.
Maps the field to one of the product's variant options (e.g. Size, Color, Material).
Set Source to Option.
In the Attribute value – Select Option field, enter the exact option name as it appears in Shopify — for example Color, Size, Title.
Outputs a fixed static value for all products that match the case condition.
Set Source to Custom.
Enter the fixed text value in the field that appears.
Useful for constant attributes — for example
newfor a condition field, or a fixed shipping label.
Gives you full control using Shopify's Liquid templating language. Use this when the other source types are not flexible enough.
Set Source to Liquid – Code Expression.
Write your Liquid code in the Code editor. Use the Liquid – Variables and Liquid – Filters tabs to browse what is available.
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:
{% if variant.metafields.custom.ean != blank %}{{ variant.metafields.custom.ean }}{% else %}{{ variant.barcode }}{% endif %}
Example — combine brand and model from two metafields:
{{ product.metafields.custom.brand }} {{ product.metafields.custom.model }}
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.
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.