Product Photography Cost in India: Studio, Freelancer, and AI Compared

Ask three D2C founders what product photography costs and you will get three numbers that are not comparable.

One quotes a day rate. One quotes a per-image edit price. One quotes what they paid a freelancer last month and forgets the four rounds of revisions that came after. None of them is lying. They are just measuring different things.

If you are trying to budget a catalog, you need one unit that holds across every option: cost per listing-ready SKU. Here is how to work it out, and what each route actually costs once you do.

Why day rates and per-image prices both mislead

A studio quotes you a day rate. That day rate covers the shoot. It usually does not cover retouching, and it definitely does not cover the reshoot when six SKUs come back with the wrong shadow.

A freelancer quotes you per image. That price covers one pass. It does not cover the revision rounds, the WhatsApp thread, or the two days you waited for the second version.

Both prices are real. Both are incomplete. The gap between the quote and the invoice is where catalog budgets get eaten.

The only formula you need

Cost per listing-ready SKU
  = (base production cost per SKU)
  + (images per SKU × edit cost per image)
  + (rework rate × cost per fix)
  + (your team's coordination time × internal hourly cost)

That last line is the one everyone drops, and it is often the biggest. If someone on your team spends three hours a week briefing, chasing, and checking a photographer, that is a real cost against your catalog. Price it.

A note on the numbers below. Rates in India vary enormously by city, category, and volume — a Mumbai apparel studio and a Coimbatore hardgoods shooter are not in the same market. Do not treat any figure here as a quote. Use the structure, then fill in prices you have actually been quoted.

The four routes, compared on structure

Route	What you pay for	Turnaround per batch	Scales with SKU count?	Hidden cost
Studio shoot	Day rate + retouching + travel/logistics	Days to weeks	Poorly — more SKUs means more shoot days	Reshoots; scheduling around the studio’s calendar
Freelance photographer/editor	Per image or per batch	Days	Somewhat — capped by one person’s hours	Revision loops; availability gaps
In-house setup	Equipment, space, a person’s salaried time	Hours, once running	Well, if volume is steady	Idle cost when volume dips; the person becomes a bottleneck
AI workflow tool	Per image, usually subscription or credits	Minutes	Very well — marginal cost stays flat	Rework on hard SKUs; still needs a QC pass

The pattern is straightforward. The right route is a function of your SKU count and how often your catalog changes.

Which route fits which brand

Under 50 SKUs, changing rarely

A studio shoot is defensible. You are buying craft on a small, stable catalog, and the per-SKU cost of a good shoot amortises over a long time on the shelf. Spend the money once and get it right.

50–300 SKUs, refreshing a few times a year

This is where most Indian D2C brands sit, and it is the most painful band. A studio is too slow and too expensive to repeat. A freelancer becomes a single point of failure the moment they take a holiday.

A hybrid usually wins here: shoot your hero and campaign images properly, and run the routine catalog and variant images through an AI workflow.

300+ SKUs, or constant new launches

Per-SKU cost dominates everything else. At this volume a studio-only workflow is not a budget line, it is a launch blocker — the images arrive after the window you wanted to sell in. You need a workflow with a flat marginal cost and batch throughput.

Marketplace sellers with high variant counts

Colourways and size variants multiply images fast. Twenty products in five colours is a hundred image sets, not twenty. Variants are where per-image economics decide the whole budget.

The cost everyone forgets: time to listing

Money is the easy half. The expensive half is the delay.

A product sitting in your warehouse without images earns nothing. If a studio takes two weeks to turn around a batch, that is two weeks of a launched product not being live. On a seasonal SKU, that delay can cost more than the entire photography budget.

Work out your own number:

Cost of delay = (expected daily revenue per SKU)
              × (days waiting for images)
              × (number of SKUs waiting)

Run it once for your last launch. For most brands with a real catalog, the delay cost is larger than the production cost — and it never appears on any invoice, which is exactly why it goes unmanaged.

What to do with this

Pick your last 20 SKUs. Not hypothetical ones.
Work out what they actually cost — including revisions and your own coordination time.
Divide by 20. That is your real cost per listing-ready SKU today. Most brands find it is well above what they thought.
Add the delay cost using the formula above.
Now compare quotes. Against that full number, not against a day rate.

Most brands who do this find the answer is not “replace everything.” It is “keep the studio for hero images, move the routine catalog volume somewhere with flat marginal cost.”

Where Yumi fits

Yumi is priced per image, so cost per SKU is a multiplication you can do before you commit to anything — see the pricing page for the current rate.

If your catalog is large or your SKUs are difficult, and you would rather hand over a batch than run it yourself, our white-glove service does the whole thing and returns listing-ready files.

Bottom line

Stop comparing day rates to per-image prices. They are not the same unit.

Work out your cost per listing-ready SKU, add what the wait is costing you, and pick the route that fits your catalog size. For most D2C brands past 50 SKUs, the honest answer is a mix — and the mix moves toward per-image economics as the catalog grows.