What CSV format does Shopify require?

Shopify expects a UTF-8 encoded CSV with comma-separated values. The file must follow Shopify's exact column schema — Handle, Title, Body (HTML), Vendor, Product Category, Variant Price, Variant SKU and around 40 more columns. Missing or mis-named columns cause the import to fail.

How many products can I import via CSV at once?

Shopify accepts CSV files up to 15 MB. In practice that is a few thousand to tens of thousands of variants, depending on description length. For very large catalogs, split the file into chunks or use the Admin API.

Can I update existing products with a CSV import?

Yes — Shopify matches on the Handle column. Rows with existing handles update those products; new handles create new products. Always include the Handle to avoid accidental duplicates.

Why do my images not import?

Image URLs must be publicly accessible (no auth, no local paths). Use a CDN or publicly hosted storage. Shopify downloads each URL and stores a copy — if the URL 404s or requires login, the image silently fails.

How do I handle product variants in the CSV?

Each variant is its own row. The first variant carries the product-level fields (title, description, vendor). Subsequent variants share the same Handle but leave product-level fields blank and fill Option1/Option2/Option3 values for the variant axis.

When should I stop using CSV and switch to a PIM?

Once you are importing from multiple suppliers, selling on multiple channels, or rebuilding the same CSV every week, you have outgrown CSV. A PIM like Productbay ingests any supplier format, enriches data with AI, and publishes to Shopify automatically.

Shopify CSV Import Guide: Fix Errors Fast

The Shopify CSV import is the default way most retailers move product data into Shopify — and almost every team hits the same wall within a few months. The format is rigid, the failure modes are silent, and every supplier sends data in a different shape.

This guide walks through how Shopify’s CSV import actually works, how to build a file that imports cleanly on the first try, the most common errors and their fixes — and when it is time to leave CSV behind entirely.

Why CSV is still the default for Shopify imports

CSV is universal, supported by every tool, and Shopify’s built-in importer accepts it natively. For small catalogs or one-off migrations, CSV is the fastest path:

Flat and simple. One row per variant, one file per catalog — no API keys, no integrations.
Export and edit anywhere. Open in Excel, Google Sheets or Numbers and edit inline.
Reversible. Export the current catalog, edit, re-import — the format is symmetrical.
Ubiquitous supplier support. Most suppliers can send CSV, even if the columns never match Shopify’s schema.

Step-by-step: importing products via CSV

Download the Shopify template. In Shopify Admin → Products → Import, download the sample CSV. Never build the schema from scratch — use the template.
Map supplier data to Shopify columns. Every supplier field needs to land in the correct Shopify column. Title, Body (HTML), Vendor, Variant Price, Variant SKU, Image Src are the essentials.
Handle variants correctly. Each variant is its own row with the same Handle; only the first row carries product-level fields (title, description). Later rows fill the Option columns only.
Check encoding and delimiters. Save as UTF-8 with comma delimiters. Excel’s default “CSV” on some systems uses semicolons or Windows-1252 — both break the import silently.
Upload and review the preview. Shopify shows a preview before committing. Do not skip it. Every error caught here saves an hour of cleanup later.
Run a test import with 5–10 rows. Validate structure, images and variants on a handful of SKUs before pushing thousands.

Advanced methods beyond the basic CSV

Once you have more than a few hundred SKUs or more than one supplier, the basic CSV flow hits its limits. Common next steps:

Scheduled CSV imports. Drop files on an SFTP and have them picked up automatically on a schedule.
Template transformation scripts. Normalize each supplier’s format into Shopify’s schema with a reusable script.
Admin API bulk operations. For very large catalogs, skip CSV entirely and use GraphQL bulk operations — higher throughput, better error handling.
AI enrichment before import. Fill missing attributes, generate descriptions and translate content before the data ever reaches Shopify.
PIM as the single entry point. Ingest supplier data in any format, enrich once, publish to Shopify and every other channel.

Common errors and how to fix them

Almost every broken import traces back to one of these issues:

Problem	Cause	Solution
Special characters show up as gibberish	File encoded as Windows-1252 instead of UTF-8	Save explicitly as “CSV UTF-8” from Excel or Numbers
Images do not appear after import	Image Src URL is private, behind auth, or 404	Host on a public CDN; test each URL in an incognito window first
Variants collapse into one product	Option1 Name/Value missing, or Handles differ	All variants share the same Handle; each has unique Option values
Existing products get duplicated	Handle column missing or altered	Always preserve the original Handle for updates
Import aborts silently halfway	Hidden line breaks or malformed commas inside fields	Wrap text fields in double quotes; escape internal quotes by doubling
Prices off by factor of 100	Locale-formatted numbers (e.g. “19,99”) parsed as text	Use dot as decimal separator; no thousand separators

When to move beyond CSV

The rule of thumb: if you are rebuilding the same CSV every week from the same suppliers, you are doing manual ETL. That is exactly what a PIM is built to eliminate.

The clearest signals it is time to switch:

You import from more than 2–3 suppliers with different formats.
You sell on more than one channel (Shopify + Amazon + OTTO) and rebuild files for each.
You run weekly or daily updates that someone has to stitch together by hand.
You need to enrich data — fill missing attributes, translate, generate descriptions — before publishing.

How Productbay replaces the CSV workflow

Productbay is an AI-native PIM built specifically for Shopify retailers. Instead of wrangling CSVs, you connect your suppliers once and the pipeline runs continuously:

Ingest any format. CSV, Excel, FTP, API, scraped supplier portals — Productbay normalizes all of it.
AI enrichment at scale. Auto-fill missing attributes, generate SEO descriptions, translate to every market, categorize automatically.
Native Shopify publishing. Direct API connection, no file uploads. Variants, metafields, images, SEO fields all mapped.
Multi-channel from day one. The same enriched data flows to Shopify, Amazon, OTTO and any other channel in parallel.

For retailers past the “one catalog, one CSV” stage, the payoff is immediate: the weekly file-wrangling disappears, and products go live faster with better data.

The bottom line

Shopify’s CSV import is a solid starting point and will always have its place for small catalogs and one-off migrations. But it was designed for a single-channel, single-supplier world. If your reality is messier than that — multiple suppliers, multiple channels, weekly updates — CSV becomes the bottleneck. A PIM like Productbay turns that bottleneck into an automated pipeline.

Shopify CSV Import: The Complete Guide for Online Retailers