The Real Cost of Product Photography
Everyone knows what a photo studio charges per image. Few teams track the total cost – the hours, the delays, the missed listings. Here's how to actually calculate it.
Ask any e-commerce manager what product photography costs and they’ll give you a per-image number. Maybe €2 for basic shots. Maybe €15 for styled lifestyle images. Maybe “we do it in-house so it’s free.”
That last one is never true.
The visible costs
The numbers people track are straightforward:
- Studio or photographer fees – per image, per hour, or per day.
- Equipment – camera bodies, lenses, lighting rigs, tripods, turntables, backgrounds.
- Software licenses – Lightroom, Photoshop, capture software, DAM systems.
- Hosting and storage – cloud storage, CDN delivery, backup.
For a typical Czech e-shop processing 500-2,000 products, these add up to somewhere between 50,000 and 300,000 CZK annually. That’s the number in your budget.
The invisible costs
Here’s what almost nobody tracks:
Time between capture and publish. How many days pass between photographing a product and having it live on your e-shop? For many teams, it’s 3-7 days. For some, it’s weeks. Every day a product sits without photos is a day of zero revenue on that SKU.
Coordination overhead. Someone has to schedule the shoot, transport products to the studio, communicate requirements, review outputs, request reshoots, rename files, upload to the CMS. This person-hours cost is often higher than the photography itself.
Rework. The photographer delivers 200 images. 30 have wrong backgrounds. 15 are cropped differently than the rest. 8 are matched to wrong SKUs. Fixing these isn’t “free” – it pulls your team away from other work.
Opportunity cost of delayed listings. If a new product could generate 500 CZK/day in revenue and your photo pipeline delays it by 5 days, that’s 2,500 CZK lost. Multiply by the number of products delayed per month.
Scaling friction. You want to add 1,000 new SKUs? With a traditional workflow, that means proportionally more studio time, editor hours, and coordination. Growth directly increases cost.
How teams actually spend their time
We’ve talked to dozens of e-commerce teams across Czech Republic and Slovakia. A common pattern emerges:
| Activity | Time per product |
|---|---|
| Product prep (unpack, clean, position) | 2-5 min |
| Capture (multiple angles) | 3-8 min |
| Post-processing (background, crop, color) | 5-15 min |
| File management (rename, organize, upload) | 2-5 min |
| Review and approval | 3-10 min |
| Total | 15-43 min |
At 30 minutes average per product and a loaded labor cost of 400 CZK/hour, each product costs roughly 200 CZK in time alone – before any equipment or software.
For a catalog of 1,000 products, that’s 200,000 CZK in labor. For seasonal refreshes and new arrivals, multiply accordingly.
What changes with a compressed workflow
The goal isn’t to eliminate every cost – product photography will always require human judgment and real products. The goal is to compress the pipeline.
When capture, processing, and export happen in a single flow on one device:
- Time per product drops to 1-3 minutes for standard catalog shots.
- Coordination disappears because there’s no handoff between capture, editing, and upload.
- Consistency is built in, not manually enforced – removing the rework loop entirely.
- Scaling becomes linear with products, not with people and equipment.
This doesn’t replace professional photography for hero shots or lifestyle images. It handles the bulk – the 80% of catalog images that need to be correct, consistent, and fast, not artistically unique.
Run your own numbers
Take your last month. Count the products photographed. Estimate the total hours involved – not just shooting, but the full chain from “product arrives” to “photo is live on the site.”
Divide total hours by products. Multiply by your loaded hourly rate.
That’s your real cost per product image. For most teams, it’s 3-5x what they think it is.