Data Feed Manager

The Tool Box or so-called "Black Box"

When creating a data feed, you should see a blackbox on the right of your screen. The Data Feed Manager extension includes that tool to help you create your feed and see what is wrong.

The blackbox is inevitably a very useful tool. This will help you to configure your data feed more quickly.

Here are the different options of the blackbox:

Syntax Validation

The  Check syntax button allows you to check if your syntax is correct. It helps you to see if you have forgotten a bracket or a comma by underlining in yellow the part of text that contains a mistake.

Library

If you click on Load Library, a library of your store attributes will be displayed. This makes it easier to find very quickly which attribute you need to add into your template.

Data Preview

When clicking on Check Data, you'll see a preview of your data feed. It's very useful to see if the values of your attributes are correctly retrieved or if your filters are working. 

Export and import your templates

Data Feed Manager also allows you to export and import templates into/from your Magento admin.

Export

To export a template, select an existing feed from:
Catalog › Data Feed Manager › Data Feeds

From the dropdown under the Action column, you can choose to Export that data feed template. You can also choose to Edit the data feed and then click on Export.

Via both ways, a popup window opens and allows you to save the data feed template as a .dfm file. After that, you should find the data feed template in your 'Downloads' folder.

Import

Before anything, to import a data feed template, it must be a .dfm file.

To do so, go to:
Catalog › Data Feed Manager › Data Feeds

Click on Import a template. Browse the .dfm file and click on Import now.

Now, you should see that the data feed has been imported at the end of the grid in:
Catalog › Data Feed Manager › Data Feeds

Configuration

When creating a new data feed, you have to configure a certain number of parameters from:
Catalog › Data Feed Manager › Data Feeds

In that first tab is the main configuration of the data feed. You'll find several fields to fill in.

• Feed name
  Enter the name of your feed. For example:
  

  GoogleShopping

• File type
  Choose the format of your file between XML, CSV, TXT, and TSV.
• File name format
  You have several format possibilities for your file name. 
  

  GoogleShopping-2015-01-26.xml

• Encoding type
  Choose the encoding type of the data feed.
• Path
  Define the path where you want the data feed to be generated.
  

  /feeds/

• File status
  Enable or disable the file.
• Store View
  Define which store view is concerned.

The following fields vary according to the file type you're configuring. 

XML files

If you want to configure an XML file, fill in: 

• Enclose xml tag content inside CDATA (recommended)
  Enclose xml tags inside CDATA or not. 
• Remove all empty xml tags (recommended)
  Remove empty xml tags or not.
• Header pattern
  Add your header pattern in that field. 
• Product pattern
  This field is inevitable to configure your product pattern.
• Footer pattern
  Add your footer pattern in that field.  

CSV, TXT, TSV files

For CSV, TXT and TSV files, fill in: 

• Extra header
  It will add whatever you write on the top of your file (fit in with Amazon requirements).
• Include header
  Allows you to include or not columns names in the first row of your file.
• Columns name
  Is for the attribute name (you need to look in the shopping engine specifications to know which names are required).
• Pattern
  Works in the same way than XML files. For example, {url} will return the product's url. You can also add any static values.
• Add field button
  Click on it to add a new column to your template. The fields order can be easily reordered by using the up and down arrows.
• Extra footer
  You can add an extra footer in that field.
• Fields delimiter
  Lets you choose which kind of delimiter you want to use to separate your fields.
• Fields enclosure
  Lets you choose which kind of enclosure you want for your data.
• Escape character
  Define the escape character between \ or ''.

Categories filter

You can filter your categories according to two different ways:

• Exclude all products from the selected categories.
• Include all products from the selected categories.

For example, if you wish to include only products of the Apparel category, you can configure your filter in two different ways.

First of all by ticking the Include option that will allow you to include all categories that you have selected.

Or via the Exclude option that will exclude all categories you have selected.

Category mapping

In that subtab, you can map your categories to the ones of marketplaces. This step is very important so that they can make a link between their product categories and yours.

What is a category mapping?

The category names you are using in your Magento aren't always the same as the ones used by marketplaces to reference your products.

This means you have to find out which categories have the best matching with yours, according to their taxonomy.

For example with Google Shopping, if you're selling furniture like coffee tables, you'll have a Coffee table category in your Magento admin. But Google Merchant doesn't handle this kind of category. The closest Google product category could be Kitchen & Dining Room Table.

Map your categories with Data Feed Manager

Data Feed Manager provides you an easy way to input the categories of the marketplaces that are matching yours.

In your data feed configuration, for example, Google Shopping. Go in the Categories tab. Then, in Category selection and mapping section, you'll find a tree view of all your categories.

First, select the Google Taxonomy source on which the category mapping is based.

Taxonomy files for the main countries are directly included to allow you to map your categories more easily. You can also have a look at the below documentation to know how to add a new taxonomy file.

For each category, you have a little arrow followed by mapped as. There, you'll be able to start typing a keyword in order to display a list of all categories including that keyword. You simply need to select the one you need.

Once all your categories are mapped, you can click on SAVE.

Here are a few guidelines for choosing the most appropriate category:

• Use the category that best describes your item. To do this, first determine the primary function of the products you are submitting. For specific items like MP3 Players, select the MP3 Players category. While some MP3 players can also serve different functions, like those that contain a clock, they are primarily MP3 Players.
• Use only one category. For some products, more than one category might be relevant. For example, an adapter to allow an MP3 player to be used in a car could be in both categories Motor Vehicles > Audio & Video and Electronics > Audio > Audio Accessories > MP3 Player Accessories. In such cases, choose the category that seems the most appropriate to you, but don't include more than one.
• Use the most specific category possible. Being specific will help to improve your data quality and so ensure that offers are presented in the right category. When viewing the taxonomy, try to navigate to the most specific category that still covers all the products that are being submitted. For instance, if you are submitting MP3 player chargers use the MP3 Player Chargers category. Conversely, if you are submitting multiple types of chargers use the Chargers category.

How to include the category to the XML template?

Finally, so that the category is retrieved in your data feed, you must add the following attribute to the XML template:

<category>{category_mapping,[0]}</category>

or for Google: 

<g:google_product_category>{category_mapping,[0]}</g:google_product_category>
or
{G:GOOGLE_PRODUCT_CATEGORY}

How to add a new taxonomy file?

The taxonomy is a tree of categories that will help you match your categories to the ones of marketplaces. For example with Google Shopping, it lists all possible values for the 'Google product category' attribute.

In that page, choose the language you want to use for your taxonomy at the bottom right. Then, in the Downloadable taxonomy, open the Plain Text link that contains full category names.

Save that file and paste it in:
Magento Root Directory › Lib › Wyomind › google

Don't forget to apply the permissions 755 to the file.

You'll then be able to choose that specific taxonomy from your data feed configuration in the Categories tab.

Filters

Data Feed Manager also allows you to filter your products on several levels according to their attribute sets or their visibility for example.

Product Type

First of all, you can choose to include products to your feed according to their type. For example, don't include grouped products.

Attribute Set

You have the choice to include the attribute sets you want.

Product Visibility

Then, choose the products that will be included to the feed between the products that are not visible individually, products from the Catalog, the Search results, or both.

Advanced Filters

In the Advanced filters, you can go further by setting more personalized filters.

For example, we wanted to include only products which are enabled, and which SKU and name are not null.

Here again, you have the possibility to configure your advanced filters according to several options.

• LIKE / NOT LIKE

name like %shirt: will include all products which name ends with 'shirt'.
name like Apple%: will include all products which name starts with 'Apple'.
name like %women%: will include all products which name contains the 'women' character string.
name not like %shirt: won't include any product which name ends with 'shirt'.
name not like Apple%: won't include any product which name starts with 'Apple'.
name not like %women%: won't include any product which name contains the 'women' character string.

• IS NULL / IS NOT NULL

Special price is null: will include all products that don't have special prices.
SKU is not null: will include all products which SKU is not null.

• IN / NOT IN

Brand in Acer Apple Sony: will include only products from these 3 brands.
Brand not in Dell Toshiba: will include all products which brand is not Dell or Toshiba.

Advanced filters can be grouped into sub-division by using AND/OR clauses.

(SKU LIKE ABC% AND Brand = Acer) OR (Brand IN Dell, Toshiba AND Price >= 99.99)

The option must be enabled in:
System › Configuration › Wyomind › Data Feed Manager

Scheduled Tasks

Data Feed Manager provides you a fully configurable schedule in the Scheduled task tab of your template configuration for each data feed. You just have to tick the days and hours when you want your feed to be generated.

FTP Settings

In Data Feed Manager, you can specify ftp settings to upload your data feeds.

Select a data feed and go to the Ftp Settings tab. There you'll be able to configure some parameters:

• Enable FTP upload
  Select Yes if you want to upload your data feed using FTP.
• Use SFTP
  Select Yes if you are using SFTP.
  Secure connection (sftp) is only available in the latest version of Data Feed Manager.
• Use Active mode
  If you are using SFTP, you don't have to care about the passive/active mode.
  For more info about Active and Passive mode, have a look to that documentation.
• Host
  In that field, fill in the host. For example:
  

  ftp.wyomind.com

• Login
  Is your login to connect to server
• Password
  Is your password to connect to server
• Destination directory
  Is a relative path from the entry directory when you connect to the ftp. For example:
  

  upload/
  or
  /

In order to be sure your settings are correct, click on Test Connection .

• If you don't have an error message, it means the connection succeeded.
• If you have an error message, you'll certainly have to check your credentials.

Generate the data feeds

With Data Feed Manager, you can generate your data feed manually or automatically.

Manually

There are two different ways you can use to generate your data feeds manually: 

• You can generate your data feeds in the grid from the action dropdown.

• Or you can do it from the data feed configuration panel by clicking on  GENERATE  . 

Via the cron tasks

You can generate your data feeds automatically using the cron tasks. 

First, check that the main cron task is enabled on your server.

If it is disabled, a warning message will appear in Data Feed Manager:

Then, you have to select in the Scheduled Task tab, the days and time frames when you want the data feed to be updated.

From the command lines

Data Feed Manager allows generating data feed via the command lines

php -f shell/wyomind_datafeedmanager.php -- [options]

The following options are available:

• --generate
  Generate all data feeds
• --generate id1,id2,...,idN
  Generate data feeds from the given list
• --list
  List all data feeds

Download the data feeds

When a data feed is ready to be downloaded, the link is displayed in both, the data feed grid and the data feed page at the top of the page. You can download the data feed directly by right-clicking + saving link as or from your ftp client if the directory where the data feed is stored is not publicly accessible.

PARENT ATTRIBUTES

Most of the time simple products are related to parent products like configurable, grouped and bundle products. That is why you might need to retrieve Parent attribute values instead of simple product attribute values such as url, image, description...

All the above attributes (Basic, Special and Magic) may be used to retrieve a Parent attribute value instead of a product attribute value.

All options are still available, for example:

{description parent,[htmlentities]}

{attribute_code parent}

Retrieves the first parent attribute value.

The parent value is retrieved only if the simple (item) product is associated with a parent product, if not, its own attribute value is retrieved.

The parent product may be a configurable, a grouped or a bundle product. The first parent product that matches the simple product is used to get the attribute value.

For example:

{G:PRODUCT_TYPE parent}
<g:product_type>{categories parent,[last]}</g:product_type>

{attribute_code configurable}

Retrieves the first configurable parent attribute value.

The configurable product value is retrieved only if the simple product is associated to a configurable product, if not, its own attribute value is retrieved.

For example:

{G:IMAGE_LINK configurable}
<g:image_link>{image configurable}</g:image_link>

{attribute_code grouped}

Retrieves the first grouped parent attribute value.

The grouped product value is retrieved only if the simple product is associated to a grouped product, if not, its own attribute value is retrieved.

For example:

{G:GOOGLE_PRODUCT_CATEGORY grouped}
<link>{url grouped}</link>

{attribute_code bundle}

Retrieves the first bundle parent attribute value.

The bundle product value is retrieved only if the simple product is associated to a bundle product, if not, its own attribute value is retrieved.

For example:

{G:SALE_PRICE bundle}
<g:price>{price bundle}</g:price>

PRODUCT IDENTIFIERS

{id}

Retrieves the product id.

For example:

<g:id>{id}</g:id>

{G:ID}

Is the shortcut for:

<g:id>{sku}</g:id>

You can retrieve the id instead of the sku by adding an option:

{G:ID,[id]}

{G:ITEM_GROUP_ID}

Is the shortcut for:

<g:item_group_id>{sku configurable}</g:item_group_id>

{sku}

Retrieves the product SKU.

For example:

<g:mpn>{sku}</g:mpn>

{brand}

Retrieves the brand of the product.

For example:

<g:brand>{brand}</g:brand>

{manufacturer}

Retrieves the brand of the product.

For example:

<g:manufacturer>{manufacturer}</g:manufacturer>

BASIC INFORMATION

{inc}

<g:increment>{inc}</g:increment>

{name}

Retrieves the product name.

Par exemple:

<g:title>{name}</g:title>

{G:TITLE}

Is the shortcut for:

<title>{name}</title>

{description}

Retrieves the description of the product.

For example:

<g:description>{description}</g:description>

{G:DESCRIPTION}

Is the shortcut for:

<description>{description}</description>

You can retrieve the short description instead by adding a parameter:

{G:DESCRIPTION,[short]}

{short_description}

Retrieves the short description of the product.

For example:

<g:description>{short_description}</g:description>

{condition}

Retrieves the condition of the product.

For example:

<g:condition>{condition}</g:condition>

{weight}

Retrieves the weight of the product.

For example:

<g:weight>{weight}</g:weight>

{magento_product_type}

Retrieves the Magento product type (simple, configurable...).

For example:

<magento_product_type>{magento_product_type}</magento_product_type>

PRICES AND PROMOTIONS

{price}

Retrieves the normal price or the special price if it exists.

If prices are exclusive of VAT and the product is liable to a unique VAT rate, the price retrieved will include this rate. Otherwise, the price exclusive of tax is retrieved.

For example:

<g:price>{price}</g:price>

You also have the possibility to use some parameters with this attribute:

• currency is for currency conversion. This option automatically converts the original product price to a specified currency. It uses an exchange rate already stored by you in your admin panel. By default, your local currency is used.
• vat_rate is a floating value between 0.00 and 100.00 that represents an arbitrary VAT rate to apply. This option rewrites the VAT rule for the product except if the product doesn't have any tax class. 

<g:price>{price,[currency],[vat_rate]}</g:price>

Here are some examples:

To convert the prices to EUR and apply a 20% VAT rate:

<g:price>{price,[EUR],[20.0]}</g:price>

To convert the prices to USD and not apply any VAT rate:

<g:price>{price,[USD],[0]}</g:price>

If the prices of your catalog are already including VAT:

<g:price>{price,[EUR]}</g:price>

To use an ISO2 code corresponding to one of the countries for which you specified a VAT rate in your tax settings (from Simple Google Shopping >= 5.1.0, and Data Feed Manager >= 3.0.0 ):

<g:price>{price,[EUR],[FR]}</g:price>

This code may also be completed by an area code:

<g:price>{price,[USD],[US/NY]}</g:price>

To apply the VAT corresponding to a country/area:

<g:price>{price,[USD],[-US/NY]}</g:price>

To retrieve prices including different price values for simple products associated to a configurable one (from Data Feed Manager v7.3 ):

<g:price>{price parent,[EUR],[20.0]}</g:price>

{G:PRICE}

Is the shortcut for:

<g:price>{price}</g:price>

{normal_price}

Retrieves the price and ignores any existing special price value.

<g:price>{normal_price}</g:price>

{special_price}

Retrieves the promotional price (special price) if exists.

If this price doesn't exist the value is null.

<g:price>{special_price}</g:price>

{price_rules}

Retrieves either the price or the special price or the price including the catalog price rules if indicated.

For example:

<g:price>{price_rules}</g:price>

You also have the possibility to use some parameters with this attribute:

• currency is for currency conversion. This option automatically converts the original product price to a specified currency. It uses an exchange rate already stored by you in your admin panel. By default, your local currency is used.
• vat_rate is a floating value between 0.00 and 100.00 that represents an arbitrary VAT rate to apply. This option rewrites the VAT rule for the product except if the product doesn't have any tax class.

• customer_group_id allows you to determine which price rules must apply for a given custom group id (by default the "NOT LOGGED IN" customer group applies).

<g:price>{price_rules,[currency],[vat_rate],[customer_group_id]}</g:price>

{group_price}

Retrieves the group price if it exists. Otherwise, it displays the normal price.

For example:

<g:price>{group_price,[1],[USD],[0]}</g:price>

You also have the possibility to use some parameters with this attribute:

• customer_group is the id of the customer group for which the group price is valid (check in: Customers › customer groups).
• currency is for currency conversion. This option automatically converts the original product price to a specified currency. It uses an exchange rate already stored by you in your admin panel. By default, your local currency is used.
• vat_rate is a floating value between 0.00 and 100.00 that represents an arbitrary VAT rate to apply. This option rewrites the VAT rule for the product except if the product doesn't have any tax class. 

<g:price>{group_price,[customer_group],[currency],[vat_rate]}</g:price>

{G:SALE_PRICE}

<g:sale_price>{special_price}</g:sale_price>
<g:sale_price_effective_date>{special_from_date}/{special_to_date}</g:sale_price_effective_date>

<g:price>{normal_price}</g:price>
{G:SALE_PRICE}

{is_special_price}

• value_if_yes value to retrieve if a special price exists. By default 1.
• value_if_no value to retrieve if no special price exists. By default 0.

For example:

<g:is_special_price>{is_special_price?[yes]:[no]}<g:is_special_price>

{tier_price}

Retrieves the tier price if it exists, otherwise, the value is null.

For example:

<g:price>{tier_price}</g:price>

You also have the possibility to use some parameters with this attribute:

• customer_group is the id of the customer group for which the tier price is valid (check in Customers › Customer Groups).
• index is the index of the Tier Price you want to retrieve.
• currency is for currency conversion. This option automatically converts the original product price to a specified currency. It uses an exchange rate already stored by you in your admin panel. By default, your local currency is used.
• vat_rate is a floating value between 0.00 and 100.00 that represents an arbitrary VAT rate to apply. This option rewrites the VAT rule for the product except if the product doesn't have any tax class. 

<g:price>{tier_price,[customer_group],[index],[currency],[vat_rate]}</g:price>

{min_price}

Retrieves the minimum price.

<g:price>{min_price,[EUR],[20.0]}</g:price>

{max_price}

Retrieves the maximum price.

<g:price>{max_price,[EUR],[20.0]}</g:price>

{G:PROMOTION_ID}

Retrieves the product promotion id if exists.

To know more about the use of this attribute, check out our doc on Google Merchant Promotions extension.

LINKS

{url}

<g:link>{url}</g:link>

The url attribute can receive the currency code as a url parameter to display the landing page with a specific currency, for example:

<g:link>{url}?currency=USD</g:link>

With children of configurable products {url} can be used with one additional parameter as follows:

{url,[variant]}

• variant (optional): generates the url of the configurable product including additional parameters that may help to display the price of the variant and to pre-select the configurable attribute

<link>{url,[variant]}</link>​
// return for example: https://www.website.com/product-page.html?c=583&391=768#391=768

{G:LINK}

Is the shortcut for:

<link>{url}</link>

{image}

• index is the index of any additional images to retrieve. By default 0 (the main image).

For example:

<g:image_link>{image,[0]}</g:image_link>

{G:IMAGE_LINK}

<g:image_link>{image}</g:image_link>
<g:additional_image_link>{image,[1]}</g:additional_image_link>
<g:additional_image_link>{image,[2]}</g:additional_image_link>
...

{host}

Retrieves the host url, for example https://www.website.com.

An example with attribute {small_image}:

<g:image_link>{host}/media/catalog/{small_image}</g:image_link>

{url_key}

<g:url>https://www.mywebsite.com/mystore_code/{url_key}</g:url>

CATEGORIES

{categories}

Retrieves a list of category paths separated by "," in which the product may be found.

{categories,[number_of_category_path],[from_category_level],[number_of_categories_in_each_path]}

• number_of _category_path, by default infinity
• from_category_level, by default 1 (root catalog)
• number_of_categories_in_each_path, by default infinity

For example:

<g:categories>{categories,[INF],[1],[INF]}<g:categories>

2 arguments can be used to specify the path separator and the category separator:

{categories,[path_separator],[category_separator]}

• path_separator, by default "comma" (,).
• category_separator, by default "higher than" (>)

For example:

<g:categories>{categories,[,],[>]}<g:categories>

Only one argument can be used to get the first or the last (deepest) category path:

For example:

<g:categories>{categories,[last]}<g:categories>
<g:categories>{categories,[first]}<g:categories>

A complete list of all categories per product can be retrieved with the following method:

<? $product->getCategoriesArray(); ?>

{G:PRODUCT_TYPE}

<g:product_type>category A > sub-category B </g:product_type>
<g:product_type>category A > sub-category B > sub-category C</g:product_type>

{category_mapping}

Retrieves any new category that you have assigned (in the Categories filter) to the item's own product category. If no mapping is assigned to the first category found, the second category will be used etc.

{category_mapping,[index]}

• index: index of the category mapping

For example:

<category>{category_mapping,[0]}</category>
<category>{category_mapping,[1]}</category>
<category>{category_mapping,[2]}</category>
<category>{category_mapping,[3]}</category>
<category>{category_mapping,[4]}</category>

Will retrieve a maximum of 5 category mappings in 5 separate tags.

{G:GOOGLE_PRODUCT_CATEGORY}

Is the shortcut for:

<g:google_product_category>{category_mapping,[0]}</g:google_product_category>

This magic attribute retrieves the Google category that you assigned (in filter section/category filter) of the first category found to which the product is linked. If no Google category is assigned to the first category found, the second category will be used, if no Google category is assigned to the second, the third will be used etc.

To find the Google categories that match with your categories:
Google Product Category documentation

{attribute_set}

Retrieves the attribute set in which the product is.

For example:

<attribute_set>{attribute_set}</attribute_set>

That attribute can be useful for your Adwords campaigns.

AVAILABILITY

{status}

Retrieves either "enabled" if the product is enabled or "disabled" if the product is disabled.

{status,[value_if_enabled],[value_if_disabled]}

You can modify the default values:

• value_if_enabled: value to retrieve if the product is enabled
• value_if_disabled: value to retrieve if the product is disabled

For example:

<g:status>{status,[enabled],[disabled]}</g:status>

{stock_status}

Retrieves the stock status "in stock" or "out of stock".

For example:

<g:availability>{stock_status,[instock],[outofstock]}</g:availability>

{G:AVAILABILITY}

is the shortcut for:

<g:availability>{is_in_stock?[in stock]:[out of stock]:[available for order]}</g:availability>

{is_in_stock}

• value_if_in_stock value to retrieve if the product is in stock
• value_if_out_of_stock value to retrieve if the product is out of stock
• value_if_preorder value to retrieve if the product is backorderable

For example:

<g:availability>{is_in_stock?[in stock]:[out of stock]:[preorder]}</g:availability>

{qty}

Retrieves the available quantity.

The quantity retrieved for the configurable products is based on the sum of simple products.

For example:

<g:availability>{qty}</g:availability>

{min_sale_qty}

Retrieves the minimal sale quantity.

For example:

<g:min_sale_qty>{min_sale_qty}</g:min_sale_qty>

REVIEWS

{review_count}

• storeview_id is the id of your store view. If not specified the current store view is used.
  "*" will count all reviews for all store views.

For example:

<g:product_review_count>{review_count,[*]}</g:product_review_count>

{review_average}

Retrieves the average score of all the evaluations that your customers have left for the product.

{review_average,[storeview_id],[ base_value]}

• storeview_id id of your store view. If not specified the current store view is used.
  "*" will count all reviews for all store views.
• base_value the base number. By default 5.

For example:

<g:product_review_average>{review_average,[*],[3]}</g:product_review_average>

{G:PRODUCT_REVIEW}

<g:product_review_average>{review_average}</g:product_review_average>
<g:product_review_count>{review_count}</g:product_review_count>

PRODUCT VARIANTS

{gender}

Retrieves the gender of the product.

For example:

<g:gender>{gender}</g:gender>

{age_group}

Retrieves the age group of the product.

For example:

<g:age_group>{age_group}</g:age_group>

{color}

Retrieves the color of the product.

For example:

<g:color>{color}</g:color>

{size}

Retrieves the size of the product.

For example:

<g:size>{size}</g:size>

{material}

Retrieves the material of the product.

For example:

<g:material>{material}</g:material>

{pattern}

Retrieves the pattern of the product.

For example:

<g:pattern>{pattern}</g:pattern>

BASIC OPTIONS

Basic attributes are the default attributes defined in Magento and also include any attributes you have defined for your products. (eg: name, description, short_description, weight, size, color)

You can apply one or more options to all of these attributes by using the following syntax:

{attribute_code,[option1],[option2],[option3],[...]}

All options are executed in the written order eg:

<title>{name}</title>
<title>{name,[htmlentities],[strtolower]}</title>
<title>{name,[htmlentities],[strtolower],[ucwords]}</title>

will produce:

<title>NOKIA© 2610 Phone</title>
<title>nokia&copy; 2610 phone</title>
<title>Nokia&copy; 2610 Phone</title>

{attribute_code,[strip_tags]}

Remove all html tags.

For example:

<description>{description,[strip_tags]}</description>

{attribute_code,[cleaner]}

Remove all characters that don't belong to the UTF8 charset.

For example:

<title>{name,[cleaner]}</title>

{attribute_code,[substr],[max_length],[end_string]}

• max_length: maximum length of the value
• end_string: string that will be added at the end of the string. By default: [...]

For example:

<description>{description,[substr],[50],[...]}</description>

{attribute_code,[strtoupper]}

Transforms the value to upper case.

For example:

<title>{name,[strtoupper]}</title>

{attribute_code,[strtolower]}

Transforms the value to lower case.

For example:

<title>{name,[strtolower]}</title>

{attribute_code,[inline]}

Removes all EOL characters from the value.

For example:

<description>{description,[inline]}</description>

{attribute_code,[html_entity_decode]}

Converts all HTML entities to their applicable characters.

For example:

<description>{description,[html_entity_decode]}</description>

{attribute_code,[htmlentities]}

Converts all applicable characters to HTML entities.

For example:

<description>{description,[htmlentities]}</description>

{attribute_code,[implode],[separating_string]}

Joins all array elements in a string.

• separating_string: string used between each value. By default it is a comma (,).

May be useful for multi-select attributes like color.

For example:

<g:color>{color,[implode],[,]}</g:color>

will give:

black, blue, red, green

{attribute_code,[float],[decimals]}

Converts a numeric value to a floating number.

• decimals: number of floating number. By default [0].

<g:shipping_weight>{weight,[float],[2]}kg</g:shipping_weight>

STOCK IN THE CHANNEL USERS

The Stocks in The Channel users can use the following attributes in order to build their data feeds :

{SC:URL}

Retrieves the canonical URL of the product:

<link>https://www.example.com/product.html</link>

{SC:EAN}

Retrieves the unique ean value of the product:

<g:ean>1234567891234</g:ean>

{SC:IMAGES}

Retrieves the associated image of each product:

<g:image_link>https://www.example.com/media/catalog/image.jpg</g:image_link>

{SC:DESCRIPTION}

Retrieves the description for the product:

<g:description>...product description ...</g:description>

A default value is retrieved when the description is empty.

API coding standards

The Data Feed Manager PHP API uses the exact same syntax and standards as any PHP coding.

Attribute calls

For performance reasons, Data Feed Manager only loads in the collection of products the attributes that are explicitly required in the data feed template.

This means that only the attributes that are called using the template placeholders, {attribute_code}, will be added to the collection of products.

As a consequence, when you try to access the value of an attribute from the $product object, you must be sure that the attribute has been added to the collection.

Most of the time when the returned value is null for a given attribute, it means the attribute is not loaded in the collection of products.

The best way to be sure that all the attributes you need are well loaded in the collection, is to add at the beginning of your template a simple script that lists all the attributes required.

<?
/* list of required attributes
* {attribute_1} {attribute_2} {attribute_3} {attribute_4}...
*/
?>

Then you should be able to get the values of these attributes in your PHP script:

<? return $product->getAttribute1();?>
<? return $product->getAttribute2();?>
<? return $product->getAttribute3();?>
....

PHP functions in attribute calls

You can use any PHP function to apply in the attribute calls even if the function requires one or more additional arguments, for instance:

{name,[str_replace("Apple","Banana",$self)]}

You can use several consecutive functions:

{ean,[str_pad($self,10,"0",STR_PAD_LEFT)],[str_replace("X","0",$self)]}

Conditional values

To output values based on different conditions, use PHP conditional statements:

• if/else
  

  <?
  /* attribute {sku} required */
  if ($product->getSku()=="abc"){
  return "Alphabetic";
  }
  elseif($product->getSku()=="123"){
  return "Numeric";
  }
  else{
  return "Mixed";
  }
  ?>

• switch/case
  

  <?
  /* attribute {sku} required */
  switch($product->getSku()){
  case "abc":
  return "Alphabetic";
  break;
  case "123":
  return "Numeric";
  break;
  default:
  return "Mixed";
  }
  ?>

Opening and closing tags

When using the PHP API inline directly in your data feed template, you must use the opening and closing short PHP tags (<? ... ?>)

<?
if($product->getData('size')=="X-Large") {
return "XL";
}
?>

Outputting a value

• Return
  Any value that you want to output in your data feed, must be returned with the return instruction.

<? return "Don't miss! ".$product->getTitle(); ?>
/* This script adds for each product in data feed  a new ouput line
*  Don't miss! Iphone 5
*  Don't miss! Galaxy note 7
*  ...
*/

• echo, var_dump, print_r
  Any value printed in the data feed through these functions will be rendered at the top of the data feed and will not be added to the final file.
  Such functions must be used for debugging purposes.

<? var_dump($product->getTitle()); ?>
/* This script adds for each product in data feed  a new debugging trace
*  String(8) "Iphone 5"
*  String(13) "Galaxy note 7"
*  ...
*/

Variables scope

All variables available in PHP scripts have a local scope, this means they can't be shared between several scripts.

If you wish to share a variable with different scripts all along the data feed generation process, then the variable must be set as a global variable.

<?
global $increment;
$increment++;
return $increment;
/* This script will output a incremental $variable
* 1
* 2
* 3
* ...
*/
?>

API Objects, Variables and Methods

Object $product

$product is an instance of Mage_Catalog_Model_Product. It contains all methods available by default and some other specific to Data Feed Manager.

The list below is not exhaustive but lists the most useful methods.

• $product->getCategoriesArray()
  Retrieves an array of arrays that describes the categories to which belongs the products
• $product->getCategoryIds()
  Lists all category ids in which the product may be found
  
• $product->getVisibility()
  Returns the visibility of the product (1 = not visible individually, 2 = catalog, 3 = search, 4 = catalog and search)
  
• $product->getStatus()
  Returns the status of the product (1 = enabled, 2 = disabled)
  
• $product->getData($attributeCode)
  Returns the value of the given attribute code
  
• $product->getAttributeText($attributeCode)
  Returns the textual value of the given attribute code
  

Object $this

$this is an instance of Wyomind_datafeedmanager_Model_Feed. It provides a few useful methods.

• $this->hasParent($product, $type="parent")
  Returns a Boolean value whether a product has a parent from the given type (parent, configurable, grouped, bundle) or not
  
• $this->getParent($product, $type="parent", $strict=false)
  Returns a product object of the given parent type (parent, configurable, grouped, bundle) if available or the product object passed as 1st parameter when $strict parameter is set on false.
  
• $this->skip()
  Skips the current product, useful to filter out some products based on specific condition
  

String | Integer | Boolean | Array $self

$self is the value of the attribute for the current product.

This variable is available only in the custom attributes, and in the custom functions.

Variable $param

The variable $param contains an array of the parameters that have been passed to the custom function.

{{ean,[str_pad],[10],[0]}}

The custom function str_pad, should be written as follows

<?
/* var_dump($param) gives
*  Array(3)[
*    0 => String(7) "str_pad",
*    1 => String(2) "10"
*    2 => String(1) "0"
*  ]
*/
return str_pad($self,$param[1],$param[2],STR_PAD_LEFT);
?>

This variable is available only for the custom functions.

Use custom attributes

Create custom attributes

Data Feed Manager allows you to create your own attributes and to add them to your data feed. 

To create custom attributes from your Magento admin, go to:
Catalog › Data Feed Manager › Custom Attributes

Some templates of use are loaded by default when installing the extension.

Here is how to proceed:

1. Create a new attribute.
   

   

2. Fill in the attribute code with the name of your custom attribute
   

   

3. Add your custom script. No need to add the PHP tags (<? ... ?>)
   

   

4. Add the new custom attribute into your data feed template in:
   Catalog › Data Feed Manager › Data Feed

Examples of custom attributes

Replace some words in the product descriptions:

<?
$search=array('Nokia','BlackBerry','apple');
$replace=array("NOKIA","BLACKBERRY","APPLE");
return str_ireplace($search, $replace,$product->getDescription());
?>

Create a thumbnail of the product image:

<? return Mage::helper('catalog/image')->init($product, 'image')->resize(265,265); ?>

Filter out products that match a condition:

<?
if(strlen($product->getUpc())>=12) return $product->getUpc();
elseif ($product->getMpn()) return $product->getMpn();
else $this->skip();
?>

Calculate the sum of all quantity available for a configurable product:

<?
$childProducts = Mage::getModel('catalog/product_type_configurable')->getUsedProducts(null,$product);
$stock_count=0;
foreach($childProducts as $child){
$stock_count+=(int)Mage::getModel('cataloginventory/stock_item')->loadByProduct($child)->getQty();
}
return "<g:quantity>".$stock_count."</g:quantity> ";
?>

Use custom options

Create custom options

Data Feed Manager also allows you to create custom functions.

To create your own functions, go to:
Catalog › Data Feed Manager › Custom functions

Here is how to proceed:

1. Create a new option.
   

   

2. Fill in the option name with the name of your custom option.
   

   

3. Define the number of additional parameters expected by your custom option.
   

   

4. Add your custom script - No need to add the PHP tags (<? ... ?>)

   

5. Add the new custom option into your data feed template.

Examples of custom options

Pad an attribute to a certain length with another string:

<?
/*
* {{ean,[str_pad],[10],[0]}}
* when ean is 12345, then the output is 0000012345
*/
return str_pad($self,$param[1],$param[2],STR_PAD_LEFT)
/*
* could also be used as a inline function
* {{ean,[str_pad($self,10,0,STR_PAD_LEFT)]}}
*/
?>

Format a number:

<?
/*
* {{price,[number_format],[2],[,]}}
* when price is 9.99345, then the output is 9,99
*/
return number_format($self,$param[1],$param[2],' ')
/*
* could also be used as a inline function
* {{ean,[number_format($self,2,',',' ')]}}
*/
?>

Useful links for Google Shopping

Google Shopping allows you to create data feed in destination of Google Shopping.

Here are some tips which will be useful to create your data feed.

First, we recommend you to look at these 2 links which will be helpful:

• Google Shopping's feed specifications
• Google Shopping's taxonomy

Once your data feed has been uploaded to your Google Merchant account, you can check what products have been added to the Google Shopping index:
https://www.google.com/products?authorid=[your Account ID]

File format with Google Shopping

Google Shopping handles CSV or XML file format (More information).

The following explanations will only concern the most used method: XML files.

File names should remain consistent for all updates.

Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Required attributes with Google Shopping

Required attributes with Google Shopping depend on what kind of products you want to submit.

For complete information about required attributes, please refer to the dedicated page on the Merchant Center.

Here are the most frequent required attributes used by Google Shopping.
(Between brackets, specific name for XML files)

Recommended attributes with Google Shopping

Here are some attributes (non-exhaustive list) recommended by Google Shopping that we think could be quite useful to add in your template:
(Between brackets, specific name for XML files)

Example of template with XML format with Google Shopping

Here is an example of template in XML format:

How to create a data feed in Google Merchant Center?

In order to submit your products to Google Shopping, you'll have to create a data feed in your Google Merchant Center.
Once you're login into Google Merchant Center, go in the Data feeds section.

You can choose between creating a New Data Feed and a New Test Data Feed.

We recommend that you start by creating a New Test Data Feed.

After clicking on New Test Data Feed, you have to choose the target country and a name for your data feed ("datafeed_test" by example).

You can confirm by clicking on Save changes.

Now you can see your data feed appears in the data feeds list.

Next step will be to setup this data feed so it will import the data feed you created with the extension Simple Google Shopping in your Magento store.

Click on the link Create schedule. You are now accessing the schedule upload options.

You can manage the Google Merchant's importation frequency. You can choose to import you data feed monthly, weekly or daily at a specific time.

Paste your data feed's URL in the field Feed URL.

Click on Schedule and fetch now to start the importation and the process of your data feed.

Your data feeds' status shows Processing...

After a few minutes, Google Merchant Center shows you the number of inserted items and offers you to display errors in your data feed.

Click on View errors will show you errors in your data feed.

Google Merchant Center discerns 2 kinds of errors: errors and warnings.

As long it will remain errors in your data feed, Google Merchant will not display your items in Google Shopping.

It's very important to read the errors descriptions. It will help you to understand and fix quickly your data feed's issues.

Once the errors fixed, you'll be able to proceed to the creation of a new data feed (not a test one this time) which will perform the processing and referencing of your items by Google Shopping.

File format for Shopping.com

Shopping.com handle CSV or XML file format.

For CSV files, data should be enclosed within double quotation marks ( " ), and tab as field separator.

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>.

File name should remain consistent for all updates. (e.g. MerchantnameSDC.csv). Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Required attributes for Shopping.com

These 9 attributes are required. Products without these values will not display on Shopping.com:
(Between brackets, specific name for XML files)

Recommended attributes for Shopping.com

Here are some attributes (non-exhaustive list) recommended by Shopping.com we think are quite useful to add in your template:
(Between brackets, specific name for XML files)

Example of template for Shopping.com with XML format

Here is an example of template for a website selling t-shirts:

Header:

<?xml version="1.0" encoding="ISO-8859-1"?>
<Products>

Pattern:

Footer:

</Products>

File format for Bing Shopping

Bing Shopping doesn't support XML file format. You should create TXT file format.

HEADER (the line with attribute's names) is required by Bing Shopping.

Data should be enclosed without any characters, and you should use tab as field separator.

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>
• No $ sign in the price values and no lbs in shipping weights (only numbers, limited to 2 decimal places)

File name should remain consistent for all updates. Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Bing Shopping recommends to use bingshopping.txt as a file name.

Required attributes for Bing Shopping

Bing Shopping requires these 6 attributes:

Recommended attributes for Bing Shopping

Bing Shopping highly recommends to use these attributes in your template:

Example of template for Bing Shopping with TXT format

Here is an example of template:

File format for Shopzilla

Shopzilla doesn't support XML file format. You should create TXT file format.

HEADER (the line with attribute's names) is required by Shopzilla.

Data should be enclosed without any characters, and you should use tab as field separator.

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>

File name should remain consistent for all updates. Do not include the date in your file name.
File name cannot contain spaces or illegal symbols.

Required attributes for Shopzilla

Shopzilla requires 15 attributes in the data feed, but only 5 must contain data. Others are highly recommended by Shopzilla.

WARNING: these 15 attributes must respect this order:

1. Category ID
2. Manufacturer
3. Title
4. Description
5. Product URL
6. Image URL
7. SKU
8. Availability
9. Condition
10. Ship Weight
11. Ship Cost
12. Bid
13. Promotional Code
14. UPC
15. Price

Bold attributes above must contain data.

Here are the 5 required attributes:

Recommended attributes for Shopzilla

Shopzilla highly recommends to use these attributes in your template:

Example of template for Shopzilla with TXT format

Here is an example of template:

File format with Amazon

Amazon doesn't support XML file format. You should create TXT file format.

HEADER (the line with attribute's names) is required by Amazon.

ATTENTION: Amazon requires an extra-header, which allows Amazon to identify what kind of products is in you data feed, and the actual used version. Here is an example concerning Home category products:

TemplateType=Home Version=2012.0228 This row for Amazon.com use only. Do not modify or delete.

In order to use these specific extra-header, Data Feed Manager has a specific field named Extra header:

Data should be enclosed without any characters, and you should use tab as field separator.

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• Characters such as ©,®,?,etc
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>

File name should remain consistent for all updates. Do not include the date in your file name.

Information groups with Amazon

Amazon distinguish different information groups to describe the products you'll send them in your data feed.

Some groups are generic and suitable for all types of products:

• Basic Product information
• Offer Information
• Sales Price information
• Item discovery information
• Image Information
• FBA (Fulfillment By Amazon)
• Variation information (if your Product is available in different variations)
• Product Dimensions
• Infrequently used attributes

Beside these generic groups, there are specific groups depending on your products' categories.

Here are specific groups from Home category:

• Product specific attributes included in the "ArtAndCraft"
• Product specific attributes included in the "Kitchen"
• Product specific attributes included in the "Indoor Home"
• Product specific attributes included in the "Outdoor Home and Garden"
• Battery Information

The very first thing to do before creating your Amazon data feed is to identify which kind of products your Magento catalog contains.

Once this is done, you'll have to refer to the Amazon Browse Tree Guide (Amazon BTG) matching this product category to create your data feed in the best way.

For example, if you're selling furniture, you'll have to refer to Home Amazon BTG, which matches with following themes:

• Art and Craft
• Kitchen
• Indoor Home
• Outdoor Home and Garden

We'll use this particular example for following explanations.

Required attributes with Amazon

Usually, Amazon requires these 10 attributes in the data feed.

WARNING: These 10 attributes have to be in the data feed unless Amazon will reject it.

Recommended attributes with Amazon

Amazon highly recommends to use these attributes in your template:

Detailed description of your offer (limited to 2000 characters).

Don't use special characters.

File format with Price Grabber

Price Grabber doesn't support XML file format. You should create TXT file format.

HEADER (the line with attribute's names) is required by Price Grabber.

Data should be enclosed without any characters, and you should use tab as field separator.

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>

File name should remain consistent for all updates. Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Required attributes with Price Grabber

Price Grabber requires some attributes regarding to the kind of product you're selling in your store.

For example, Home & Personal Products requires 9 attributes, where Tech Products & Software only requires 7 attributes (not the same).

Please have a look at the Price Grabber Integration Guide to know exactly which attributes are required for your products.

However, here are the most current required attributes:

Recommended attributes with Price Grabber

Price Grabber highly recommends to use these attributes in your template:

File format with Nextag

Nextag handles TXT file format.

HEADER (the line with attribute's names) is required by Nextag.

Data should be enclosed without any characters, and you should use pipe (|) as field separator.

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>

File name should remain consistent for all updates.

Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Required attributes with Nextag

Here are the required attributes for Nextag:

Recommended attributes with Nextag

Nextag highly recommends to use these attributes in your template:

File format with Twenga

Twenga handles CSV/TXT or XML file format.

About CSV/TXT files:

• data shouldn't be enclosed
• you can use either tab, semicolon, comma or pipe as field separator.

About XML files:

• the data feed must be UTF-8 encoded (<?xml version="1.0" encoding="UTF-8" ?>)
• catalog tags (<calalog>...</catalog>) must enclose the content.
• each product must be in product tags (<product>...</product>)

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>.

File name should remain consistent for all updates. (e.g. MerchantnameSDC.csv).

Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Required attributes with Twenga

These 7 attributes are required.

Products without these values will not display on Twenga:

Recommended attributes with Twenga

Here are recommended attributes by Twenga:

Example of template with XML, CSV and TXT format with Twenga

Here is an example of template with XML format:

Here is an example of template with CSV format:

Here is an example of template with TXT format:

File format with Idealo

Idealo is used to work with CSV files.

Data shouldn't be enclosed.

You can use either tab, semicolon or pipe as field separator.

The CSV file must contain a header line describing each column's name.

Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Required attributes with Idealo

These attributes are required by Idealo.

Products without these values will not display on Idealo:

Recommended attributes with Idealo

Here are attributes recommended by Idealo:

Example of template with CSV format with Idealo

Here is an example of template with CSV format:

Numéro d'article (interne);EAN (European article number);Référence fabricant (HAN);Marque / Fabricant;Produit;Catégorie;Prix en ¤ (TVA incluse);Délai de Livraison;Frais de port;URL produit;URL photo;Ecotaxe (si non incluse dans le prix);Prix Promo (facultatif)
40101966;3165140580113;GSB 14.4-2-LI;FBC BOSCH;PERCEUSE VISSEUSE 14,4V 1,3AH LI-ION;Outillages électroportatif à batterie;   518,87;Livrera sous 3 jours ouvrables après réception du paiement.;4;https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;   418,87
40101915;0000401019151;BHP453RHEX;MAKITA;PACK PERCEUSE A PERCUSSION 18V 1,5AH LXT;Perceuses, visseuses et boulonneuses;   164,00;Livrera sous 3 jours ouvrables après réception du paiement.;4;https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;   16,00
43302205;3148518627948;CPE.PB;FACOM;LOT DE 2 PINCES "PACK PREMIER";Pinces standards et coupantes;    68,90;Livrera sous 3 jours ouvrables après réception du paiement.;0 (si frais de port gratuits);https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;    55,90
46600252;0000466002525;1-94-747;STANLEY TOOLS;SERVANTE DE CHANTIER LOCK & STOCK FATMAX;Boite à outils;   1122,95;Livrera sous 3 jours ouvrables après réception du paiement.;4;https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;
45900043;3253561956294;1-95-629;STANLEY TOOLS;GILET PORTE-OUTILS FATMAX XTREM;Saccoches et porte-outils;    53,20;Livrera sous 3 jours ouvrables après réception du paiement.;4;https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;    43,20
44800848;9999999999999;0-10-825;STANLEY TOOLS;COUTEAU CUTTER PLIABLE FATMAX;Cutteurs et ciseaux;    17,95;Livrera sous 3 jours ouvrables après réception du paiement.;4;https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;
46600415;3253561974755;1-97-475;STANLEY TOOLS;JEU 2 TRETEAUX PLIABLES COMPACTS;Etais et trétaux de maçon;    84,45;Livrera sous 3 jours ouvrables après réception du paiement.;0 (si frais de port gratuits);https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;    80,00
60800432;3253561951480;1-95-151;STANLEY TOOLS;LAMPE TORCHE LED PETIT MODÈLE;Torches, ampoules, et éclairage;    16,67;Livrera sous 3 jours ouvrables après réception du paiement.;4;https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;
42606588;3253560975456;0-97-500;STANLEY TOOLS;CLE A MOLETTE A CLIQUET FATMAX;Clés de serrage à ouverture variable;    14,23;Livrera sous 3 jours ouvrables après réception du paiement.;4;https://www.idealo.fr/exemple;https://www.idealo.fr/exemple-exemple.jpg;0,1;

File format with eBay

eBay handles CSV/TXT or XML file format.

About CSV/TXT files:

• data must be enclosed with double quotation marks (")
• if you intend to use the double quote character ( " ) itself and not as a delimiter, it should be repeated. For example, '15" TV' should be entered as "15"" TV".
• you must use comma as separator in CSV files, and either tab, semicolon, comma or pipe in TXT files.

About XML files:

• the data feed must be UTF-8 encoded (<?xml version="1.0" encoding="UTF-8" ?>)
• each product must be in product tags (<product>...</product>)

The following characters are forbidden within any cell:

• Smart Quotes Character ("?")
• Carriage Returns Character
• New Line Characters
• Any character whose ascii value is less than 32, e.g. Carriage Returns (ascii 10), Newline (ascii 13)
• HTML, CSS, or any other formatting languages, e.g. "\n\r", <p>, <br>.

File name should remain consistent for all updates. (e.g. ebay.csv). Do not include the date in your file name.

File name cannot contain spaces or illegal symbols.

Required attributes with eBay

These 9 attributes are required by eBay. Products without these values will not display on eBay.
(between brackets, the name to use with XML files)

Recommended attributes with eBay

Here are attributes recommended by eBay:
(between brackets, the name to use with XML files)

Example of template with XML format with eBay

Here is an example of template with XML format: