01 / START WITH THE FILECheck the format and the task.

Save a copy of your supplier’s sheet as a comma-separated UTF-8 CSV. If you are using Excel, choose CSV UTF-8 (Comma delimited) and check the export settings. The workspace does not read XLSX files or guess another separator.

Files can contain up to 10 MB and 50,000 source records. Keep the original file nearby so you can compare it with the output.

Preparing an update to existing products? Start from the relevant Shopify export. Updates require URL handle and Title; variant-related fields can also depend on option columns. This simple new-product example is not a replacement for the columns required by your update. Check Shopify’s current field requirements.

02 / MATCH THE COLUMNSReview every suggested match.

Open the workspace and choose Supplier example ↗ to follow this example, or load your own CSV. The tool suggests matches based on the column names. You decide whether each match represents the right data.

  • Product Name → Title: check that the cells contain product names.
  • Item No. → SKU: check that the codes are the identifiers you intend to use.
  • Retail Price → Price: check the currency and the values, not just the column label.
  • Stock → Inventory quantity: use the product CSV’s inventory quantity only for a single-location store. Multi-location inventory uses Shopify’s inventory CSV.
  • Picture → Product image URL: check the image links separately; the tool does not test whether they are online.

If a suggestion is wrong, select the correct target field. After reviewing the matches and source-only columns, acknowledge that review and choose Confirm mapping & inspect.

03 / KEEP THE FULL SOURCEChoose what belongs in each file.

The example also includes Product URL and Supplier Notes. Neither column is mapped to the target file in this example. Both remain in the source-preserving copy.

Your original file stays untouched. The separate target CSV includes the selected target fields; the source copy keeps all original columns with any edits you deliberately apply.

Supplier-specific columns are useful for your own records. Do not add arbitrary extra columns to a Shopify import file; compare its headers with the current Shopify template.

04 / REVIEW THE OUTPUTInspect the findings, then the target preview.

Review the Findings before exporting. Resolve blocking errors and make a deliberate decision about anything marked for review. Check the target preview to confirm that each value is still under the intended field.

With this example’s confirmed mapping, 12 source records become 12 target records with 5 fields. No cleaning or image-row expansion is applied. The inventory cells are blank because the original demo leaves them blank; the tool does not invent stock quantities.

First three records from the mapped demo
TitleSKUPriceInventory quantity
Hoodie with Logowoo-hoodie-with-logo45blank
T-Shirtwoo-tshirt18blank
Beaniewoo-beanie20blank

The full target file also contains Product image URL. This compact table shows four fields. Image URLs are retained, not downloaded or checked.

TARGET CSV / 5 FIELDS

The selected target fields.

A separate file with the five mappings above. Review it against your task and Shopify’s import preview.

Download the mapped demo CSV ↓

SOURCE COPY / 7 COLUMNS

All the original columns.

The unchanged demo source, including Product URL and Supplier Notes. Keep this alongside the target file.

Download the full source demo ↓

Demo data is derived from WooCommerce’s public simple-product sample, not a merchant’s catalogue. Source details · Sample licence. The downloads are examples to inspect; do not import demo products into a live store.

05 / CHECK THE DESTINATIONReview Shopify’s import preview.

Once you have checked your own output, use Shopify’s import review step before confirming an import. Compare the product count and field values with the result you intended.

Row & Record prepares and checks a file within its supported scope. It does not connect to your store, check existing store data, test image availability, or validate every Shopify import rule.

Complete WooCommerce variable, variation, grouped and external-product migration is unsupported and blocks conversion. If your file has those relationships, use an appropriate migration workflow instead of treating column mapping as a complete migration.

Shopify’s product import instructions ↗

Common questions

Is the mapping automatic?

The tool suggests field matches. You review, adjust and confirm them before a target file can be prepared. A similar-looking header is not enough to prove that the column contains the right values.

What happens to columns I do not map?

They are omitted from the separate target CSV and kept in the source-preserving copy. The original file is not overwritten.

Can I load an Excel workbook?

Save it as a comma-separated UTF-8 CSV first. The workspace does not read XLSX files. Check the export settings and the resulting first row before loading it.

Does a clean review guarantee Shopify will import the file?

No. Required and related fields depend on whether you are creating products, adding variants or updating existing products. Store data and image availability also matter. Compare the output with Shopify’s current format and check its import preview.