Product Photography Cost Per SKU: Formula + Budget Example
Ecommerce teams talk about photoshoot budgets. Catalog operations run on a different number: what it costs to get one product photographed, approved, and live. That number is the one that scales with the business, and most brands have never calculated it honestly.
The short version: divide the full production cost by the products that actually received an approved image set. A cheap per-image quote can still produce an expensive catalog if it leaves out views, retouching, revisions, or your team's time.
Calculate it properly
Most teams compute cost per image, which flatters the number, or divide the photographer's invoice by the SKU count, which understates it badly. The honest formula:
Total loaded cost ÷ SKUs that shipped usable imagery
Total loaded cost includes:
- Crew — photographer, assistants, stylist, hair and makeup
- Studio or location, plus permits
- Sample logistics — pulling, shipping both ways, returns, insurance
- Post-production, per image, at your actual approval standard
- Your team's hours — briefing, attending, selecting, revising, uploading
- Reshoots and rejects
- A share of any usage licensing
Two denominators matter. Use SKUs that shipped, not SKUs photographed — the ones that got dropped still consumed budget. For this calculation, use a style-colourway as the imagery unit. If your inventory assigns a SKU to every size, group sizes that share the same image set; count them separately only when they need different imagery. Use that same denominator in every quote.
Run this once on your last production. Compare the invoice-only figure with the loaded figure to see which omitted costs matter in your workflow.
Calculate cost per SKU with current quotes
Assume 50 style-colourways need four final images each. That is 200 required images. Add photography, studio, styling, sample handling, retouching, internal review, and revisions using your own quotes. For AI generation rates, use Astria pricing.
Divide the total by the number of complete, approved SKU sets. If only 40 sets ship, divide by 40 SKUs or 160 approved images. Rejected frames still consume budget, but do not count as deliverables.
For a per-image quote, multiply the quoted rate by the required views per SKU, then add any separately billed setup, logistics, licensing, and internal work.
How to compare product photography quotes
Send every supplier the same brief: number of style-colourways, required views, background, styling, output size, retouching standard, usage, and deadline. Ask whether the quote is per image, per product, per hour, or per day, and whether minimum charges apply.
Then fill the gaps: who prepares samples, who handles difficult surfaces, how many revision rounds are included, and what happens to an unapproved image? For AI production, also count reference preparation, paid attempts, manual corrections, and human review. A credit buys an operation; your catalog needs a usable result.
Use fashion photoshoot cost for the shoot budget and AI versus traditional photoshoot cost for the production-method comparison. Keep this page's calculation at the product level.
Why the long tail stays ugly
Here is the structural problem, and it is not a failure of anyone's judgment:
When products need similar handling and views, much of the per-item work repeats. Batching spreads setup costs, but it does not remove styling, checking, and retouching for each item.
Expected sales need not follow that pattern. If a few styles carry most of your revenue, the same image spend takes a larger share of the margin on lower-volume products.
So there is a crossover point where imagery cost exceeds any defensible share of a product's expected margin. Below it, the rational decision is the cheapest possible treatment — a flat lay, a ghost mannequin, or the supplier's own photo.
That can leave the lower-volume products with less useful coverage. Before cutting it further, test whether the missing views are needed to explain the product; low sales alone do not tell you which images are expendable.
What each SKU actually needs
A typical apparel PDP set:
| Image | Purpose |
|---|---|
| Front, on-model or ghost | The primary listing image |
| Back | Fit and construction |
| Detail ×1–2 | Fabric, hardware, trim |
| Lifestyle or in-context | Scale, styling, desire |
| Additional colorways | Accuracy per variant |
For this planning example, allow four to eight images per style-colourway. Do not multiply by colourways again if your SKU count already includes them. A 200-style collection in three colorways is 600 variants and, at six images each, up to 3,600 individual assets per season.
That multiplication is the whole reason per-SKU thinking matters. Budgets are approved per shoot; costs are incurred per variant.
What actually moves the number
Batching. More SKUs per setup amortises the fixed cost. Real, and limited by attention — quality degrades late in a long day.
Simplifying the standard. Fewer images per SKU, less retouching. Cuts cost directly and visibly.
Offshoring post. Reduces the per-image retouch line. Adds turnaround time and a review burden that partly offsets it.
Shooting less often. Fewer, bigger productions. Amortises well and hurts speed to listing — new products wait for the next shoot.
Compare these choices against turnaround time and the coverage customers need. The lowest production invoice is not necessarily the lowest cost of getting the catalog live.
What changes the shape
The reason AI production is interesting here is not that it is cheap per image — it is that it decouples per-SKU cost from crew time. The AI product photography workflow shows where reference preparation, review, rejects, and channel delivery enter that calculation.
Once an approved treatment exists, the next SKU needs reference preparation, generation, and review. Some products will also need manual corrections or conventional photography. Measure those costs in a pilot rather than assuming they fall to the generation fee.
If that combined cost is lower while the approved coverage stays useful, the budget can reach more products. Whether this improves sales is a separate test; cheaper production does not establish a revenue lift.
Two honest caveats. First, the up-front direction work is real and should not be skipped; a bad treatment scaled across 600 variants is worse than no treatment. Second, review does not scale to zero — the hard garments still need looking at, per item. Budget for both, and see flat lay to on-model for which garments need the attention.
A model you can fill in
For your own catalog, work out:
- Loaded cost of last season's production (all lines above, including your hours)
- SKUs that shipped usable imagery
- Current cost per SKU = 1 ÷ 2
- Expected gross margin per SKU over its life — for a median SKU, not a hero
- Imagery as a share of margin = 3 ÷ 4
If step five is uncomfortable for the median product, you have quantified why your long tail looks the way it does. Then model the alternative honestly: up-front direction cost, plus per-variant generation and review, divided across the same SKU count.
Use your approved-image ledger for the denominator. The photoshoot calculator is another starting point for planning coverage; reconcile any estimate with the style-colourway counting rule above.
The full side-by-side is in AI versus traditional photoshoot cost, and the traditional line items are broken down in what a fashion photoshoot costs.
Frequently asked questions
How do you calculate product photography cost per SKU?
Take the fully-loaded cost of a production — crew, studio, post-production, sample logistics, and your own team's hours — and divide by the number of SKUs that shipped usable imagery. Not by images produced, and not by SKUs photographed.
How many images does each SKU need?
A working apparel set might contain four to eight images: front, back, details, and on-model or lifestyle views. Set the count from the product and sales channel. Count each style-colourway once when its size variants share those images.
Why is the long tail of a catalog photographed worse?
When low-volume products require the same production work as bestsellers, imagery can consume a larger share of their expected margin. Check that relationship in your own catalog before reducing coverage.
Do colorways need separate photography?
Each colourway needs an accurate reference and approved coverage. A digital colour edit must be checked against the actual product, including trims, patterns, and fabric appearance. Budget separately when a colourway needs its own image set.
What is a good cost per SKU target?
There is no universal figure — it depends on price point, margin, and expected units. The useful test is relative: your imagery cost per SKU should be a defensible fraction of the gross margin that SKU is expected to generate over its life.
Price your catalog with the photoshoot calculator, or explore Astria for fashion and ecommerce.