Shopify CSV import: run a small new-product test before the full file
Use a current store template, preserve source values and verify a small draft-product import before repeating the workflow.
Start with the store's own import format
For a Shopify CSV import, first obtain the product CSV example or export format available in your store's product workflow. Compare it with your supplier file before changing headers. If the supplier can supply a compatible file, you may not need another converter. For a small new-product list, mapping columns in an existing spreadsheet is a practical route without conversion-service charges. Work on a copy, retain the original supplier file and limit the first test to a few products that you can check individually in the store afterward.
Separate new products from updates
Decide whether the job creates products or changes products already present. Those tasks have different risks and must not share an unexamined import file. Check the identifiers and handles already in the store: Shopify ignores products whose handle matches an existing product unless you select Overwrite products with matching handles, which replaces existing values for every column in the CSV. A new-product conversion cannot inspect your existing catalog unless it is connected to it. Avoid assuming that a different filename makes a product new. Keep a source list of the products in your test so you can compare exactly what the import created or changed before proceeding further.
Prepare the values before the first upload
Preserve SKUs and barcodes as text, including existing leading zeros. Confirm that Title, SKU and Price describe the intended product and that the prices already use the store's currency. Decimal notation is separate from currency conversion: 24,90 can be reformatted to 24.90 without changing its currency. Confirm any optional barcode field from the supplier. If a spreadsheet has already removed zeros, return to the source rather than guessing their length. Save the CSV as UTF-8 with commas between columns, as Shopify requires, and quote any value that contains a comma or line break.
Test simple products before broader structures
Use products with one default variant for a simple first test. Size/color choices, images and inventory require additional fields and relationships; do not treat them as harmless extra columns. If they are part of your task, use the store's documented schema or a tool that supports that exact workflow. Keep products in draft during preparation: Shopify's Status column accepts draft, and if the column is missing, imported products are set to active. A draft status helps with review but does not prove that identifiers, prices or product relationships are correct, so still compare the imported product records with the source list.
Reconcile the outcome before importing more
Use Shopify's activity log and any reported line errors to investigate the run, then check the actual product records; the upload email is not a record of every change. Compare count, title, SKU, barcode, price and status for every test product. A file being accepted does not establish that the intended products were created correctly. Keep rejected rows separate with their reasons rather than repeatedly submitting the entire original list. Before a full run, confirm which rows have already been processed and avoid accidental overlap. Retain the source, mapped file and test notes so a later supplier revision can be distinguished from a repeated import of the same products.
Keep a test manifest outside Shopify
Write down the handful of source products selected for the first run, their intended handles and their expected titles, identifiers, prices and status. After the run, inspect each actual product record and mark its outcome in that list. Shopify's upload email is not an item-by-item change report, and its admin does not provide a history of past imports. Use the activity log and reported line errors when investigating differences. Keep the manifest with the exact CSV so a subsequent file can exclude products already created or clearly identify a deliberate update rather than repeating the first test blindly.
Check publication separately from record creation
A product can be created correctly but have the wrong status for the preparation stage. Include Status with draft for a new-product review file and inspect that value on the resulting product record. Do not assume that missing status means draft; Shopify defaults missing Status to active. Review any publication choices shown during import as a separate decision. Once the small test is checked, prepare the remaining new products from the same mapping and verify that none of their handles already exists. Keep overwrite unselected for a create-only job and inspect any ignored-line messages before treating the remaining run as complete.
Where Rowmoss fits
Rowmoss maps a supplier CSV to new single-variant draft products for manual import; it does not connect to Shopify. Free review needs no account and shows the first twenty transformed rows, twenty issues, total counts and a complete skipped-row list, without a full converted CSV. Sign in and use one credit to unlock a validated revision. Input limits are 1 MiB, 2,000 rows, 30 columns and 1,000 characters per cell, using UTF-8 or Windows-1252 and comma or semicolon separators. XLS/XLSX, TSV, UTF-16, images, size/color variants, inventory, updates, synchronization and saved supplier templates are unsupported. You choose price notation; currency is not converted.
Preview your supplier CSV free Pricing details
Written by Zijian Xiao. Check the source, review the import details, and verify the resulting Shopify product records.