Preparing Products for a Shopify Upload: A Step-by-Step Guide

Preparing products for a Shopify upload means getting your supplier data, variant structure, and image files into a consistent state before your upload team starts. For example: a supplier sends three spreadsheets and 400 images named with internal product codes, and two days later the team asks for a revised file because sizes were combined, images can't be matched to SKUs, and product names don't follow your store's rules. That round of revision is avoidable. The five steps below cover what to sort out first.

Key takeaways

• Preparing products for a Shopify upload means cleaning supplier data, fixing variant structure, and organizing image files before they reach your team.
• The most common cause of a paused upload job is image files named with supplier codes instead of SKUs: the team has to manually match each image to its product row.
• Variant structure from suppliers usually needs rebuilding: Shopify requires separate option dimensions (Size, Color) rather than combined values like "Red / Large."
• A short naming brief covering title format, product type values, tag structure, and collection rules prevents most rounds of revision.
• You can hand the preparation work over too: some merchants send raw supplier files and let the upload team clean and standardize the data as part of the job.

Preparing products for a Shopify upload: what to sort out first

Before your upload team can start, five things need to be in order:

1. Your supplier data files are in a consistent, readable format (no merged cells, no one-row-per-product when each product has multiple variants).
2. Your product titles and naming rules are agreed: what goes in the title field, what values the product type field uses, and how tags are formatted.
3. Your variant structure is rebuilt from the supplier's combined option columns into Shopify's separate-option format.
4. Your image files are named and organized so the team can match each image to its product row without a manual lookup.
5. You have a brief the team can check against: a short document that captures the above, so they apply your rules consistently across every product.

Each step below explains the common issues at that stage and how to resolve them.

Step 1: Audit your supplier data files

Open every supplier file before sending it to your upload team. The issues that slow jobs down most are the ones you can spot in 10 minutes.

The most common problems in supplier spreadsheets:

• Merged cells. Excel files from suppliers often merge cells across rows or columns (for example, a product title merged across all its variant rows). A merged cell typically produces one value and one blank when processed, rather than the value repeated on each row.
• Inconsistent column names. A file that uses different names for the same field across columns (for example, "Color" in one column and "Color Variant" in another) needs a manual mapping step before the team can start.
• Combined options. A single "Size / Color" column (with values like "Red / Large" and "Blue / Small") needs to be split into separate columns before upload. Step 3 covers how to handle this.
• One row per product instead of one row per variant. Shopify's CSV format requires one row per variant, with the handle repeated on every row. A product with four sizes needs four rows in the upload file, not one.
• Missing required fields. Shopify requires at minimum a title, a status, and a price. A file with blank price cells will either fail to upload or create products with a $0 price.

Shopify's CSV column reference (as of October 2026, per Shopify's product CSV guide) lists every required and optional field. Checking your file against it before sending takes less time than a round of revisions.

Step 2: Agree your naming rules in advance

The most common reason an upload team asks for a revised brief is undefined naming rules. Before the job starts, decide:

• Title format. Does your store use "Brand Name + Product Name" or "Product Name + Key Detail"? For example, "Acme Red Cotton T-Shirt" or "Classic Cotton T-Shirt." Shopify displays the title exactly as entered, so consistency across products matters.
• Product type values. If your store uses smart collections based on product type, every value must match exactly. "Polo Shirt", "polo shirt", and "Polo shirt" are three different values in Shopify's collection conditions.
• Tag structure. Tags are case-sensitive in Shopify. Decide on casing and format before upload: for example, "color:red" and "size:large" as prefixed tags rather than plain "red" and "large".
• Collection membership. Manual collections need products added explicitly. Smart collections pick up products automatically when their product type and tag values match the conditions. Which collections are manual and which are smart should be agreed before work starts.
• Vendor values. The vendor field appears in some storefronts and reports. Decide whether vendor values should match the supplier's brand name exactly, or whether you'll standardize them.

A one-page naming brief that captures these five decisions is the most useful document you can hand to an upload team. For a complete list of what to include, see what to send your upload team.

Step 3: Rebuild your variant structure

Shopify supports up to three option names per product (for example, Size, Color, Material) and up to 2,048 variants per product (as of October 2026, per Shopify's variants documentation). Each option is a separate column in the CSV, and each variant is a separate row.

Suppliers almost never deliver data in this format. The two most common formats and how to fix them:

Combined options ("Red / Large")

The supplier sends a single column with option values combined (for example, a column called "Option" with values like "Red / Large" and "Blue / Small"). To fix this for Shopify, split the column into separate columns: one called "Option1 Name" (Color) with values "Red" and "Blue", and a second called "Option2 Name" (Size) with values "Large" and "Small".

One row per product

The supplier sends one row per product with the variant sizes spread across multiple columns ("Size S price", "Size M price", "Size L price"). To fix this for Shopify, convert to one row per variant, with each size on its own row sharing the same handle.

If you're expecting a large file, ask your supplier to provide data with separate option columns before you receive it. An upload team can rebuild the structure for you, but it adds time at the job start if not caught early.

Step 4: Organize your images by SKU

Image files are the most common cause of a paused upload job. Suppliers typically name image files after their own internal product codes ("IMG_4592.jpg", "1042-navy-XL.jpg") rather than the Shopify handle or SKU. An upload team that receives 500 images with no clear naming convention must manually match each image to its product row, which can double the time spent on the image assignment step.

Before sending your image folder:

• Rename image files to match your Shopify handle or SKU. For example, if the handle is "cotton-polo-shirt" and the SKU for the navy large variant is "POLO-NVY-L", name the file "cotton-polo-shirt-navy-large.jpg" or "POLO-NVY-L.jpg".
• For products with multiple images (different angles, color options), name files consistently: "handle-color-angle.jpg" or "SKU-1.jpg", "SKU-2.jpg".
• Keep all variant images in a single folder rather than in subfolders by color or supplier, unless your team specifically asks for a folder structure.
• Check that every product has at least one image before sending. Products uploaded without images need a separate image assignment step later.

For more on how image preparation fits into a product upload job, see how a Shopify product image optimization service works.

Step 5: Do a final field check before you send

Before handing over your data file, check each column against Shopify's field requirements. A file with missing required fields will either fail to upload or create products with empty fields that customers can see.

Fields to verify before sending:

• Every product has a title
• Every variant has a price
• Every variant that tracks inventory has a unique SKU (Shopify needs a SKU to track stock at the variant level)
• Every product has a status set ("active" for products that go live immediately, "draft" for products that will be reviewed before publishing)
• Weight is filled in for physical products that use calculated shipping rates

The Shopify product data entry checklist covers every field a team fills during an upload job. If you're unsure which fields apply to your catalog, use it as a reference to check your file before sending.

If you'd rather hand the preparation work over entirely, our Shopify product data entry service includes supplier file cleanup, naming standardization, variant structure rebuilding, and image organization as part of the job scope.

Frequently asked questions