Photographing a hundred products without stopping trading

A product photography workflow is a fixed sequence — shot list, locked lighting, tethered capture, cull, retouch, export — that lets a small team shoot a hundred SKUs in a day without taking the catalogue offline. The speed comes from repetition, not from rushing: you build the set once, then change only the product.

Key Takeaways

• A batch shoot is a production line, not a creative session: the set, lights and camera stay fixed while the product changes.
• Lock the shot list and the file naming before the day starts. Unplanned SKUs are what make shoots run long.
• Shoot tethered with a colour reference frame at the top of every session, so drift is provable rather than argued about.
• Retouch to a template, not per image. Hand-finished edits are where batch consistency quietly dies.
• Verify with a contact sheet and a manifest diff before anything reaches the storefront.
• Budget set-up once per session and retouch per image — that split decides whether the day was worth running.

What is a product photography workflow?

A product photography workflow is the fixed order of operations behind every catalogue image: style the item, lock the camera and lights, capture tethered, cull against a reference, retouch to a template, then export files named after the SKU they show. It replaces per-shot judgement with a checklist anyone on the team can follow.

The word doing the work there is "fixed". A photographer who resets the lights for every item produces beautiful images that never quite match each other, and a category page built from them looks assembled rather than designed. Consistency is a systems problem, not a talent problem.

It also changes who can do the job. Once the set is locked and the checklist exists, a studio assistant can shoot the routine items while the senior person handles the five that genuinely need a human eye — glass, chrome, anything with a mirror finish.

Why does a big shoot stall the shop?

A large shoot stalls trading when the set has to be rebuilt between sessions, when bestsellers sit in a studio for days, or when images only reach the site after a manual upload. Keep capture off the sales floor and keep the live listings running while you work through the batch.

In practice, most of the damage isn't the photography. It's the gap between capture and publish. Files land in a shared drive, somebody renames them by hand, and the one person who knows which frame belongs to which SKU is on leave. The listing keeps the old photo, or worse, keeps no photo at all while customers are still searching for it.

When do you need a studio batch shoot — and when is a phone and a lightbox enough?

You need a studio batch shoot when the catalogue has to look uniform across dozens or hundreds of SKUs, when marketplaces reject inconsistent images, or when the product itself is the main selling argument. A handful of items updated occasionally does not justify building a set at all.

Approach	Fits best	Throughput reality	Watch out for
Phone plus lightbox	A few SKUs, quick listing updates	Fine for one or two items a week	Colour and shadows shift between sessions
Fixed studio set, one operator	50–150 SKUs per shoot day	Highest consistency per session	Set build and calibration eat the first two hours
Outsourced studio, per batch	Peak season or a full relaunch	Fast, but you queue for their calendar	Agree specs and naming in writing first
Supplier or manufacturer images	Commodity goods sold on many sites	No capture work at all	You compete with every other reseller

How does the workflow actually run?

The workflow runs as stations rather than one job: prep, capture, cull, retouch and export happen in separate passes, each with its own quality gate. Splitting the work lets a junior operator shoot today's batch while a designer retouches yesterday's, and it keeps a single slow image from blocking the queue.

The capture station is a table, a seamless sweep, two or three lights and a tripod that nobody moves. The camera is tethered to a laptop, so each frame lands on disk immediately with a filename, not on a card that has to be downloaded later. The retouch station is a saved preset, a colour profile and an export action, and the person there never touches exposure unless the shot list says the item is special.

Everything between those stations is naming and manifests. The file that leaves capture already carries the SKU, the angle and the variant, so nothing downstream has to guess.

How do you shoot a hundred products in a day?

You shoot a hundred products in a day by removing every decision that can be made beforehand. Prepare the SKU list, the angles per SKU, the naming pattern and the export spec before the camera comes out; on the day, the operator only swaps the product and presses the shutter.

1. Freeze the shot list: which SKUs, how many angles each, which ones need a detail or scale shot.
2. Prep the goods the day before — clean, steam textiles, remove tags, fingerprints and packaging creases.
3. Group items by shape and size so lighting changes are batched instead of scattered.
4. Build and lock the set: table height, sweep, light positions, camera height and lens. Mark the floor with tape.
5. Tether the camera and shoot a colour reference frame plus a white card at the start of every session.
6. Capture in category batches, naming files as you go rather than afterwards.
7. Cull in batches against the reference frame; delete rejects immediately so the folder stays honest.
8. Retouch with the saved template, export to the agreed spec, and hand over with a manifest listing every file.

Which capture settings and naming rules matter most?

Manual white balance, sRGB output and one fixed aspect ratio do more for catalogue consistency than any camera upgrade. Naming matters just as much: a file called IMG_4471 is a file nobody can publish safely six months later, when the shoot is a memory and the SKU list has moved on.

Rename in bulk, but never blind. A dry run costs nothing and catches a wrong prefix before a thousand files carry it:

# 1. Dry run — prints the mapping, changes nothing on disk
for f in *.jpg; do echo "$f  ->  ${SKU_PREFIX}_$f"; done

# 2. Apply only after the mapping looks right, and only once
#    the card or folder has been copied somewhere else first
for f in *.jpg; do mv "$f" "${SKU_PREFIX}_$f"; done

That second loop renames real files in place. Copy the folder to a second drive before you run it, and never run it on the only copy of a shoot.

How do you verify a batch before it goes live?

Verify a batch by building one contact sheet, diffing the file list against the SKU manifest, and spot-checking the awkward items — glass, jewellery, black fabric, anything reflective — under the same light your customers browse in. Caught here it costs an hour; caught after publishing it costs a re-shoot.

The manifest diff is the step people skip and later regret. Export the SKU list from your store, list the exported filenames, and compare the two sets. Every SKU should have exactly the angles you agreed, and every file should have a SKU that exists. That one check catches the missing variant, the duplicate name and the item that never made it out of the prep box.

What fails in a batch shoot, and what do you check first?

Colour drift — the slow change in white balance and exposure between sessions — is the most common failure, and the first thing to check is the reference frame shot at the top of each session. If the chart matches, the problem is downstream: a retouch preset, the export profile, or a colour-managed viewer on someone's laptop.

• Mixed colour temperature: auto white balance was left on. Switch to manual and re-shoot the affected batch.
• Missing SKUs: run the manifest diff before publishing, not after.
• Inconsistent crops: two people exported with different settings. Keep one export action.
• Hotspots and reflections: lights too close or too direct. Move them, don't retouch them.
• Lost files: a single card with no second copy. Tether, and copy to two drives during the shoot.
• Over-retouched products: colour and texture that no longer match the item. Cap the preset, not the judgement.

What does a shoot cost in time and operational overhead?

A batch shoot costs set-up, capture and retouch, and the split between those three decides whether it is worth doing in-house. Set-up is paid once per session; retouch is paid per image, and it is usually the largest and least visible line in the whole exercise.

Beyond labour, count storage for the raw files, the egress and delivery cost of serving large originals to shoppers, and the licence or subscription cost of any tethering and editing software you use. Image delivery through a CDN is worth understanding before you publish a large catalogue — see Cloudflare's image delivery documentation for how transformation and caching change what leaves your origin. Cloud pricing moves constantly, so confirm current figures with the vendor's own calculator rather than a blog post.

The hidden cost is a re-shoot. Getting it right the first time is nearly always cheaper than explaining to a supplier why 120 items need photographing twice. If you would rather have someone scope that split for you, our team can help you work out what belongs in-house and what doesn't — start a conversation.

What security and rights issues come with a product shoot?

Product shoots carry rights and embargo risk: unreleased items photographed before launch, supplier artwork you have no licence to reproduce, and raw files sitting on a freelancer's personal drive. Agree who owns the images, who can reach the raw files, and when those files get deleted or archived.

Keep unreleased products watermarked and out of shared folders until launch day. Store the raw library behind access control, not on a public link, and hand over credentials in the client's own accounts where possible. If you publish to marketplaces, structured product data is the other half of the job — Google's search documentation for product markup explains what the listing needs beyond the photo itself.

A realistic scenario: 120 SKUs without a dark week

A Kathmandu retailer with 120 SKUs and a live storefront cannot afford a dark week, so the shoot runs around trading hours. Prep happens the day before, capture happens in one long session, and the storefront keeps selling the old images until each new batch passes its check.

Day one is prep: goods cleaned and grouped, the shot list frozen, the set taped out. Day two starts with the reference frame, then runs in two batches with a break for the lighting change between textiles and hard goods. Retouching happens the following morning from a preset, and the export lands in a folder named for the batch. Nothing is published until the manifest diff passes and someone has opened the contact sheet on a calibrated screen.

The first run takes longer than anyone expects. The second one doesn't, because the tape marks, the preset, the naming rule and the manifest already exist. That is the whole point of the workflow: the first shoot is an engineering project, and every shoot after it is operations. Work like this sits alongside the catalogue and storefront projects we have delivered — you can see a few on our portfolio.

Does the workflow change for WordPress or marketplace catalogues?

The workflow doesn't change, but the export spec does: WordPress and WooCommerce want a consistent aspect ratio and reasonable file sizes, while marketplaces publish their own rules on background, crop and image count. Match the export to the strictest destination and the softer ones will accept it.

WordPress stores usually need a thumbnail, a category image and a zoom image per SKU. Generate those from one master file with the same crop rule every time, and let the theme handle resizing rather than uploading three hand-edited versions. We do a fair amount of WordPress and WooCommerce catalogue work, and the shops that suffer are the ones where every image was cropped by hand.

Marketplaces are stricter about the white background and the minimum pixel dimensions, so shoot to the tighter rule. Retouching is also where brand consistency lives: background treatment, shadow softness and any overlay marks should come from the same design system as the rest of your brand, not from whatever preset the freelancer had on their laptop.

If you're still deciding how the catalogue is structured before you shoot, the questions in our frequently asked questions cover the common ones we hear from retailers.

In short: freeze the shot list, lock the set, calibrate every session, name files after SKUs, retouch from a template, and verify against a manifest before publishing. Do that and a hundred products is a long day's work rather than a lost week of trading.

People also search for

• Product photography workflow for an e-commerce catalogue
• How many product photos can you shoot in a single day?
• Do you need a PIM, or will a spreadsheet do?
• Handing a product shoot over to another team
• What actually drives the cost of an e-commerce build

If you'd rather not build this yourself, our team can help you plan the shoot, template the retouch, and wire the exported files into your storefront so publishing stops being a manual job. Tell us what you're shooting, and take a look at the catalogue and web projects we've delivered while you're at it.