Preparing Seasonal Catalogs for Your Upload Team

Seasonal catalog prep for your upload team means giving them accurate data, clean files, and clear rules before the season's products touch Shopify. When merchants hand over a folder of supplier sheets without context, the team has to pause and ask questions. That pause costs time before the peak period.

This checklist covers what changes between seasons in your product data, how to handle new variant structures, and what the upload team needs to work without interruption.

Key takeaways

• Product handles, pricing, and availability status are the three fields most likely to need changes between seasons, and the upload team needs clear instructions on each before they start.
• Sending new colorway names with no Shopify-ready format puts the team into naming decisions that should have been made earlier.
• Retiring last season's SKUs requires explicit instruction; an upload team will not delete or deactivate anything without a confirmed list.
• A seasonal brief template takes about 30 minutes to fill in and prevents back-and-forth during the busiest weeks.

What changes between seasons in your product data

Most product fields stay stable year to year, but four areas shift with every seasonal range.

Product titles and handles. A "Linen Shirt" that existed last summer may return this year in a different fabric weight, with new colorways, or under a slightly different name. If you reuse the same Shopify handle, the upload team will update the existing product rather than create a new one. If you want a new listing, you need a new handle. Telling the team which is which prevents the wrong products from being overwritten.

Variant options. New colorways ("sage," "clay," "vintage white") must match the capitalization and format you used for earlier colors in the same product range. Shopify stores option values as text, so "Sage," "SAGE," and "sage" create separate entries and cause filter problems on your storefront. Send a list of approved color and size names that the team can match against.

Pricing. Introductory prices, early-season sale prices, and compare-at prices all need to be set correctly from day one. If your seasonal range opens at a launch price that changes in four weeks, include both the opening price and the compare-at price, and note whether the compare-at price should be populated from launch or added later.

Product status. New season products usually go in as draft while images and copy are finalized, then flip to active on release day. Confirm the target status with the upload team, along with any publication date fields (Shopify's "scheduled publish" feature is available on select plans, as of November 2026). If the team sets products active immediately and you aren't ready, your storefront shows incomplete listings.

Variant structure for seasonal lines

Seasonal ranges often introduce new products with more complex variants than your store's existing range.

A common example: last season you sold t-shirts in one size run (XS to XL). This season you are adding oversized fits, which need a separate "Fit" option alongside "Size." Shopify allows up to three option types per product (as of November 2026). If the new range needs more than three, you'll need to decide whether to split those into separate products before the data goes in. That structural decision needs to happen before the upload team starts, not during the job.

Send a brief note for any product category where the option structure differs from last season:

• What option names are you using (Size, Color, Fit, Finish)?
• Are any existing product types getting a new option type added?
• Do any bundles or sets need to be listed as one product with quantity variants, or as separate items?

Handle conflicts and retired products

The most common cause of a mid-season data error is sending the upload team a "new season" spreadsheet that reuses the previous season's handles.

Shopify uses the handle as the unique identifier for a product. When a CSV row matches an existing handle, Shopify updates that product instead of creating a new one. If your spring spreadsheet contains handles from the previous autumn range, the team will overwrite live autumn products with spring data.

Before handing over any file, run through these two lists:

1. Handles to retire. Products that are discontinued, archived, or end-of-season. Give the team an explicit instruction for each: draft them, make them unavailable, or leave them live with a sale tag. Upload teams don't delete products; they need a clear directive.

2. Handles to reuse. Products that carry over between seasons (a core t-shirt, a year-round accessory line) with updated variants or pricing. The team will update rather than create for these, so confirm which fields to change and which to leave.

If your seasonal range is entirely new products with no overlap, say so. That's the clearest brief an upload team can receive.

Pricing, availability, and date fields

Field	What to tell the upload team
Price	The launch price for each product or variant, in the store's currency
Compare-at price	Whether to populate it, and from what date (can be blank at launch)
Product status	draft or active; if active, whether that is immediate or scheduled
Sales channels	Online store, point of sale, buy button: confirm which channels the product publishes to
Inventory policy	Whether to continue selling when out of stock (Shopify's "overselling" toggle)
Requires shipping	Yes for physical products (default); no for digital. Affects the checkout flow
Taxable	Whether the product collects tax at checkout, which varies by jurisdiction

For a seasonal range landing in Shopify before it goes live, draft status plus the correct price and compare-at from day one is usually the safest setup. The team can flip status to active on a schedule, or you can do it yourself in Shopify admin when you're ready.

Seasonal catalog prep checklist for your upload team

Print this out and fill it in before you send anything to the upload team. You can hand it over alongside the product file.

Before you send the files:

• Confirm whether this is a new product range (all new handles) or a mix of new and carry-over products
• List every product handle being retired and the action to take (draft, unavailable, leave active)
• List every product handle being reused and what changes (price, colorways, inventory only)
• Confirm the option types for each new product category (Color, Size, Fit, Material, etc.)
• Confirm approved option values: exact spelling and capitalization for every new colorway, size, and fit name
• Confirm launch prices and whether compare-at prices apply from day one
• Confirm whether products should land as draft or active
• Confirm which sales channels each product publishes to

In the file you send:

• One header row with Shopify-compatible column names, or a column mapping note if your headers are different
• A Handle column that matches your intent (new handle = new product; existing handle = update)
• A Variant SKU column with a unique SKU for every variant
• A Variant Price column with launch prices
• A Status column, or a note at the top of the brief confirming the target status

A note on file format: Shopify's CSV template for products is the most reliable format for large seasonal uploads (see Shopify's product CSV guide for the current column names and format, as of November 2026). If you are using your supplier's format instead, tell the upload team what cleaning steps they should expect.

Your Shopify product uploading service does this conversion as part of the job, but the data you send must be specific enough to make the decisions above. No amount of Shopify expertise can substitute for knowing whether "Linen Shirt" is a new product or an update to an existing one.

For large seasonal ranges, bulk product uploading handles the volume, but the brief above is still the same size regardless of how many products you are adding.

Understanding variant limits before you brief

Shopify caps each product at 100 variants and three option types (as of November 2026; see Shopify's variants documentation for current limits). A women's top in 5 sizes, 10 colors, and 2 fits = 100 variants exactly. Add a third color and you are over the limit.

If a seasonal range pushes a product past 100 variants, the upload team will need a decision from you: split into multiple products (for example, "Top - Core Colors" and "Top - New Season Colors"), or drop some options. That decision changes the product structure, so it cannot be made mid-job.

A quick check: multiply your option counts before the brief. If the total exceeds 100, flag it in the handover note. The seasonal catalog handover timeline covers when to have these conversations relative to your release date.

For category-specific seasonal data requirements, the skincare gift sets handover guide shows how to brief a team on a gift range with bundles and limited-edition packaging, and the activewear drop timing guide covers what lead time looks like for a large seasonal range.

Frequently asked questions