Quality control is the studio's internal review of the actual proof or release set against the current requirements.
It asks two broad questions:
- Is the required set complete?
- Does each file match the approved requirement?
Quality control is not the same as retouching.
It is not the same as client approval.
It is not a certification.
A useful QC process identifies the requirement, reviewer, file or set, disposition, evidence, and next action before the work moves forward.
Keep three review stages separate
Retouching self-check
The maker checks the current edit against the retouching instruction and output requirement.
Internal quality control
The studio reviews the whole required set and the final or proof files against the current job record.
Client review
The client comments, requests changes, or approves the named proof or set.
The same person can perform more than one stage on a small team.
Keep the decisions distinct.
Do not call a retoucher's self-check a client approval.
Do not ask the client to become the studio's only completeness check.
Define the source of truth
QC needs a current requirement.
Use:
- Client agreement for legal and commercial terms
- Current job brief
- Current shot list
- Current photography style guide
- Approved references
- Current official channel source
- Accepted exceptions
- Current delivery manifest
Do not inspect against memory.
Do not use the previous job without confirming that its requirement still applies.
Name the review unit
Choose what the QC record covers.
Examples:
- One proof
- One SKU set
- One gallery
- One release batch
- The complete final delivery
Identify:
- Job
- QC record or batch
- Files reviewed
- Reviewer
- Date
- Requirement versions
- Current release state
A broad label such as:
Finals checked
does not explain which files were reviewed.
Use four dispositions
Pass
The file or set meets the current requirement.
Correct before release
The studio can correct the issue before the work moves forward.
Client decision needed
The current requirement is incomplete, conflicting, or requires an authorized client decision.
Accepted exception
An authorized decision maker accepts a named deviation for the affected file, SKU, or set.
These are operational labels.
They do not decide:
- legal responsibility;
- price;
- refund;
- liability;
- contractual acceptance.
Review completeness first
Use the current shot list or manifest.
Confirm:
- Every required product or SKU is represented
- Every required variant is represented
- Every required view or asset is present
- Every required alternate crop or format is present
- No required file is only a placeholder
- Known missing outputs have an accepted exception
- Every final file maps to a current row
- Every manifest entry exists
- Every delivered file belongs in the release set
Completeness is a record comparison.
It is not an aesthetic judgment.
Review product identity and truth
Confirm:
- The file shows the correct product
- The visible variant matches the row
- The quantity and included accessories are accurate
- The label and package belong to the product
- Retouching did not invent or remove an unapproved feature
- Permanent product characteristics remain accurate
- A damaged or substituted sample follows the recorded client decision
Do not assume a similar thumbnail belongs to the same variant.
Use the stable product identifier and current reference.
Review the visual and technical result
The full copyable checklist covers eight areas:
- Required set and product identity
- Product truth and visible condition
- Framing, crop, scale, and composition
- Background, edges, shadows, and reflections
- Color and retouching
- Technical output
- File identity and manifest
- Approval, release, and delivery
Use the current Product Photography Quality Control Checklist.
Do not recreate a shorter universal standard in this article.
Choose the reviewer deliberately
A maker self-check is useful.
Naming a reviewer for this pass is one instance of a standing accountability — product photography team roles covers who owns QC as a role when the same people also shoot and edit.
That choice matters more, not less, on a deliverable that did not come from your own floor — a partner studio covering overflow capacity still earns full review, not a lighter pass because someone else already looked at it.
A second reviewer can be useful when:
- the set is high risk;
- the reviewer can see the current requirement;
- the studio needs independent confirmation;
- the client agreement or internal policy requires it.
A second reviewer is not universally required.
A person other than the maker is not automatically more qualified.
Record the reviewer and evidence.
Decide what receives full review
The studio can choose full review, structured sampling, or a combination according to:
- client agreement;
- product risk;
- channel risk;
- color sensitivity;
- file count;
- repeatability;
- automated checks actually available;
- consequences of a missed issue.
Do not publish a universal sampling percentage.
Do not sample the required-set reconciliation.
The studio should still confirm that every required output is accounted for or has an accepted exception.
When sampling is used, record:
- Population
- Sample rule
- Sample size
- Reason
- Result
- Expansion rule after a failure
Illustrative example
A studio has a release set for ten products.
The QC record says:
- Review unit: Final release batch
- Requirement: Brief version 4, shot list version 3, Account Guide version 2
- Completeness: Every required row reconciled
- Full review: Main product-page images and color-critical variants
- Sample review: Secondary detail exports under the recorded sample rule
- Disposition: One correct-before-release filename issue
- Final result: The corrected release set passed the recorded checks
This example does not prescribe a sample percentage.
Record the issue, not only the correction
A useful QC issue record contains:
- File or SKU
- Checklist area
- Issue
- Disposition
- Owner
- Correction or decision
- Evidence
- Date
- Resolved state
Do not write only:
Fixed
The record should explain what was fixed or accepted.
Handle a systemic issue
When the same issue appears across several files:
- pause the affected release;
- identify the shared requirement or production step;
- define the affected population;
- correct or review the full affected population;
- update the brief, style guide, shot list, or retouch instruction when needed;
- record the final disposition.
Do not claim that a QC log guarantees the issue will not recur.
The log gives the studio evidence for a process review.
Keep internal QC separate from client review
The client can still identify a problem.
The studio should not describe client review as a substitute for internal QC.
Use the client review for:
- current creative direction;
- requested changes;
- authorized decisions;
- accepted exceptions;
- approval.
Use internal QC for the studio's current release and proof check.
The same issue can affect both stages.
Keep the records distinct.
QC before proofing and QC before release
Some studios use two gates.
Before client proofing
Check that the proof set is complete enough and technically appropriate for the client decision.
Before final release
Check the actual final files, delivery names, manifest, access, and release set.
Do not assume that an approved preview proves the final exported file is correct.
Test the actual download or release path.
Placement matters as much as the checks. The post-production workflow runs internal QC before client proofing, not after — this post owns what to inspect at each gate; that one owns when in the sequence.
Channel requirements remain separate
Amazon, Shopify, retailers, marketplaces, and client-owned systems do not share one universal image standard.
Use:
- current official source;
- correct region;
- correct category;
- correct theme or placement;
- client requirement;
- review date.
A client instruction can be stricter than a platform minimum.
The Quality Control Checklist includes current source-maintenance guidance.
What Lenso records
Lenso can retain:
- current brief;
- product and shot rows;
- proof versions;
- comments;
- requested changes;
- approval;
- optional invoice;
- final files;
- manifest and release context.
Lenso does not currently inspect the image and determine:
- whether color matches the physical sample;
- whether the crop is creatively successful;
- whether retouching is truthful;
- whether every marketplace rule is met;
- whether the file is legally acceptable.
A qualified person still reviews the work.
Copyable QC process record
This is a process record, not the full image checklist.
- QC RECORD
- Job:
- Review unit:
- Files or set:
- Reviewer:
- Review date:
- REQUIREMENTS
- Client agreement reference:
- Brief version:
- Shot-list version:
- Style-guide version:
- Channel source and review date:
- Accepted exceptions:
- REVIEW METHOD
- Completeness review:
- Full-review population:
- Sampled population:
- Sample rule:
- Expansion rule:
- DISPOSITIONS
- Pass:
- Correct before release:
- Client decision needed:
- Accepted exception:
- ISSUES
- File or SKU:
- Checklist area:
- Issue:
- Disposition:
- Owner:
- Correction or decision:
- Evidence:
- Resolved date:
- RELEASE
- Final set:
- Manifest:
- Actual download tested:
- Recipient:
- Release date:
- Access expiry or revocation:
Use the full Quality Control Checklist for the actual review areas.
Questions about product photography QC
Is retouching the same as QC?
No. Retouching changes the image. QC checks the current work and release set against the requirement.
Should the client perform QC?
The client can identify issues and make decisions. The studio should not rely on the client as the only internal review.
Does every file need a second reviewer?
Not universally. Use a reviewer and method appropriate to the job, risk, and agreement.
Can the studio sample a large set?
The studio can use a documented sampling method where appropriate. Completeness still needs to be reconciled across the required set.
Does passing the checklist guarantee channel acceptance?
No. Third-party systems control their own acceptance and can change requirements.