Shopify product import: choose a workflow for your catalog structure
Separate simple new products from variants, images and updates before selecting a spreadsheet or conversion tool.
Classify the import before selecting a tool
A Shopify product import should start with a list of the operations you need. Are you creating new simple products, creating size/color variants, attaching images, changing inventory or updating existing records? Do not assume one converter covers all of these. If you only have a small list of new simple products, manual entry or a carefully mapped CSV can avoid a conversion purchase. Obtain Shopify's current product CSV template and note its required fields: for new products only Title is required, and URL handle is also required when you add variants. A broader catalog task needs a workflow whose documented scope matches those operations and relationships.
Review the supplier's row meaning
Ask what one row represents in the source file. It may be a product, a size option, a stock position or a repeated listing with a different barcode. Compare several related rows rather than judging by the header alone. Repeated SKUs can mean duplicate data or a source problem, and their handling should be explicit. Do not collapse size/color rows into a single product merely because titles match. Keep the original file and note any supplier clarification so later changes do not silently reverse decisions made during this preparation pass.
Define identity before building the output
Treat title, SKU, barcode and handle as distinct fields. Titles are descriptive text; they do not automatically provide a stable identity. Preserve existing SKU and barcode zeros by importing them as Text in a spreadsheet. Check whether products or handles already exist in the store before assuming the file creates only new records. A standalone file tool cannot establish that store state for you. Keep a working reconciliation list of source rows and intended product records, especially if you split a larger supplier export into several import files for review.
Compare manual mapping with automation
A spreadsheet can map a simple supplier list into a store template without an additional conversion fee. You remain responsible for values, quoting, identifiers and every destination column, and Shopify warns that sorting a product CSV in a spreadsheet can disassociate variants or image URLs. A specialized converter may offer clearer validation and a preview for a narrow scope. Broader import tools may fit more complex operations, but inspect their actual supported formats and pricing separately. Do not pay for a transformation before you know whether it handles your variants, images or updates. A successful conversion of four basic columns is not evidence that the rest of a catalog workflow is supported.
Test the intended behavior in the store
Prepare a small representative file and inspect the import preview before confirming. Check the actual product records after the test, including price, identifier strings and status. If the job is for new products, verify that it did not target existing records. Compare the products actually created with your source list, using the store's activity log and any line errors Shopify reports, and keep rejected rows for correction. Correct the source or mapping before repeating the task; importing overlapping files without tracking outcomes can create confusion. Save the final mapping notes alongside the source so the next supplier revision receives the same deliberate scope review.
Make an operation matrix from supplier examples
Pick several real source rows and write down the intended result for each: a new product, another option of an existing product, an image attachment, a stock change or an update. Group them by operation before choosing a file workflow. A list containing a red and a blue shirt might describe variants of one product or two separate products; the title alone cannot decide that. Ask the supplier or catalog owner to resolve the relationship. Keep that decision with the source map so a converter's single-variant output is used only for rows whose intended structure actually fits it.
Keep the broader product model intact
For a richer catalog, preserve the relationship between a product, its variants and any image rows while preparing the official template. Do not independently sort one identifier or price column, and avoid flattening all related rows into one per title. Shopify supports richer product CSV fields, but Rowmoss intentionally omits those operations. If the job includes inventory across locations, use the documented inventory workflow rather than pasting stock values into an unrelated product field. Check a representative product with all required relationships in the destination before expanding the job; four correctly mapped basic columns do not validate a complex catalog import.
Where Rowmoss fits
Rowmoss handles only new single-variant draft products, not images, size/color options, inventory changes, existing-product updates, store synchronization or saved supplier templates. It maps Title, SKU, Price and optional Barcode; you explicitly select dot-decimal or European pricing without currency conversion. Supply one UTF-8 or Windows-1252 CSV with comma or semicolon separators, up to 1 MiB, 2,000 data rows, 30 columns and 1,000 characters per cell; XLS, XLSX, TSV and UTF-16 CSV are unsupported. Anonymous preview includes twenty transformed rows, twenty issues, total counts and the skipped-row list. Complete CSV download needs sign-in and a credit.
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.