A seasonal catalog handover for your Shopify team runs smoothly when it starts 6 to 8 weeks before the range goes live, not the week you receive supplier data. That window covers the brief, the data delivery, the processing run, and a review cycle before launch day.
Most merchants start too late because they assume the handover begins when the supplier file arrives. It does not. It begins when you lock in the decisions that shape every product in the range.
Key takeaways
- A seasonal catalog handover for a Shopify team starts 6 to 8 weeks before launch, not when supplier data arrives.
- The handover brief locks in collection names, product types, variant naming, and tag structure before any data entry begins.
- Image folders organized by product name rather than supplier code save a full day of pre-processing on large seasonal ranges.
- A seasonal upload also changes your existing catalog: decide what happens to discontinued and archived products before the job starts, not during it.
- A review cycle before launch takes 3 to 5 business days; count that back from your go-live date when you plan the timeline.
What makes seasonal work different from a standard upload
A standard upload adds new products and finishes. A seasonal catalog handover is more involved because the new range has to fit inside an existing store structure, and that structure often needs to change.
Old-season products need decisions: do they stay live at a reduced price, get archived, or come down entirely? Seasonal collections need planning: is this year's summer range a standalone collection, or does it extend an existing one? Product types and tags from last season may not match the naming rules for this season's range if your catalog has grown or changed.
These are brief-time decisions, not upload-time decisions. If they are left unresolved when the data arrives, the team has to stop and wait while you work them out. That delay adds up across a large range.
The order of operations matters more on a seasonal run than on a straightforward new-products upload. Collection structure must be locked in before data entry begins, not adjusted mid-run. Any change to collection conditions after products have already been entered means checking every uploaded product to confirm it landed in the right collection.
What to include in your seasonal catalog handover brief
The brief is the document your upload team works from. For a seasonal range, it needs to cover these areas before any product data is delivered.
Collection structure. Name every collection the new range feeds into. If you are adding a new top-level seasonal collection, confirm its name and whether it uses manual or automated conditions. For automated collections, conditions must match the product type and tag values exactly as they will be entered, including case and spacing. Confirm these values before the run starts, not after.
Product types. List the product type values for every category in the range, spelled and capitalized exactly as they should appear in Shopify. Product type is a free-text field, and supplier data almost never uses the same labels your store does. The brief is where those mismatches get resolved before entry begins.
Variant naming. List size options, color options, and any custom options, in the order they should appear in Shopify. Include the exact label casing: "Small / Medium / Large" rather than "S / M / L" if that is what your store uses. Each variant must be on its own row in the data file. Shopify supports up to 2,048 variants per product (as of October 2026), which is rarely a constraint on seasonal ranges, but consistent naming across every product matters.
Tags. List every tag that applies to seasonal items. If you run promotions using tag-based automated collection conditions, such as a "summer-2027" tag to populate a promotional collection, include that tag in the brief. Discovering it was missing mid-run means a retroactive tag update across every affected product.
Discontinued products. Confirm whether products not in the new range should be removed, kept live at a reduced price, or moved to a clearance collection. The team needs a clear decision before the job starts, not a question to resolve during it.
The seasonal catalog handover timeline for your Shopify team
Work backward from your launch date. The table below uses a 6-week window. If your range is 300 or more products, extend to 8 weeks.
| Weeks before launch | What you do | What the team needs |
|---|---|---|
| 6 to 8 | Lock in the brief: collection names, product types, variant naming, tags, and discontinued-product decisions | Your current collection structure and a list of which products are leaving the range |
| 4 to 5 | Deliver the product data file and the image folder | A complete file with one row per variant, images organized by product name |
| 3 | The team processes the data: creates collections, enters products, assigns images, checks naming against the brief | Collaborator access with product and collection permissions, set up before the run starts |
| 2 | Review a sample batch before the full run completes | A list of the first 10 to 20 products you want to check |
| 1 | Final review and approval of the complete range | Your sign-off, or a list of corrections to be made before go-live |
| Launch | Products go live; the seasonal collection is published | Your confirmation to make the collection visible |
What the team works through
Once the brief and the product data arrive, the processing run follows this order.
File check. The team reviews the data file before anything goes into Shopify. Common issues on seasonal ranges include merged variant rows (each variant needs its own row in the file), missing product type values, and image files saved by supplier reference codes rather than product names. Shopify's CSV file size limit is 15 MB (as of October 2026), so a large seasonal range is typically split into batches.
Collection setup. New collections are created and conditions are confirmed before products are added. This order matters: products entered before collection conditions are set may not populate automated collections correctly.
Product entry. Products are entered field by field: title, description, product type, vendor, tags, variants with their SKUs and pricing, images, weight, and SEO fields. The brief determines every naming decision. Without it, each ambiguous value requires a question, and each question takes time. Shopify's product management documentation (as of October 2026) covers what fields appear on every product record.
Image assignment. Each image is assigned to the product it belongs to, with variant-specific images mapped to their variant. If your image folder is organized by supplier code rather than product name, the team builds a mapping document before assignment can begin. On a range of 500 products, that step typically adds a day.
Collection review. After entry, automated collections are checked to confirm they populated correctly using the conditions in the brief. Manual collections are checked for completeness.
What delays a seasonal catalog handover
Most delays on seasonal ranges come from four sources.
Image folder organization. Images named by supplier reference code rather than product name need a mapping step before they can be assigned. Name your image files to match the product names in your data file before you deliver them.
Unresolved collection decisions. "Active" as a product type value, a tag name, or a collection condition means something different in each context. If those definitions are in the brief, the team works from the brief. If they are not, the run pauses.
Late brief changes. A change to product type naming mid-run affects every product already entered. A new tag structure means re-tagging every product in the affected category. Brief changes cost nothing at week 6. They are costly at week 3.
Missing access. The team needs collaborator access with product and collection permissions before the processing run begins. Add the team by email with permissions to manage products, collections, and product data only. Access requests that arrive the day the run is scheduled to start delay the whole timeline. For how a Shopify product data entry service handles access and the full scope of a seasonal upload job, see the service page.
For context on how ongoing catalog work differs from a one-time seasonal handover, the Shopify catalog management service for ongoing updates covers how a regular update brief is structured differently. If this is your first time working with an upload team, what to send your upload team covers the three materials every handover needs. The catalog rules agreed during Shopify store setup (product types, collection hierarchy, variant naming) are the foundation every seasonal brief builds on.
Frequently asked questions
How far in advance should I start a seasonal catalog handover?
Six to 8 weeks before the range needs to be live gives time for the brief, a clean data delivery, the processing run, and a review cycle. For a range of 300 or more products, 8 weeks is the safer choice. Smaller ranges can move faster, but 4 weeks is the practical minimum for a clean handover with no surprises.
Does the image folder need to be organized a specific way?
Yes. Organize it by product name, using the same names that will appear in your Shopify product records. Image folders organized by supplier code or internal reference number require the team to build a mapping document before any image can be assigned. On a large seasonal range, that step adds a full day to the start of the run.
Can the team help if my supplier data needs cleaning before entry?
Yes. The team reviews the supplier file before entry begins and flags issues: merged variant rows, missing product type values, naming inconsistencies. For a seasonal range, the file check is part of the job. If the data needs significant restructuring, mention it when you enquire so it can be factored into the timeline and the quote.
What happens to old-season products during a seasonal handover?
That depends on the decision in your brief. Options include keeping them live at a reduced price, moving them to a clearance collection, hiding them, or removing them from the store. Confirm your preference in the brief before the run starts. Our Shopify product uploading service page covers the full scope of what a seasonal upload job includes.
What access does the team need for a seasonal catalog handover?
The team is added to your store by email, with permissions to manage products, collections, and product data only. No owner password or full store access is needed. Set this up before the processing run is scheduled to begin, not on the day.
