What should I do if I encounter an incorrect row separator in my feed?

This error usually happens when the structure of the feed file changes or a specific row becomes corrupted. First, download and review the latest version of the file to check for formatting problems, such as broken rows, misplaced line breaks, or a row unintentionally split into two (for example, a Description field spilling onto the next line). An empty line at the end of the file does not normally trigger this error. If the file appears normal, the row separator may not match the format of the source file, or the supplier may have changed the file’s encoding or formatting without notice. In some cases, an encoding artifact such as a  prefix before the first column name can affect how the file is read; re-download or regenerate the file with the correct encoding and test it again.

If the feed uses a semicolon-delimited CSV, verify that the source is a valid downloadable file and that the delimiter matches the file. If the feed works when uploaded manually but fails through a URL or FTP connection, compare the files because the retrieved source may differ or contain unexpected encoding or formatting changes. Also check that the configured file path, including capitalization, matches the source path.

Contact support with the feed name and a copy or link to the latest file so the team can inspect it. The row separator may need to be adjusted manually on the backend. Support can also verify whether the issue is caused by a corrupted row, encoding or formatting changes, an invalid source URL, or another source-file problem.

If the feed is fixed, run the next scheduled or manual update and verify that the products were updated in the destination store, not only in the feed preview or change log.

Updated on: 27/07/2026