All product image guides Product photography brief template

Agree on the deliverable before making the image.

A prompt describes one generation attempt. A photography brief agrees the job between a client and the people making, reviewing and publishing the assets. Give them the real product evidence, a defined image role and a clear approval route.

Explore one brief-approved direction Two free credits when you sign up. Review the result before publishing.
Existing live Fayvoro bottle scene, not a stocked customer product
LIVE FAYVORO RESULT
01 / EXAMPLEGENERATED WITH FAYVORO
What this shows

Use a concept to discuss a direction.

The live bottle scene can illustrate warm interior lighting in a planning conversation. It is not a client-approved brief, a delivered customer asset or evidence that a branded product would be retained accurately.

Unbranded bottle reference made for the Fayvoro demonstration
Input photoReference used for this demonstration.
Existing live Fayvoro bottle scene, not a stocked customer product
Live Fayvoro resultAn existing live photo-to-scene demonstration with an unbranded bottle. It is not a customer asset, a calibrated color test, or proof of exact product preservation.

This is one demonstration result; your result may differ. AI can change product shape, color, packaging, labels, and text. Check every important detail against the real item.

02 / A PRACTICAL WORKFLOWSTART WITH YOUR PHOTO
01

State the buyer question and image role

Name the product and variant, the buyer who will see it, and the question the image should answer. “Show how the bottle fits on a small bathroom shelf” gives a secondary scene a purpose. “Show the exact front label” calls for a factual real capture or precise verified edit. Do not let an atmospheric reference replace required evidence.

List where each deliverable will appear and who owns the destination rules. Keep a required real-photo set separate from optional scenes or text-only concepts. Agree whether the output is a finished flat image, a cutout layer or an editable composition before estimating the work.

Scope a specific retouch — Separate cosmetic cleanup from a changed product fact before handing off edits.

Check permission for the source image — Record who owns the photo and whether the intended edit and upload are permitted.

02

Explain what each reference contributes

Use a small reference set with notes: one shows light, another shows surface texture, and another shows the amount of empty space. Include an example to avoid if that helps define the boundary. Record that references communicate a direction rather than permission to copy another seller’s image or logo.

Attach your own product photographs and specifications separately. Mark immutable facts such as package count, label text, dimensions and stocked color. A mood board may guide atmosphere; it cannot approve a changed product, invented accessory or unverified physical claim.

Choose mockup, concept or real capture — Match the image method to design approval or evidence of an item for sale.

03

Make the handoff testable

Record asset roles and quantities, formats, dimensions or crop needs, naming pattern, destination and deadline. Clarify who supplies the original photos and who handles final export. If exact dimensions or destination requirements are unresolved, mark them as open decisions instead of copying a guessed standard.

Define review stages for product facts, visual direction and final-file delivery. Name the client approver and the person responsible for each repair. Agree a revision scope and budget directly with the team; this template does not quote photographer work, grant image rights or create a contract.

Plan the garment layers to capture — Keep real neckline and interior evidence for a hollow-garment composite.

04

Approve a pilot before extending the set

Start with one representative product and one intended placement. Keep feedback attached to a file revision and classify it as factual correction, technical repair or scene direction. Once the owner has accepted that pilot, document what should repeat for the remaining real products.

If Fayvoro is part of the pilot, use it only for the agreed scene or concept task. It does not manage client approval, generate a guaranteed consistent multi-SKU catalog or produce editable layered files. The builder below creates a planning note while this page is open; copy it into your existing handoff and obtain the actual approval there.

Keep image selection tied to a revision — Use a contact sheet to approve direction without confusing source and final files.

Client-to-creator brief

Make the handoff
clear to the people involved.

Build a planning note for a photographer or designer. Empty fields remain unresolved. It does not generate an image, send a brief, save a record or obtain approval.

This handoff is distinct from a generation prompt: it defines evidence, deliverables and responsibilities. Obtain agreement through your existing client workflow before extending the pilot to a batch.
Direction to try

A useful starting note.

Use this as a starting point, then adjust it for your own product. No prompt can guarantee exact product details.

Explore one secondary scene from my own product reference in the direction agreed with my client. Use a calm surface and leave room for the specified crop. The client will verify the actual product facts and exported revision before the asset is delivered.
Before you publish

Check the details.

  • The buyer question, real product identity and image role are agreed.
  • References specify a visual purpose and do not replace factual evidence.
  • Deliverables, export owner, deadline and unresolved decisions are listed.
  • A named client approver signs off the exact pilot revision before batch work.
Common questions

A few things to know.

How is this different from a generation prompt?

The brief assigns deliverables, source evidence, responsibilities and approval between people. A prompt is only one instruction used to create a candidate image.

Does copying the template approve the project?

No. It is a planning note. Share it through your existing client workflow and obtain real agreement on scope, rights, budget and the final assets.

Can Fayvoro enforce this brief across every SKU?

No guaranteed catalog consistency or approval automation is offered. Test one appropriate scene, compare it with the source and review each product separately.

Make your image
with intention.

Explore one brief-approved direction