Why rows are skipped in a Shopify import

Skipped rows are not errors — they are rows that Csvio intentionally did not process, usually because they don't meet the requirements for the selected import mode. The Done screen lists exactly which rows were skipped and why, right under the result summary.

Why are rows skipped in Create mode?

Most often because the row's SKU is already in your store. The other reasons are a duplicate SKU in the file, a blank row, or a missing title.

Already in your store Create only adds products that don't exist yet. If a row's SKU matches a product you already have, that row is skipped and the existing product is left untouched — this is the normal, expected outcome, not a failure. See Understanding import modes. To actually change that product, use Bulk edit or, for a supplier you've saved before, Resync.

Duplicate SKU within the file If two or more rows have the same SKU, Csvio processes the first one and skips the rest. This prevents creating duplicate products.

Blank or empty rows Rows with no data in any mapped column are skipped automatically.

Missing title When creating a new product, a row without a value in the Title column can't be processed and is skipped.

Why are rows skipped in Bulk edit mode?

Usually because no product in Shopify matches the row's match key. A blank, duplicated, or space-padded match key also causes a skip.

No matching product in Shopify Bulk edit only updates existing products. If the match key value (SKU, Barcode, Handle, Variant ID, or Product ID) doesn't correspond to any product in your store, the row is skipped.

Missing match key If the match key column is blank for a row, Csvio can't look up the product and skips it.

Duplicate match key in the file Only the first occurrence of a duplicated match key is processed.

Trailing spaces in the match key A SKU of "ABC-123 " (with a trailing space) won't match "ABC-123" in Shopify. Trim whitespace from your identifier columns.

Not skipped: a row that kept its photos If a photo on the row wasn't in the files you uploaded, that product keeps the photos it has. The row itself still runs and every other mapped column is updated, so it counts as a success rather than a skip. See Upload product photos from your computer.

Why are rows skipped in Bulk delete mode?

Because no product in Shopify matches the row's identifier, or the identifier is blank.

No matching product in Shopify If no product matches the identifier in the row, there's nothing to delete. Rows that don't match anything are skipped rather than treated as an error.

Missing identifier Rows with a blank value in the match column are skipped.

Where can I see which rows were skipped?

The Done screen at the end of an import breaks down the result and, when rows were skipped, shows a table with the row number, SKU, product name, and the reason for each one. If you ran a preview, skipped rows appear there too with a "Skipped" label and reason before you commit to the import.

How can I reduce skipped rows?

• If you expect a row to update an existing product, confirm you're running Bulk edit, not Create — Create will skip it by design.
• Make sure every row has a value in the title column (for Create) or the match key column (for Bulk edit / Bulk delete).
• Remove duplicate identifiers from your file, or consolidate them into a single row.
• Check for leading or trailing spaces in your identifier columns.
• Verify that the match key you selected (SKU, Barcode, etc.) is the one your Shopify products actually use.