Supplier Product Photos as AI References: Permission Guide

Using supplier product photos as AI references starts with a question that belongs before the upload button: does your permission cover this file, this AI workflow, and the intended use? A supplier might send a perfectly usable packshot while leaving background replacement, advertising, or third-party processing unresolved.

Resolve that scope before producing candidates. Once the input set is approved for the planned workflow, you can open the Oxava studio, choose a reference-capable image model, and start production. Technical acceptance of a file does not establish permission to use it.

This guide proposes a practical input-permission record for retailers and agencies. It is an organizational workflow, not a legal opinion or an Oxava rights-checking feature. The US and UK sources below illustrate jurisdiction-specific principles; your contracts, local law, and target markets may require different analysis. Ask a qualified adviser when the legal basis remains uncertain.

Sources checked on October 25, 2026; recheck the terms relevant to your workflow before use.

The cover is a conceptual AI-generated illustration. The three briefs below are hypothetical, not examples of legally cleared campaigns.

Separate the photograph, the operation, and the destination

Start with four questions rather than one broad “commercial use” checkbox:

1. Who can authorize this photograph? Identify its origin and the person or organization entitled to grant the relevant permission.
2. What will happen to the file? Specify upload to the selected service, background editing, scene generation, reference reuse, or other planned operations.
3. Where will the results go? Name the business or client, channels, markets, and campaign period.
4. What else needs review? Flag people, artwork, brand restrictions, unreleased products, confidential details, and any approval obligations.

For a US example, the Copyright Office explains that the photographer is generally the initial copyright owner, with a limited work-made-for-hire exception. Paying for a shoot or selling the photographed product should therefore prompt a contract check rather than an ownership assumption. US Copyright Office photography guidance.

The questions also keep different decisions apart. Permission for an input, the generator's commercial terms, copyright in a resulting image, and the accuracy of the pictured product each need their own consideration. A favorable answer to one does not complete the others.

Keep this review ahead of the creative process in our AI product photography guide. Otherwise, a team can spend its approval meeting discussing lighting while the authority to upload the source remains undocumented.

Record permission for supplier product photos as AI references

Use an external document, spreadsheet, or asset-management record. The following is a proposed working format, not a legal standard. Give each reference a stable ID and connect it to the exact file version, even when several references arrive in the same supplier folder.

1. Identify the asset and its job

Record the original filename, your reference ID, the SKU and packaging revision where relevant, and the source location. Add the intended role: product identity, setting, composition, or lighting. A mood photograph needs review even if you only plan to borrow its atmosphere.

Keep the original separate from any approved working copy. A descriptive name such as MUG-42-front-v2 is easier to trace than final-new.jpg. If you later replace the image, create a new version rather than silently changing the file behind an old approval.

2. Link the permission evidence

Record who supplied the image, who is identified as the rights holder or authorized licensor, and where the applicable agreement or permission can be retrieved. Include the agreement version and any relevant attachment or order reference.

A sales representative may be the correct contact without being the person who can expand the license. Record that distinction. “Supplier emailed it” describes delivery; your reviewer still needs evidence addressing the proposed use.

3. Describe the proposed workflow

Write the actual service, account or workspace, and operation to be reviewed. “AI use” alone is too vague for useful clarification. Distinguish a one-off background edit from a reusable reference library, client handoff, or model-training project.

Do not infer training from the fact that an upload occurs. Check the relevant service terms and data-handling information for the particular route you intend to use. Record unanswered questions rather than filling them with assumptions about privacy, storage, or training.

4. Capture limits and the decision

List intended channels, markets, duration, required credits, permitted edits, and further approvals where applicable. Leave no ambiguous blank: use “not yet confirmed” when a material point is unresolved.

Finish with a reviewer, decision date, evidence link, and one of three internal states: ready for this workflow, hold for clarification, or replace this input. Add the next action. These states communicate your team's decision; they do not certify legal clearance.

Check each source on its own terms

Supplier portal or shared folder

Find the terms attached to the asset or supplier relationship. A download button is useful for obtaining a file, but your review should establish which downstream activities are covered. Check whether the permission identifies your business, an authorized retailer group, or another licensee.

For a UK example, government guidance explains that licenses may be limited by purpose, time, or place. That supports checking the planned campaign against the actual grant rather than assuming every marketing use travels together. UK guidance on using somebody else's copyright.

Commissioned photography

Retrieve the photographer's agreement and relevant delivery terms. Check the entity receiving the rights, editing scope, service-provider access, and client use. If the agreement already covers the workflow, record that basis; this checklist does not presume every project needs a new AI addendum.

Stock or style references

Read the applicable stock license, asset restrictions, and any separate permissions alongside the selected tool's terms. For example, Getty Images' agreement contains AI restrictions but also exceptions for internal cataloguing and permitted editing of licensed creative content, subject to limits concerning training, fine-tuning, and data ingestion. It should not be summarized as either “all AI is banned” or “all editing is allowed.” Getty Images content license agreement.

If a particular stock-and-tool combination remains unclear, seek clarification or choose a different, adequately documented input. Do not upload an unknown-origin screenshot to “make it original.” A polished result would leave the source question unanswered.

Your own photograph

An in-house shoot can make the photo's origin easier to establish. Still review relevant employment or contractor arrangements, depicted people, artwork, trademarks, and confidential information. Keep a clear view of the actual product, but do not treat personally pressing the shutter as a guarantee that every planned use is cleared.

Ask a question the rights holder can actually answer

The Library of Congress recommends identifying the rights holder and requesting written permission specifying the item and intended use. Library of Congress permission guidance.

For your project, assemble a short clarification brief:

• Files: exact reference IDs and filenames, with thumbnails if appropriate.
• Processing: the named AI service and proposed operations, including whether sources will be saved for later reuse.
• Deliverables: intended stills or videos and the business or client using them.
• Distribution: storefront, marketplace, paid advertising, or other specified channels, plus markets and period.
• Open point: the precise gap in the existing permission and who can resolve it.

Ask the contact to confirm their authority or route the request to the appropriate licensor. A helpful reply should connect the approved scope to identifiable files. If the answer addresses advertising but says nothing about the proposed processing, keep that remaining question visible.

Keep agreements and correspondence in an access-controlled business record. The generator needs the approved visual input, not an uploaded bundle of confidential contracts. This is a document-handling recommendation, not a statement about any service's privacy protections.

Use a short before-upload decision workflow

Apply this sequence to every file in the proposed reference set:

1. Origin or authority unclear? Hold that input and identify the responsible contact.
2. Operation or destination outside confirmed scope? Ask for clarification, narrow the brief, or replace the input.
3. Service terms or sensitive details unresolved? Route the specific question to the person responsible for contracts, privacy, or confidentiality.
4. Required evidence reviewed? Record approval for the exact file set and workflow, then release those inputs to production.

A tool accepting an image is not the missing review. Adobe's generative AI guidelines, for example, prohibit uses that violate third-party copyright, trademark, privacy, publicity, or other rights, including relevant reference-image inputs. This is an Adobe-specific illustration of user obligations, not an account of Oxava's terms. Adobe Generative AI User Guidelines.

Avoid a batch-wide green light when only one asset has been checked. Equally, keep a hold scoped to the unresolved inputs so the team can evaluate an independently documented alternative.

Three hypothetical briefs and their next actions

These examples demonstrate workflow decisions, not legal findings.

Brief 1: a mug packshot moves from listing to paid ads

A homeware supplier provides MUG-42-front-v2 for an unchanged retailer listing. The creative team wants to upload it to an AI editor, place the mug in a breakfast scene, and use the result in paid social advertising.

Record: the supplier permission addresses the existing listing; the proposed processing and advertising scope remain unconfirmed. The source photograph is identifiable, but the new brief is broader than the evidence on hand.

Decision: hold the AI edit while the account manager asks the authorized contact about those specific operations and placements. Continue the unchanged listing only within its existing confirmed scope. If the broader request is approved, attach that decision to this version of the mug photograph; do not extend it automatically to every supplier asset.

Brief 2: an in-house electronics shot reveals unreleased details

An electronics team has documented its authority to use a product photograph. A close view also contains a prototype serial label and a confidential launch identifier. The planned AI background replacement would send the full source to an external service.

Record: photo permission is addressed, but disclosure review is pending. A teammate's promise to remove the identifier from the final advertisement does not resolve what would be included in the input.

Decision: have the product and confidentiality owners approve a suitable source version before upload. That might mean a new photograph of approved retail hardware or an authorized, locally prepared working copy. Keep its version linked to the original record and confirm it still depicts the intended SKU accurately. Do not let the AI service be the first place the sensitive source is reviewed.

Brief 3: a serum scene combines three different sources

An agency selects a supplier's serum packshot, a licensed stock bathroom photograph, and a hand image from an earlier campaign. Each has a different evidence trail. Permission for the packshot does not answer the stock image's operation-specific conditions or the hand image's reuse questions.

Record: make three entries, even though the prompt will produce one composition. Mark the packshot's confirmed scope separately from the unresolved setting and person-related questions.

Decision: pause the combined input set. If the other references are unnecessary, revise the brief to a text-described setting without a person and use only the packshot once its intended workflow is approved. If the references are essential, obtain the missing review first. Record the revised set so an old attachment is not accidentally reused during production.

Hand off approved inputs without losing their limits

Give production a short handoff: approved reference IDs, permitted operations, destinations, restrictions, and the evidence owner. If a library is used, distinguish approved inputs from pending material rather than relying on everyone remembering a conversation.

Our named-reference guide covers how to assign technical roles and reuse references in supported workflows. A convenient reference name does not expand the permission attached to its underlying image. Revisit the record when the source, client, account, operation, or destination changes, or when a documented review date arrives.

Then perform a separate product review. Confirm that generated packaging, ports, closures, colors, and quantities match the real item. Use the SKU catalog quality-control workflow to track those checks without treating an input approval as visual approval.

Finally, follow the image export and destination guide for delivery. Metadata, attribution, and correct storefront assignment belong in that downstream handoff; none substitutes for the before-upload decision.

Resolve the input, then build the image

For supplier product photos as AI references, a useful permission record tells the next person which file can enter which workflow, where the result is intended to go, and who resolved the open questions. Keep uncertain inputs on hold, request precise clarification, and preserve the decision with the asset.

Once permission and the other required reviews are resolved, open Oxava with the approved reference set. Generate your candidates, compare them with the real product, and complete the separate output and destination checks before publishing.

Frequently Asked Questions

Can I use supplier photos if the supplier says “free to use”?

Connect that statement to the files and proposed workflow. Ask whether the contact can authorize the use and whether any existing terms limit processing, editing, or distribution. Keep the clarification with the asset record instead of relying on the phrase alone.

Is it enough to change the photo substantially with AI?

Do not use how different the output looks as your input-permission test. Resolve the basis for using the source before uploading it. If you intend to rely on a legal exception rather than permission, get advice for that specific use and jurisdiction.

Does a commercial AI plan provide permission for my inputs?

Review the plan's terms, but also establish the basis for using each source. An entitlement to use a service commercially does not document what your supplier or photographer authorized. Record those checks separately.

Does taking my own product photo settle everything?

It can simplify the source trail, but still check relevant agreements, depicted people or artwork, brand-related restrictions, and sensitive details. Approve the actual file and intended workflow rather than treating its in-house origin as a blanket clearance.