Product Photography Workflow: From Shot List to Approved Asset
A dependable product photography workflow is a sequence of decisions, not a pile of camera files. It connects the SKU list, visual brief, capture settings, file names, review notes, retouching limits, exports, and final channel assignment. When each stage has a clear owner and pass condition, the studio can move quickly without losing product accuracy.
The most useful principle is to separate capture truth from creative variation. First produce an accurate, repeatable source image. Then create channel-specific crops, lifestyle scenes, on-model views, and campaign assets from an approved source set.
Start with the deliverable map
Do not begin with “photograph every product.” Begin with the places the images will appear and the buyer question each place needs to answer.
Deliverable | Buyer question | Capture requirement | Typical output |
|---|---|---|---|
Main PDP image | What exactly is this? | Clean view, true color, complete product | Square or adaptable master |
Alternate angle | What is the construction? | Consistent camera height and rotation | Three-quarter or side view |
Detail | What is the material or finish? | Close focus and controlled reflections | Tight crop |
Scale image | How large is it? | Reliable reference or on-body context | Lifestyle or on-model frame |
Campaign image | Why should I care? | Art direction and negative space | Channel-specific crop |
This map prevents two common mistakes: overshooting images with no destination and discovering after the set is gone that a required angle is missing.
Build one source of truth before shoot day
Create a production table with one row per SKU and these required columns:
SKU and product name;
variant, color, size, or finish;
shot types required;
styling notes and non-negotiable details;
props or models needed;
filename stem;
capture status;
retouch status;
approval owner;
final asset links.
The source-of-truth table should be boring. Its job is to prevent ambiguity. Keep mood boards, references, and creative options in the brief, but keep production status in a structure that can be filtered and audited.
Use a gated seven-stage workflow
Stage | Owner | Pass condition | Handoff |
|---|---|---|---|
1. Intake | Producer | SKU data and samples agree | Approved product list |
2. Brief | Creative lead | Every image has a job and reference | Locked shot list |
3. Prep | Stylist | Product is clean, complete, and labeled | Ready rack or tray |
4. Capture | Photographer | Exposure, focus, color reference, and angle pass | Tethered selects |
5. Select | Creative and ecommerce | Coverage is complete before teardown | Approved selects |
6. Retouch | Retoucher | Product truth remains intact | Master files |
7. Export | Ecommerce owner | Channel rules, names, crops, and metadata pass | Published asset set |
Shopify’s current product photography guidance recommends keeping the camera and tripod in the same position for consistency and using the highest available image quality. Those small capture disciplines reduce downstream correction and make SKU grids feel coherent.
Lock the camera, light, and color reference
Repeatability matters more than a clever setup that cannot survive the next product. Mark the tripod position, camera height, sweep edge, key light, fill cards, and product center. Record focal length, aperture, ISO, white balance, and light power. Include a neutral or color reference at the start of each lighting setup.
Use one lighting family for a collection unless a material requires a deliberate exception. Glass, polished metal, velvet, and translucent packaging may need different modifiers, but the exception should be documented so the next batch can reproduce it.
Shoot tethered when possible. Review focus, surface defects, reflections, and edge shape at working size while the product is still on set. A two-minute correction during capture is more reliable than reconstructing missing detail later.
Separate correction from invention
Retouching may remove dust, normalize a background, balance exposure, and correct color toward the physical reference. It should not quietly change a product attribute.
Edit | Usually acceptable | Escalate before approval |
|---|---|---|
Dust and temporary lint | Yes | No |
Background cleanup | Yes | If it removes a product edge or transparency |
Color correction | Yes, toward the sample | If it creates a different sellable color |
Shape correction | Minor perspective only | If silhouette, fit, or volume changes |
Label repair | Only from verified source art | If text or claims are reconstructed |
Generated scene | As a clearly managed derivative | If product details are regenerated or obscured |
This boundary protects the asset library. A master should be a reliable record of the product. More interpretive derivatives can branch from it without replacing it.
Name files for systems, not humans
Use a stable pattern such as sku-variant-view-version.ext. For example, LA204-oxblood-front-v01.jpg is more useful than final-red-top-new2.jpg.
Keep the master independent from channel crops. A single master can feed square PDP, vertical social, and landscape campaign exports. Stable names and URLs also matter in commerce feeds. Google Merchant Center recommends using stable image URLs and changing the URL when the actual image changes. Review the current Merchant image specification before export.
Run proof checks before teardown and before publish
Checkpoint | Question | Evidence |
|---|---|---|
Coverage | Is every required SKU and view present? | Shot list has no unexplained gaps |
Product truth | Does color, pattern, material, and hardware match? | Side-by-side source comparison |
Technical | Are focus, edges, transparency, and reflections controlled? | 100% zoom review |
Consistency | Do adjacent products share scale and horizon? | Contact sheet review |
Distribution | Does each export meet its channel job and rules? | Channel-specific checklist |
Google says the main product image should accurately display the item and match submitted attributes such as color, pattern, and material. It also prohibits placeholders and promotional overlays in the main feed image. These are distribution constraints, so they belong in the workflow before publishing, not in a forgotten note after rejection.
Add generated variation after the master passes
Once the source set is approved, Look Atlas can create studio, lifestyle, campaign, and on-model derivatives from product imagery. This is where Look Atlas fits in the workflow: after capture truth is locked and before channel export.
Use the broader professional product photo guide for capture fundamentals. Then define which variations are safe to generate and review every derivative against the same product-fidelity checklist. Current plan details should be checked on the Look Atlas pricing page rather than copied into a durable workflow document.
The operating rule
One approved source should lead to many controlled outputs. Do not let every channel create its own undocumented version of the product. A workflow earns its value when the team can answer three questions immediately: which image is authoritative, why was this derivative created, and who approved it?