Product Photography Without a Studio: What Operations Teams Are Actually Doing in 2026

Photo by George Milton on Pexels

Ask an operations manager at a mid-sized distributor what their biggest content bottleneck is, and product imagery comes up more often than you would expect. Not marketing campaigns — the mundane requirement that every SKU in the catalogue needs a usable photo, and new SKUs arrive faster than anyone can shoot them.

The traditional answers were all expensive: a studio, a photographer on retainer, or accepting whatever the supplier sent and living with inconsistent backgrounds and lighting across the catalogue.

What Changed

Generated and edited imagery moved from novelty to routine tooling in about two years. The practical result for operations is narrower than the marketing suggests, but it is real.

Background replacement and standardisation is the clearest win. A supplier photo shot on a warehouse floor becomes a clean catalogue image on a consistent background, at scale, in minutes rather than days. For a catalogue of several thousand items with inconsistent source photography, this is the difference between a coherent storefront and a messy one.

Lifestyle and contextual shots are the second. Showing a product in a plausible setting used to require either a shoot or a stock photo that did not quite match. Generated context is now good enough for category pages and secondary images, where nobody is inspecting closely.

Variant imagery is the third. When a product exists in eight colours, generating the seven you did not photograph is faster and more consistent than shooting all eight.

The Cost Model Is Different From What Ops Teams Expect

Most operational software is licensed per seat or per site. This is not. Generation is billed per image, at fractions of a cent to a few tens of cents depending on resolution and quality, through platforms that route to several models behind one account. Published rates for the GPT Image 2.5 Flare API and comparable models are listed openly, which means you can budget a catalogue project before committing to it rather than after.

The number that catches people out is not the per-image price. It is the multiplier. Nobody accepts the first output — real usage runs three to eight attempts before something is worth putting in a catalogue. If your project plan assumes one generation per SKU, your budget will be wrong by roughly a factor of five.

Plan for it deliberately: iterate at low resolution until the treatment is right for a category, then batch the final renders once at full quality. Establish the treatment on twenty representative SKUs before running two thousand.

Where It Still Fails, and Why That Matters More Here

For operations use, the failure modes are more consequential than they are in marketing, because catalogue images make implicit promises to buyers.

Text on packaging is unreliable. Any product where the label, model number or specification is visible and legible will come out wrong in a generated image. For these, edit the real photograph rather than generating a replacement.

Fine detail on the product itself drifts. Generated images approximate. For a decorative item that is acceptable; for a component where the buyer is checking the connector type, it is a returns problem waiting to happen.

This leads to a straightforward policy that most teams land on: generate and edit the context, never the product. Backgrounds, settings, lighting and staging are fair game. The item itself should come from a real photograph.

The Governance Question Nobody Asks Early Enough

Once generated imagery is in the catalogue, somebody needs to know which images are real photographs and which are not. Retailers, marketplaces and regulators are all moving in the direction of requiring that distinction, and retrofitting it across a catalogue of thousands of items is painful.

Tag it at ingestion. A single field recording whether an image is photographic, edited or generated costs nothing now and saves a genuinely unpleasant project later.

A Sensible Position

This is not a replacement for product photography. It is a way to make inconsistent source material usable, to fill gaps in a catalogue that would otherwise stay empty, and to produce secondary imagery that was never going to justify a shoot.

For operations teams measured on catalogue completeness and time-to-list, that is a meaningful improvement at a cost that is small and, unusually for this category of tool, easy to calculate in advance.