Operations
Part of How do you run product photography operations at scale?
What a product photography quality checklist means for studio operations
A product photography quality checklist for ecommerce teams, covering image files, alt text, colour checks, crawler access and when to report a breach.
What to take away
- A product photography quality checklist now covers accessibility, crawler access and personal data, not just sharpness and lighting.
- Alt text and contrast sit inside WCAG 2.1 success criteria, so image and web teams share the sign-off.
- Robots.txt rules decide whether image directories are crawled, which makes folder structure a commercial decision.
- Where a shoot involves identifiable people or customer data, a breach has a legal reporting clock attached.
- Each line needs an owner, a frequency and a piece of evidence.
Why the checklist has grown beyond the studio
A product image is now judged in a browser, a feed and a search index, so whoever signs off a shot signs off metadata and access rules too.
Accessibility is the clearest example. The WCAG 2.1 quick reference sets out success criteria for non-text content and contrast, and they apply to every image your team publishes. A crisp pack shot with empty alt text still fails a buyer using a screen reader.
Crawler access is the second shift. Image directories behind a blocked path will not be indexed, however good the photography. Google explains matching behaviour in its robots.txt specification guidance, which is worth reading before you reorganise a media library.
The checklist also has more readers than it used to. Retail marketplace teams and paid media buyers ask for the same evidence, often at short notice, and each of them wants it presented differently.
The checklist, grouped by what it protects
File and naming checks
- File names describe the product, for example red-cotton-shirt-front.jpg rather than IMG_4471.jpg.
- Each variant carries a stable suffix such as -front or -detail, so replacements do not break a page.
- Folder paths mirror the site structure, so one category maps to one image directory.
- Deleted or retired files are logged, not simply removed from the server.
- Master files are versioned, so a second retouch never overwrites an approved image.
Metadata and accessibility checks
- Alt text describes the product and its visible state in one short sentence.
- Decorative crops carry empty alt attributes.
- Contrast between overlaid text and the image meets the relevant success criterion.
- Alt text describes what is visible rather than repeating the product name.
To see who owns each line, the product photography team roles in England article maps tasks to job titles, which helps when a checklist item has no obvious owner.
Colour and fidelity checks
- A reference target appears in the first frame of every lighting setup.
- Skin tones, fabric and metal finishes are checked against that target, not against memory.
- The published file matches the approved proof after final export, not only on the studio monitor.
- A monthly sample of live pages is checked, because content delivery networks can alter files.
- Screens are calibrated on a schedule, and the calibration record is filed with the shoot.
Access, rights and data checks
- Model and property releases are filed against the shoot reference.
- Consent records state where an image may appear, including paid placements.
- Raw captures and retouched files are limited to named staff.
- A breach involving identifiable people or customer images follows the ICO's reporting a breach process, which sets out the 72-hour notification window.
- Consent is captured in writing at the shoot, not reconstructed months later.
Checks by owner and frequency
| Check | Typical owner | Frequency | Evidence |
|---|---|---|---|
| Alt text present and accurate | Content editor | Every publish | CMS audit log |
| Colour target in first frame | Studio lead | Every setup | Capture sequence |
| Robots.txt allows image paths | Technical SEO | Quarterly | Crawl report |
| Release and consent filed | Producer | Every shoot | Rights folder |
| Live page sample review | Ecommerce manager | Monthly | Signed sample sheet |
| Breach route understood | Data protection lead | Annually | Training record |
A checklist that names owners but no evidence drifts within two quarters. Adjust the frequencies to your volume.
Evidence can be modest. A timestamped audit log entry, a signed sheet or a screenshot all work, provided a reviewer who was not in the room can see that the check happened.
The wider delivery picture, from briefing through to archiving, sits in the operations and delivery guide for 2027, which places this checklist inside a full workflow rather than treating it as a standalone document.
Common questions
How often should the checklist be reviewed?
Review the full list once a year, and the crawler and accessibility lines quarterly. A platform change, a site migration or a new lighting setup all trigger an out-of-cycle review.
Who signs off a product image before it goes live?
The content editor or ecommerce manager signs off the published asset; the studio lead signs off the capture. Splitting the two signatures stops a good shot going live with poor metadata.
What happens if a customer image is exposed by mistake?
Treat it as a personal data breach. Assess the risk, record the decision, and if notification is required, use the ICO route within the stated window.
