The third "can you just…" landed on Thursday. Same SKU. Same proof set. A new angle the brief never named — and the retoucher was already halfway through fixing it for free.
Nobody had lied. The studio also had no written rule for classifying that ask. So the path defaulted to whatever felt polite in the thread.
A product photography revision policy is the classification rule that stops that default. It decides whether a client request stays in retouch, goes back to set, or becomes a re-scope — before the work starts, not after the invoice argument.
A revision policy is a classification rule, not a vibe
A product photography revision policy states how the studio classifies a client request against the approved scope, which operational path follows, and who inside the studio makes that call.
It is not "we'll be flexible" and it is not a universal round count copied from another studio's FAQ. Flexibility without a rule just means the softest person on the team absorbs the work.
If you still need the commercial buckets — correction, requested change, new requirement — and how they affect price, use the pricing guide. If you need how labels appear in the review UI, use online proofing for product photography. This post owns the decision tree those pages assume exists.
Start from what was approved, not from the latest comment
Measure every request against the current approved records — not against the loudest message in the thread.
- Working brief: goal, destinations, exceptions, decision makers — see the product photography workflow map for where that record sits.
- Shot-list rows: one row per independently required output — the product photography shot list is the countable scope.
- Style guide version: background, crop, shadow, retouching boundaries — the style guide is the visual truth the proof was built against.
- Current proof version: which files the client is actually commenting on.
A comment that asks for something those records never included is not automatically a free revision. It may still be a good idea. It is a different path.
Three paths: stay in retouch, go back to set, or re-scope
Most client asks after a proof lands in one of three operational paths.
Revision (stay in retouch). The capture matches the approved requirement. The fix is post-production work inside the agreed treatment — cleanup, crop within the guide, color within the approved reference, removing a scuff the sample actually had. The set does not need to come back.
Reshoot (go back to set). The approved requirement still stands, but the capture cannot meet it in retouch without inventing product truth — wrong angle, missing view, lighting that cannot match the guide, damaged sample that was substituted without approval, or a composition the brief required and the files do not contain.
New requirement (re-scope). The client changes or adds a product, output, setup, destination, schedule, treatment, or decision that was not in the approved records. That is not a revision of the current proof. It is a scope change — commercially treated in the pricing guide, operationally tracked as a new or revised job slice.
In the review tool, those paths show up as labels — revision, reshoot, client decision needed, new requirement. Online proofing for product photography covers how to apply the label without hiding the type of work. The policy decides which label is true. The label does not decide who pays; the client agreement does.
"Included revisions" is a studio choice — write it before round two
Studios love to ask how many revision rounds to include. There is no universal answer that fits every ecommerce job.
What you must do is state the boundary before the second "can you just…" arrives. That boundary can be a round count, a scope boundary ("included revisions correct the current proof against the approved brief and style guide"), or a hybrid. The pricing guide deliberately refuses to prescribe a universal number — copy that discipline into your policy. Inventing "two free rounds" because a competitor's FAQ said so is how you train clients to spend both rounds on new requirements.
Write what happens when the boundary is hit: pause and re-scope, quote additional retouch time, or schedule a reshoot under the agreement. Silence here is how free work becomes the culture.
Use the retouching checklist before you book the set again
Before you call something a reshoot, run the request through a hard retouch check. The product photo retouching checklist is the practical list of what post can honestly fix. If the ask is dust, edge cleanup, background uniformity inside the guide, or a crop the style guide already allows — stay in revision.
Go back to set when retouch would have to invent geometry, lighting direction, a missing view, or product condition that was not in the capture. "We can fake it in Photoshop" is not a revision policy. It is a risk decision about product truth, and ecommerce clients notice when the packshot and the sample diverge.
Also keep internal QC before the client ever sees the file. Product photography quality control is the pass/correct/exception step that should catch studio-caused misses so they never burn an "included revision" the client did not cause.
Who classifies the request inside the studio
One named person classifies the path. In a 3–10 person studio that is usually the producer or lead who owns client-facing decisions — see product photography team roles for the standing ownership map. The retoucher can recommend. The photographer can flag capture limits. The client does not get to rename a new requirement as a free revision by tone alone.
When feedback arrives in three channels — portal comment, email, Slack screenshot — the classifier consolidates it against the current proof version before anyone starts pushing pixels. Scattered "yes" replies are how two people each start a different path on the same SKU.
If email is already the review system and it is breaking, the client approval portal comparison is the category read. The policy still matters either way: a portal without classification rules just organizes the same fight.
Say the path in one plain sentence
Clients escalate when the studio sounds uncertain. Use language that names the path and the next step — not a lecture.
- Revision: "We'll treat this as a revision against the approved proof — cleanup on SKU-014 front within the current style guide, then a new proof version."
- Reshoot: "This needs a reshoot — the approved brief requires a 45-degree view we do not have in capture. We'll schedule set time under the current agreement."
- New requirement: "This adds a lifestyle setup that was not in the shot list. We'll send a revised scope before production continues."
Do not invent fee amounts in the chat. Point to the agreement and, when needed, a revised proposal. The policy classifies. Counsel-reviewed terms decide payment.
Copy-ready revision policy checklist
- Name the classifier (producer/lead) for client-requested changes after proofing.
- List the truth records: brief version, shot-list version, style-guide version, current proof version.
- Define revision: post-production fixes that meet the approved requirement without new capture.
- Define reshoot: approved requirement still stands; capture must return to set.
- Define new requirement: product, output, setup, destination, schedule, or treatment not in the approved records.
- State the included-revision boundary (count, scope rule, or hybrid) in the proposal/agreement — no silent default.
- State what happens when the boundary is hit (pause, re-scope, additional work path).
- Require a retouch-vs-set check before booking reshoot time.
- Require internal QC before client proofs so studio-caused misses do not burn included revisions.
- Use one review record; consolidate off-channel feedback before classifying.
- Reply with one-sentence path language (revision / reshoot / new requirement) plus the next step.
- Keep commercial treatment in the agreement; do not invent fees in the comment thread.
When the job record has to carry proof versions, requested changes, and the classified path in one place, Lenso for studios is built for that lineage. It does not write your policy or decide who pays — that stays with the studio and the agreement.
FAQ
What is the difference between reshoots and additional photography?
A reshoot returns to set to meet an already approved requirement the current capture cannot satisfy. Additional photography usually means new outputs or setups that were not in the approved shot list — closer to a new requirement than to fixing the current proof. Use your brief and shot-list rows to tell them apart.
What counts as a revision vs a reshoot in product photography?
A revision stays in retouch when the capture already matches the approved requirement and the fix is within the agreed treatment. A reshoot is required when meeting that same requirement needs new capture — missing angle, wrong lighting geometry, product state, or a view the files do not contain.
How many revisions should be included?
There is no universal count. The studio and the current agreement decide the boundary — a round number, a scope rule, or both. The pricing guide FAQ takes the same stance. Write the boundary before proofing starts so "included" is not invented mid-thread.
Who pays if the client asks for a reshoot?
The client agreement decides payment. The revision policy only classifies whether the ask is a reshoot, a revision, or a new requirement. Studio-caused misses caught in internal QC should not be billed as client-caused reshoots. Client-caused scope changes should not be absorbed as free revisions by habit.
When should a studio retouch instead of reshooting?
Retouch when the fix can meet the approved requirement without inventing product truth or geometry the capture lacks. Use the product photo retouching checklist as the practical gate. If you would have to fabricate an angle, a lighting direction, or a missing view, book the set.