Adding a feed gives a failed to load feed-error

When adding a (new) feed you can use either a XML or CSV-feed to import product data.

However, there are a few common reasons your feed can not be successfully processed in ChannelEngine (resulting in a 'Failed to load feed' error).

General

  • The feed that is being add is not an online resource (/ is a local file). Because the main focus of ChannelEngine is to synchronize data from and to your own system including frequent stock updates, there is no direct option to 'upload' a file. If you want to use a static / one time usage file to enrich product information, your could always use a resource like Google Spreadsheets to store the data and make it accessible for ChannelEngine.

XML

  • Wrong product node selected:
    When using a XML-feed you need to select the 'node' on which products are grouped. Usually this is a node named something like <products> or <items>, but in the dropdown to select possible nodes, all nodes that occur more than once are displayed. If you pick the wrong one and this has no valid (possible) attributes, this might result in issues / errors. As long as you don't save anything, you can just go back, re-add the feed. Should the name of the node change in your feed, please re-add the feed as well as this will lead to errors (as the exact name / trail is stored of the product node).
  • XML tags are not closed:
    If a feed is not fully / properly generated or not all tags are closed correctly, this will result in issues with reading the data from the feed. Please check if your feed is generated / closed properly, like in the below example.
    <xml>
    	<products>
    		<product>
    			<id> </id>
    			<name> </name>
    			<stock> </stock>
    			<price> </price>
    		</product>
    		<product>
    			<id> </id>
    			<name> </name>
    			<stock> </stock>
    			<price> </price>
    		</product>
    	</products>
    </xml>
    	

CSV

  • Multiple possible delimiters:
    One of the most common problems with 'new' product feed is that we do not know the delimiter (that character that separates columns from each other) yet. When initially loading the data, the software will check which usable character ( , ; | \t) appears the most. However, a common issue is that the delimiter will be a semicolon, but the various attributes contain more comma's than semicolons (for example in descriptions). In that case the comma is picked as delimiter, but of course this fails because columns will not be separated correctly. 

    This is an issue we hope to resolve in the nearby future with an update of the CSV-parser, but we can manually add the feed for you to circumvent this issue.
  • There are only 2 attributes / columns in the feed:
    To determine the correct delimiter from the product feed, all possible delimiter characters are checked. However, if there are only 2 columns (for example for a specific price or stock feed) they are separated by 1 delimiter. Because the software checks for delimiters with a minimum count of 2, no delimiter can be set.

    This is an issue we hope to resolve in the nearby future with an update of the CSV-parser, but we can manually add the feed for you to circumvent this issue.
  • The feed contains unescaped special characters:
    Please note that a comma ( , ) and quote / quotation mark ( " ) are special characters for CSV syntax. If you do not 'escape' them, the feed might not be processed or processed correctly. If you description attributes for example contain comma's to separate parts of sentences, you need to escape them with quotation marks.

    Example: 
    This ring is made of silver, gold and has a 4 carat diamond on top. 

    This needs to be escaped, so
    "This ring is made of silver, gold and has a 4 carat diamond on top." would be correct and will result in proper parsing of the attribute value.

    Because the quotation mark is a special character, it can not be used in values unless escaped as well.

    Example:
    Size of TV screen: 50"

    The quotation mark needs to be escaped, so
    Size of TV screen: 50""
  • Delimiter has changed, feed name / id has not: 
    When a feed is added for the first time, the delimiter (the character that separates columns) is automatically selected and stored. However, should you change the delimiter in your source feed (and not add this as a new feed, but re-use a current feed) the stored delimiter will not change. 

    Please add it as a new feed if you changed the delimiter of the source feed or contact us to manually change the delimiter (if you have a lot of mappings in the current feed for example).