Blog · AI & workflow

How to run a season-wide photo refresh

A season-wide refresh is a sequencing problem rather than a shooting one: order the catalogue by how much traffic each listing gets and how wrong its current photo is, then work down that list until the Sep 24 deadline rather than trying to reshoot everything.

Published 18 August 2026

A cable-knit sweater on a model in a pale interior, shot for a new-season refresh — The Fall / Winter drop refresh is the one shoot that touches the whole catalogue — which is why it needs an order, not a target.

Fall / Winter drop — the dates

Window opens: Aug 18
Photos live by: Sep 2430 days from today
Peak: Oct 15 2026

Dates are computed from the event's recurrence rule, not typed into this post — they roll to the next occurrence on their own.

Do not try to reshoot everything

The refresh that fails is the one framed as a total. A catalogue of several hundred listings will not be fully reshot by any deadline, so a plan that requires it produces the same outcome every year: the easy listings get done, the deadline arrives, and the listings that mattered are still carrying last season's photos.

The plan that works inverts it. Accept from the start that you will not finish, and make sure the part you do finish is the part that earns. That turns the whole exercise into ordering the list correctly.

Two inputs decide the order

Rank by traffic and by wrongness, and take the listings that score high on both first. Traffic you already have. Wrongness is the judgement call, and it is more specific than 'old': a photo is wrong when it contradicts what the shopper is about to buy it for.

A summer dress shot on a beach is not merely dated in October — it actively argues against the purchase. That is a different and more urgent problem than a photo that is simply two years old but still season-neutral.

Swimwear styled for an off-season listing refresh — Off-season categories are the clearest example of wrongness: the product still sells, the setting no longer matches why.

High traffic, clearly wrong season — do these first, they are losing money now
High traffic, dated but neutral — second, and often a background swap is enough
Low traffic, clearly wrong — third, cheap to fix in a batch
Low traffic, neutral — leave them; the refresh does not need to be complete

Batch by treatment, not by product

Once the order exists, group the work by what has to happen to each image rather than by category. Everything needing only a background change is one batch; everything needing a new on-model render is another. Switching treatment costs more attention than switching product.

This is also where consistency is won or lost. A refresh done listing-by-listing over six weeks drifts — different lighting, different model, different crop — and a category page assembled from that drift reads as less trustworthy than one left alone. Batching keeps a run of listings visually coherent because they were produced in the same pass.

Background swaps — the cheapest treatment, and often enough for a neutral photo
New on-model renders — for anything whose styling contradicts the season
Full reshoots — reserve for hero listings that carry the category page
One model identity per batch — the thing that keeps a category page coherent

Where this stops applying

This is a plan for a catalogue too large to reshoot. If you have twenty listings, the sequencing overhead is not worth it — do all twenty and skip the ranking.

It also assumes your traffic data is meaningful. A new shop without history has nothing to rank by, and guessing at an order is worse than working through the catalogue in a sensible fixed sequence. And nothing here rescues a listing whose photo is fine and whose problem is price or sizing.

Small catalogues, where ranking costs more than it saves
New shops with no traffic history to rank by
Listings whose real problem is price, sizing or reviews
Categories where the current photos are genuinely season-neutral

Common questions

Which listings should I reshoot first in a seasonal refresh?

The ones that are both high-traffic and clearly wrong for the coming season — a photo that contradicts the purchase is more urgent than one that is merely old.

When does the fall/winter refresh need to be done?

Photos should be live by Sep 24 for a Oct 15 peak, which is what makes the ordering matter — the deadline arrives whether or not the catalogue is finished.

How do I keep a refresh from making my category pages inconsistent?

Batch by treatment rather than by product, and hold one model identity across each batch. A refresh done one listing at a time over weeks drifts in lighting and styling, and the drift is visible on a category page.

Is a background change enough, or does it need a full reshoot?

For a photo that is dated but season-neutral, a background swap is usually enough and is much cheaper — see AI background changer. Reserve reshoots for listings whose styling actively contradicts the season.