A studio can shoot a lot of products in a day. Almost none of them reach a product page that week. The gap is where the backlog lives, and it is mostly not photography.
Short answer: three things create studio backlogs. Setups that are rebuilt from memory each session, so images do not match between batches. Shot lists that are agreed after the shoot, so frames are missing and products come back. And a post-production step whose main output is crops, which should not be produced at all. Fix those and throughput roughly doubles without a second studio.
Standardise the setup, then never rebuild it
Consistency across a product grid matters more than the quality of any single frame. A customer scrolling a category page reads inconsistency instantly and quality barely at all.
The way to get consistency is to stop treating the setup as a creative decision each time.
- Fix the camera position, lens, height and distance per category. Write them down with numbers, not adjectives. Mark the floor.
- Fix the lighting. Same modifiers, same positions, same power. Photograph the setup itself and pin the photograph up.
- Shoot a reference target at the start of every session. A grey card and a colour checker take ten seconds and make colour correction deterministic instead of subjective.
- Keep a physical reference product. Shoot it first each session and compare against the last session’s frame. If they do not match, something moved, and you want to know before three hundred products go through.
The gain is not only visual. A standardised setup means the crop and the framing are predictable, which means downstream processing can be automated instead of eyeballed.
Agree the shot list before the sample arrives
Reshoots are the most expensive failure in the pipeline because they consume a slot, a sample and a second round of everything after.
The shot list should be a property of the category, not of the shoot. Every chair gets these seven angles. Every garment gets these five plus a detail. Written once, reused every season, and known to the person booking samples so that a product without the required angles never leaves the studio.
Two additions make it much more useful. First, mark which frames are mandatory for each channel, so the studio knows the square-on-white is not optional if you sell on a marketplace that requires it. Second, treat the list as a manifest for ingest, so the pipeline can tell you which frames are missing rather than someone noticing later. That is the same manifest idea described in the product image workflow.
Stop making crops
Look at what post-production actually spends its time on. A share of it is real work: cleanup, colour, background, product accuracy. The rest is producing the six or eight sizes and aspect ratios that different destinations need.
That second part should not exist. If renditions are derived from an approved master by parameter, the studio ships one file per frame and the destinations take the shapes they need. This removes a step, removes a storage problem, and removes the whole class of bug where the product page updates and the marketplace listing keeps the old crop.
Two mechanics make it work reliably at scale.
Content-aware cropping. A centre crop of a wide product shot cuts the product in half. Automatic subject-aware cropping, such as gravity-based cropping, gets it right for most frames without a person choosing a focal point. Set a focal point manually for the exceptions.
Background handling as a transformation. Cutting out a product against white is genuine post-production work, but a large share of it is now doable as a transformation on delivery rather than as a file someone produces. Treat it as a first pass to be reviewed rather than as a finished result, and keep the master untouched underneath.
The point is not that the tooling is clever. It is that the studio’s output becomes one master per frame, which is the smallest thing it can be, and everything downstream is a parameter.
Add capacity without adding a studio
When the shoot slot genuinely is the bottleneck, the options are cheaper than a second studio.
Batch by setup, not by product. Shooting every product that uses the same setup consecutively removes the rebuild time between products, which is often more than the shooting time. This can double throughput on its own and it costs nothing.
Shoot in a fixed rhythm. A standing weekly session that always happens is more productive than an ad hoc session that gets scheduled around availability, because samples can be prepared against a known date.
Separate the easy from the hard. Most catalogues are eighty per cent products that need seven standard frames and twenty per cent that need art direction. Running them through the same process paces everything at the speed of the hard ones. Split the flow.
Consider a second location for the standard eighty per cent. A fixed, standardised setup can be replicated. An art-directed one cannot. This is the argument for outsourcing the simple flow rather than the complex one, which is the opposite of what usually happens.
Preserve metadata through post-production
Every export step is an opportunity to lose the information that makes the images findable later.
Capture software can write the SKU, the shoot date, the photographer and the campaign into the file at capture. Retouching software can strip all of it on export, and often does, depending on the export preset. IPTC photo metadata fields are the standard carrier for this, and ExifTool is how you check whether yours survived a round trip.
Test your own pipeline once, deliberately: write known values at capture, run a file through the whole post-production path, and read them back at the end. Whatever is missing is missing for every image you have ever shipped, and the fix is usually one export preset.
What does good throughput look like?
Ranges rather than targets, because category matters enormously. A standardised tabletop setup with a fixed shot list will comfortably do thirty to sixty products a day with one photographer and one assistant, where a product means seven frames. Art-directed lifestyle work is a different activity and comparing them is not useful.
What is worth comparing is your own before and after. Measure products published per week, not frames captured, because frames captured is the number that looks good while the backlog grows. The operating model that keeps that number stable across a season is in running product content as an operation, and the pre-launch version is in the catalogue launch checklist. For what the images should carry once they land in the library, see what a DAM actually does.
