Product Photography Workflow: Four Gates From Intake to Publish
A reliable product photography workflow moves each SKU through four release gates: intake, capture, master, and distribution. Nothing advances because it “looks done.” It advances when the next person can identify the exact product, see the evidence, and confirm the pass condition.
This page is the operating system around the shoot. Camera technique belongs in the professional product photography guide, while a detailed shot list should remain its own working document. The workflow below controls how those inputs become approved assets without losing product truth or ownership.
The four gates make rework visible while it is still cheap to fix
The costliest workflow error is a late discovery: a missing back view after the set is dismantled, the wrong colorway after retouching, or a feed rejection after every crop has been exported. Each gate is placed before that kind of mistake becomes expensive.
Gate | Advance only when |
|---|---|
Intake | The physical sample, SKU record, variant, required deliverables, owner, and exception notes agree |
Capture | Coverage is complete and focus, reflections, color reference, scale, and product condition pass before teardown |
Master | Retouching preserves the sellable item, the approved file is versioned, and its source remains traceable |
Distribution | Every derivative has a destination, exact export preset, stable name, approval, and final URL or delivery location |
A SKU advances only when the next owner can verify the evidence.
The gates do not prescribe a studio size or camera brand. They prescribe evidence. A small seller working with a phone can use the same pass conditions as a larger tethered studio, with fewer roles and a simpler file system.
One production record follows the SKU through every gate
Do not make the mood board, chat thread, retouch folder, and ecommerce backend compete as four sources of truth. Create one production record per SKU and link every specialized document from it. A record is complete when a new operator can understand the product, expected deliverables, current state, and next decision without asking the original producer.
Here is a filled example, not a blank list of recommended columns:
Record: FW26-014
SKU and variant: LA204-OXB, oxblood, size M sample
Product: ribbed merino cardigan
Required use: PDP main, front, back, button detail, and one 4:5 editorial derivative
Product invariants: five horn buttons, deep V neckline, rib direction, oxblood color, straight hem
Sample condition: approved; lint removed; spare button bag excluded from frame
Capture setup: SET-KNIT-02; camera height and light positions marked; neutral reference captured first
Filename stem:
LA204-OXBCapture owner and status: photographer; complete pending teardown approval
Retouch boundary: dust and background cleanup allowed; no knit reconstruction or silhouette change
Approver: ecommerce merchandising lead
Master and exports: blank until the corresponding gate passes
Filled example: one SKU record carries source identity, required use, capture set, retouch boundary, approver, and release state.
The shot requirement is one field in this record, not the whole workflow. That separation prevents this hub from competing with the dedicated “product photography shot list” topic while still showing where a shot list belongs.
Gate one: intake resolves identity before anyone styles the product
Match the sample to the SKU and variant record before it reaches the set. Confirm color name, size or finish, included pieces, labels, packaging, and visible defects. If the ecommerce record says “oxblood” but the sample tag says “burgundy,” stop and resolve the source data rather than letting retouching make the decision later.
Attach the deliverable map to the record. Each requested image needs a destination and buyer question: identity, construction, texture, scale, use, or campaign mood. The producer may link to a detailed shot list, but the gate passes only when coverage and ownership are unambiguous.
Record exceptions at intake. A scuffed sample may still be approved for a distant lifestyle image but rejected for a macro detail. That decision should be visible before the photographer spends time hiding a defect that merchandising actually needed to see.
Gate two: capture ends only after a coverage review
Lock a repeatable baseline for each product family. Mark camera height, product center, key light, fill, background edge, focal length, aperture, ISO, white balance, and light power. Capture a neutral or color reference whenever the lighting setup changes. The values themselves may differ by product; the workflow requirement is that the setup can be identified and repeated.
When the camera and software support it, tethered capture makes the gate easier to enforce. Adobe’s current Lightroom Classic tethering documentation explains that a session can be segmented by shots and that shutter speed, aperture, ISO, and white balance can be controlled from the tether bar. More important operationally, the latest frame is available for a large-screen check while the product is still on set.
Review the contact sheet before teardown. Check every required view, then inspect focus, edges, transparency, reflections, surface defects, and any scale reference. A missing angle is a capture problem. It should not become a retouching request.
Conceptual illustration: a controlled product set with neutral references; this is not a photographed client coverage review.
Hold the set until the capture owner and approval owner agree that coverage is complete. If one person fills both roles, make the second pass after a short break and compare the contact sheet with the production record rather than relying on memory.
Gate three: the master records the product, not the retoucher’s imagination
Preserve the raw capture and create one approved master before making channel crops. Dust cleanup, background normalization, exposure balance, and color correction toward a physical reference can belong in the master. A new seam, reconstructed logo, altered silhouette, different stone shape, or invented label does not.
Use a retouch log for exceptions: what changed, why it changed, who approved it, and which file contains the revision. Name the master with stable identifiers such as sku-variant-view-master-v01.ext, not “final-new-2.” The exact convention matters less than uniqueness and traceability.
Approve the master in two views. At normal viewing size, check crop, scale, and consistency beside neighboring SKUs. At 100 percent, check focus, edges, surface texture, retouch artifacts, labels, and hardware. Compare color with the approved physical reference under a controlled viewing setup; do not use a memory of the sample as the standard.
The master gate produces one answer to “Which file is authoritative?” Creative derivatives can branch from it, but they never silently replace it.
Gate four: exports are recipes tied to destinations
An export is not “save as JPEG.” It is a named recipe containing destination, file format, color space, dimensions, crop behavior, compression, sharpening, metadata handling, and filename rule. Adobe’s current Lightroom Classic export guide documents those separate choices and the ability to save them as reusable presets.
Create one preset per actual destination, then record the preset version in the production record. For Shopify-specific source dimensions, crop behavior, and responsive-delivery checks, use the Shopify product image sizing guide. The PDP, marketplace feed, email, social, and print files may come from one master, but they are not interchangeable merely because they share a subject.
For Google listings, the current Merchant Center image specification says the main image must show the actual product and match submitted attributes such as color, pattern, and material. It also recommends stable image URLs and says to change the URL when the image itself changes. Those requirements belong inside the distribution gate, followed by a check of the live destination rather than an assumption that a successful upload equals a correct render.
Generated variation belongs after the master gate
Current Look Atlas review controls: approve a keeper, create or edit a variation, and export selected work. Demo data only.
Once the master is approved, a brand can create controlled studio, lifestyle, on-model, and campaign derivatives without confusing them with the documentary source. This is the point where Look Atlas can enter the workflow.
The current Look Atlas Studio organizes a shoot around selected products, cast, planned shots, a visual director, and generation settings. In the review room, a user can approve a variation, edit it, request another variation, inspect version history, and download selected work. The proof image above should show that real handoff using current authorized captures, not a fabricated interface.
Look Atlas does not remove the need for a verified source, an asset owner, or product-fidelity review. A generated derivative that changes the sellable item returns to review; it does not become a new master because the scene is attractive. Use the AI model photoshoot decision guide when choosing between campaign production, virtual try-on, and a physical shoot. Check the pricing page for current plan terms instead of embedding changing allowances here.
The handoff test
The workflow is healthy when another operator can open one SKU record and answer five questions without a meeting: What exact item is this? Which deliverables were required? Which source and master are authoritative? What was changed and approved? Where did each final file go?
If one answer lives only in someone’s memory, the SKU has not passed its gate. Fix the record at the point of uncertainty, then let the work move forward.
