Most merchants hand product files to an upload service once the store theme is live. The mistake is assuming that is early enough. If the product types, collection logic and variant naming conventions have not been agreed before the first row goes into Shopify, the upload team will pause to ask questions. Each pause adds a correction cycle. This shopify upload checklist before store launch covers everything that needs to be in place before work starts.
Key takeaways
- Store structure decisions, including product types, collection logic and variant naming, must be locked before uploading begins.
- The upload team needs an agreed brief for descriptions, SEO fields and what to do when supplier data is missing.
- Image files must be named to match SKUs before they are sent; unnamed batches cause the most common upload delays.
- A free custom quote is available for first stores; the team can review a sample before the full job starts.
Why the upload starts with store structure, not products
An upload service enters products into the structure you have already set up. If that structure is not settled, every product entry requires a decision the merchant has not yet made.
A common example: a merchant sends 300 products before agreeing on collection names. The upload team creates placeholder collections, the merchant changes the names after launch, and every product needs to be re-assigned. The correction work takes longer than the original upload.
Shopify's collection system (as of November 2026) supports both manual collections, where you add products one by one, and automated collections, where products are added by conditions such as product tags. Deciding which approach to use before the first product is entered shapes how the entire catalog is structured.
The same logic applies to product types and variant option names. Shopify's product details allow free-form product types and tags, which means every inconsistency in naming has to be fixed afterward. Locking these values in a brief before work starts is the difference between a clean catalog and one that needs a cleanup job before launch.
For more on what the upload team handles once structure is agreed, see how the upload team approaches a new store.
Shopify upload checklist: store structure before launch
Work through these before sending the first file.
Collections
- Decided: manual or automated collections (or a mix)?
- Main navigation collections named and their purpose agreed (for example, "Dresses", "Sale", "New Arrivals")
- Any sub-collections or nested groupings listed
- For automated collections: the condition tags that will trigger them agreed and consistent in the product data
- A test collection created so the team can verify assignments during upload
Product types
- A fixed list of product type values agreed and written into the brief (for example, "T-shirt", "Hoodie", "Accessory" and not a mix of "T-shirt", "Tee" and "Top")
- A default product type for products that do not fit a specific category
Vendor names
- Vendor values agreed and spelled consistently (a supplier's name as it will appear in Shopify's vendor field, not how it appears on the invoice)
Variant options
- Variant option names agreed (for example, "Size" not "size", "Color" not "Color" lowercase, since Shopify is case-sensitive in some contexts)
- Standard values for each option listed (for example, sizes "XS / S / M / L / XL", not a mix of "Small", "S" and "small")
- Products with no variants confirmed (no empty "Title" option needed)
Tags
- Any tags needed for automated collections created and listed
- Tag format agreed: lowercase, hyphenated, no spaces (for example, "category-dresses" not "Category: Dresses")
Product data and image file checklist
Supplier data file
- Supplier spreadsheet exported and reviewed: one product per row, or one variant per row with a consistent handle in the first column
- Required fields present for every product: title, description (or notes for the team to write one), SKU, price, weight (metric and imperial), and an image file name or image URL
- Any missing data flagged before sending: an upload service can note gaps, but a brief needs to say what to do when a field is empty
- Supplier abbreviations explained (for example, "BLK" = Black, "MED" = Medium)
The product data entry checklist covers the specific fields an upload team expects in a supplier file. Reading it before you send the data file saves the most common round of questions.
Descriptions
- A description style guide prepared: minimum length, tone, what to include from the supplier data, what to leave out
- Any fields the team should NOT touch marked clearly (for example, supplier legal disclaimers to enter verbatim)
- SEO titles and meta descriptions: should the team write them, or will the merchant provide them?
For what to include in a full handover package, see what to send your upload team.
Image files
Shopify accepts JPEG, PNG, WEBP, HEIC and GIF files, with a maximum file size of 20 MB per image and a maximum resolution of 25 megapixels (as of November 2026, Shopify file requirements).
- Image files named to match SKUs exactly (for example, SKU12345.jpg or SKU12345-1.jpg for the first image, SKU12345-2.jpg for a second angle): files named IMG_0001.jpg require manual matching, the most common cause of upload delays
- One folder per product, or a flat folder with SKU-based file names: either works, but mixed conventions do not
- No duplicate file names in the batch
- All images under 20 MB
- Background style agreed and consistent: white background, lifestyle shots, or a mix with a rule for which products use which style
- Alt text brief prepared: does the team write it from the product title and SKU, or does the merchant provide it?
The brief your upload team needs
A brief does not need to be long. A one-page document covering these items is enough for a first store:
| Item | What to include |
|---|---|
| Product types | The fixed list of values, one per row |
| Vendor names | The exact spelling for each supplier |
| Variant options | Option names, standard values and any exceptions |
| Collection assignments | Which product type or tag maps to which collection |
| Description rules | Length, tone, what to include and what to leave out |
| Missing data | What to do if a required field is empty: flag it, skip it, or use a placeholder |
| Image matching | How image files are named relative to SKUs |
| Out-of-scope items | Anything the team should not change, such as legal text or pricing fields |
The Shopify product uploading service includes a setup meeting before the first batch, where the brief is agreed and any gaps in the data are worked out. For stores with large catalogs, the Shopify product data entry service covers ongoing entry work after the initial upload. For a step-by-step guide to preparing supplier files, see preparing products for a Shopify upload.
Frequently asked questions
When is the right time to send product data to an upload service?
Once the store structure is settled: collections named, product types listed, variant naming agreed. The upload team can review a sample file before the full job starts to flag anything missing.
Does the upload team create collections, or do I need to create them first?
The team can create collections as part of the job, but the names, logic and any automated collection conditions need to be agreed in the brief first. If those decisions change mid-upload, every affected product needs to be updated.
What if my supplier file is missing some fields?
Note the gaps in the brief and say what to do: flag them, leave the field blank, or enter a placeholder. An upload team will not guess and will pause to ask, so documenting the rule upfront saves time on both sides.
How should image files be named if I have multiple angles per product?
Use the SKU as the base and add a number for each angle: SKU12345-1.jpg, SKU12345-2.jpg, SKU12345-3.jpg. This lets the team match every image to its product and variant without a manual lookup step.
Do I need to have all products ready before contacting an upload service?
No. A quote is based on the scope of the work: roughly how many products, how many variants per product, what fields need to be filled. You can get a quote from the product list and a sample of the data file before the full batch is ready.
