Feed errors and how to fix them

Row errors: the row is skipped

• No SKU: every row needs your own product ID.
• No product name.
• No product address, or one that does not start with http:// or https://.
• No price, or a price we cannot read.
• A price of zero or below.
• The same SKU twice: we keep the first row.

If more than 5 % of the rows have errors, the whole run stops.

Warnings: the row is imported

• The before price is not above the current price: we ignore it.
• The member price cannot be read, or is not below the price: we ignore it.
• The delivery cost cannot be read: we show it as unknown.
• Unknown stock status: we treat the row as out of stock.
• Invalid GTIN or EAN: we ignore the code.
• Unknown condition: we treat the product as new.

Stopped runs: nothing is changed

When a run stops, we change nothing. Your previous prices and offers stay live, so a broken export never empties your listing.

• The feed address is missing, is not https:// or ftp://, or contains a date or timestamp.
• A price or currency is not in EUR.
• We could not read the file, for example a zip with more than one file in it, or broken XML or JSON.
• The feed has no products, or no row we could import.
• More than 5 % of the rows have errors.
• You have at least 20 offers with us, and the new feed has less than 50 % of them. This protects you from a half-finished export.
• We could not fetch the feed: the server did not answer with the file, it was larger than 200 MB, or the FTP login failed.
• Something went wrong on our side. We are told automatically and run it again.

Why we reject addresses with a timestamp

An address with a date or time in it changes with every export, so we cannot fetch the same feed again, and an old address can point at old prices. Give us one address that always returns your latest feed.

The portal shows your last run with its errors and warnings.

Open the merchant portal