Why product photography service standards need a written baseline

What to take away

Why a written baseline beats goodwill

Most disputes about product photography are not about taste. They are about an unwritten expectation. A studio shoots what it thinks a white background means, while the retailer expects a specific shade and shadow.

A baseline fixes the definition. It states the file format, the crop, the colour treatment and the number of angles. It also states who checks delivery and how long that check takes.

That is the logic behind the wider product photography operations and delivery guide for 2027. Treat the 2027 in its title as a planning label, not a delivery date; the guide sets the delivery cycle around agreed checks rather than ad hoc reshoots.

Written standards also shorten onboarding. A new supplier can read the schedule and start work without a second briefing call, which matters when a range launches on a fixed date.

What belongs in the standard

A service standard should cover five areas: image specification, turnaround, revision limits, file naming and rights. Each one needs a number or a named owner, not an adjective.

Copy this one-page standard and fill in your own numbers:

A retainer example is £400 a month, and both sides can point to the same lines.

Specification matters more than most buyers expect. A PNG with transparency and a JPEG on a white background are different products. If the standard does not say which, the studio chooses, and that choice may not suit your marketplace listings.

Naming conventions look trivial until a catalogue grows. A pattern that carries the SKU, colour and angle keeps a feed tidy, and it makes a missing shot obvious to whoever checks the upload.

Ownership is the other common gap. Who holds the raw files, for how long, and what happens when the contract ends? Agree that in the contract before the first shoot.

Delivery checks before sign-off

A workable check has three steps. First, the file must open and match the agreed format. Then the product colour must hold against a physical reference or a previously approved image, and the naming convention must land it in the right catalogue folder.

Who signs the standard off

One named person should own the final approval. In larger teams that is often a studio manager or a content lead. The product photography team roles in England page sets out how those responsibilities usually divide between shoot, edit and publishing.

Before and after a written standard

The legal layer around the creative work

The creative standard does not sit alone. If you plan to use product images in email or paid social, the ICO guidance on direct marketing and privacy and electronic communications applies. It explains the UK GDPR and the Privacy and Electronic Communications Regulations (PECR) consent rules for electronic marketing.

Technical standards matter too. If a supplier claims to crawl your site on Google's behalf, check that claim against Google's guidance on verifying Googlebot rather than taking it on trust.

Delivery also depends on the platform itself. A marketplace can reject an image for a technical reason long before a buyer ever sees it, so keep the file rules beside the legal rules.

Neither rule changes how a product looks. Both change whether the image can legally and reliably reach the buyer.

Common questions

Does a service standard have to be a long document?

No. A one-page schedule covering format, turnaround, revisions, naming and rights is often enough. Length matters less than whether every line can be checked.

Who owns the images after the shoot?

That depends on the contract. Many studio agreements license the images rather than transferring copyright, so read the rights clause before you sign and agree the raw file position in writing.

How often should the standard be reviewed?

Review it when a marketplace changes its image rules, when a new supplier joins, or at least once a year. A standard nobody revisits stops matching what your listings actually need.