Launch Thursday, photos still missing
The new collection is due to go live on Thursday. On Tuesday, the product team discovers the olive colourway of the wrap dress was never shot, because the sample was at a press day. Three styles have front and back shots but no detail close-ups. The retoucher has sent 400 files named 'DSC_4471_edit.jpg', and someone is dragging them into Shopify one at a time, looking at each to work out which product it belongs to.
The shoot itself went well. The problem is everything around it: which sample goes to the studio, which shots each style needs, what the files are called and how they reach the product page.
Where the time goes
- Shot lists are written fresh for each shoot, often from memory.
- Samples are not tracked, so a missing colourway is found on the day.
- File naming depends on the photographer and retoucher, not on your product data.
- Matching finished images to products is done by eye.
- Alt text, image order and colour assignment are done by hand for each product.
Each gap is small. Together they turn a short shoot into a long wait before the collection is sellable.
What the delays cost
| Delay | Effect |
|---|---|
| Missing shots found late | Reshoots and pushed launch dates |
| Manual image matching | Days of product team time per collection |
| Wrong image on a colour | 'Not as pictured' returns |
| Stock sitting unshot | Goods in the warehouse that cannot be sold |
How we build the shoot workflow
- Your product data, from the range plan or Shopify drafts, generates a shoot tracker: one line per style and colour that needs photographing.
- Each product type has a standard shot list you define once, such as front, back, side, detail and on-model. The tracker shows every shot needed per colour.
- Samples are checked in and out against the tracker, so the team sees on the morning of the shoot which colourways are not in the studio.
- The photographer or studio names files to a rule based on style, colour and shot, and a shared folder in Google Drive, Dropbox or similar receives them.
- Uploaded files are matched to products by name automatically, placed in your chosen order and assigned to the right colour variant. Anything that does not match goes into a short exceptions list.
- Alt text is drafted from product data and shot type, for example 'Olive wrap dress, back view', and a person approves it.
- The tracker shows, for each product, which shots are complete, so the launch decision is based on a list rather than a scroll through the store.
Shoot week afterwards
On Monday, the tracker shows the olive wrap dress sample is still with the press agency, so it is called back before the shoot. On Wednesday, edited files land in the folder and appear on draft products within minutes, in the right order and on the right colour. The product team spends Thursday on copy and checking, not on dragging files. The collection goes live with every shot in place, or with a clear list of the two that are still coming.
If you use an outside studio
Many brands send samples to an outside studio. The same tracker works: the studio sees the shot list, the file naming rule is part of the brief, and their delivery folder is the one the matching watches. If the studio has its own naming, we can map it to yours rather than asking them to change. For flat lays, ghost mannequin and on-model shots taken on different days, the tracker keeps each shot type separate so a partial delivery is still usable.
Signs your photo workflow is the bottleneck
- Collections wait for images after the stock has landed.
- Missing colourways or shots are found close to launch.
- Image files arrive with names that mean nothing.
- Someone uploads and orders images one product at a time.
- Shoppers see photos of the wrong colour on some variants.