Before-upload permission
Resolve source permissions before processing the image, not after a candidate looks useful
For supplier, dealer or commissioned furniture imagery, identify the actual source and ask the responsible rights owner about the intended processing and use before submission. Keep relevant permission scope, restrictions and versions with the reference. This is a manual evidence checklist, not legal advice, an automatic rights detector or a grant of permission from XinVise.
By XinVise TeamPublished Updated


Built for this workflow
- Separate public visibility from actual permission
- Confirm relevant processing and intended-use scope
- Hold missing authorization before submission
Identify the source without guessing ownership
Record the actual image/source version and responsible supplier, photographer or other rights contact through the approved process. Do not assume the seller, uploader or person who can download the file owns every relevant right.
A publicly viewable image or supplier folder is not by itself evidence of permission to edit, process with AI or reuse it for the intended channel. If ownership or authority is uncertain, hold submission and consult the appropriate qualified owner.
Keep actual product/article identity separate using the BOM reference precheck; identity is not permission.
Ask about the actual processing and use
Define the proposed action, such as reference processing, upholstery alteration, scene creation or later publication, and the intended audience/channel. Retain the actual relevant permission or agreement, restrictions and applicable version with the authorized reviewer.
Do not invent a universal license, assume a supplier allowance covers every derivative use, or treat account credits as a rights grant. Public previews select catalog fabrics with sign-in and credits; owned collections and broader operations need separate evaluation.
The enterprise pilot checklist helps define operating scope without substituting for rights review.
Hold unclear scope and unnecessary private data
If permission, restrictions, permitted processing or the authority to confirm them is missing, leave the task held. A promising generated result cannot retroactively supply authorization. This guide does not decide legal ownership, interpret a contract or certify compliance.
Share only minimal approved references through the agreed process. Do not attach customer personal data, credentials, confidential collection contents or full agreements to a public inquiry. Any required private review needs its authorized channel and owner.
Use buyer change review only after the proposed change and rights scope are actually clear.
Keep permission limits with later delivery
Retain source/version, approved action/use, relevant permission reference, restrictions, review role/date and unresolved items. A changed source, use or permission needs re-review rather than automatic inheritance.
Actual publication, channel requirements and material claims remain separate decisions. No rights detection accuracy, commercial clearance, license coverage or legal outcome has been measured or guaranteed here.
The DAM handoff checklist retains delivery provenance; this page owns the before-upload permission gate.
Recommended process
- 01
Identify actual source and authority
Keep image/version and the responsible rights contact without assuming a downloader owns the rights.
- 02
Define proposed processing/use
Ask about the actual action, channel and restrictions using relevant permission evidence.
- 03
Hold unresolved permission
Do not submit missing-scope or unnecessary private data; obtain qualified review through an approved process.
- 04
Retain limits with delivery
Keep permission references, use, reviewer/date and revisions separate from software access.
Workflow comparison
| Permission field | Actual evidence to retain | Not established |
|---|---|---|
| Image source | Actual source/version and responsible rights authority | Download access does not establish ownership |
| Proposed processing | Defined alteration/reference/scene action | No blanket permission from a public image |
| Intended use | Actual audience/channel and relevant agreement scope | Credits or a software account do not grant reuse |
| Restrictions | Actual terms and qualified review when required | No universal license or legal interpretation |
| Data scope | Minimal authorized references and approved channel | Public inquiry is not permission for confidential uploads |
| Review record | Permission reference, role/date, limits and revisions | No automatic clearance or legal guarantee |
Sources and method
These primary sources support method and platform constraints; they are not third-party endorsements of XinVise product outcomes.
- Product image requirements
Google Merchant Center
Provides Google-specific accuracy and presentation context; it is not universal platform policy or legal advice.
- GS1 Product Image Specification
GS1
Provides an industry reference for product-image views, naming, versioning, and asset governance.
Frequently asked questions
Does finding a supplier photo online authorize AI processing?
Not by itself. Confirm actual source authority and relevant permission for the proposed action/use before submission.
Do account credits grant rights to supplier images?
No such grant follows from access or credits. Source permissions, restrictions and intended use need their own actual evidence and review.
Can XinVise automatically clear an image's rights?
No capability or legal clearance is established here. This is a manual checklist, and uncertain authority or terms require appropriate qualified review.
Should I send the full agreement or customer collection in a public inquiry?
No. Use minimal approved references and the authorized private process where needed, without credentials or personal/confidential contents.
Discuss the authorized reference scope
Bring minimal approved source identifiers and open processing/use questions, not confidential agreements or credentials.
Discuss permission-review scope