Buyer revision scope
Request one fabric change, then review product details
Name the fabric change and the product details that must stay consistent. Try preset sofa colors, then request real swatches before approving the material.
By XinVise TeamPublished Updated


Built for this workflow
- Keep the real request distinct from assumed permission
- Name intended change and unchanged features
- Review output rather than count attempts as success
Keep the actual request and reference version
Record the supplied product/variant, current visual reference and the actual requested change using the approved process. State whether the request concerns a catalog fabric direction, a scene or another visual question; do not silently broaden it to a redesign.
A previous visual preference is not automatically physical or production approval. Retain source/version and required rights without including private buyer conversations or personal data in a public inquiry.
Resolve before-upload permission separately from the buyer's preferred appearance.
Name the change and the features to keep
Write the intended visible change and unchanged outline, modules, hardware, seams, text and logos. Public fabric previews select available catalog materials with sign-in and credits; owned textile or more controlled editing needs separate evaluation.
The written request does not add per-panel controls, exact instruction following or automatic version management. If the actual workflow cannot express the required scope, hold it and evaluate a suitable real capture, retouch or technical workflow.
Use the mixed-material boundary check for non-target surfaces.
Review the actual candidate and failed-attempt status
Compare the candidate to its source and requested purpose. Hold or reject changed product identity, uncertain article mapping or missing evidence before discussing preference. A successful request or additional image count is not a usable-result decision.
For failure, inspect the reported issue and existing account/generation status before repeating an uncertain action. Resolve input, access or credit issues first; service/limit issues are different. No free retry, refund, fixed allowance or guaranteed convergence is created by this guide.
Use the image-quality checklist and catalog access and credit boundaries, not an invented attempt budget.
Close with an explicit visual decision and open physical questions
Retain request/reference/candidate versions, selected fabric, allowed use, review role/date and accept/hold/reject reasons through the team's approved process. Changes in product, material or request require a new relevant review rather than an inherited pass.
Physical color, fit, material properties and construction still need actual samples/records and responsible approval. This guide supplies no customer approval system, automatic audit log, measured turnaround or sampling saving.
Keep the physical-sample boundary visible when communicating a visual choice.
Recommended process
- 01
Retain the actual request
Keep product/reference versions and the bounded requested visual change without exposing buyer conversations.
- 02
Name unchanged features
Use actual workflow controls and catalog access, not assumed exact editing or version features.
- 03
Inspect the whole candidate
Compare source and purpose; separate failure/status checks from any new request.
- 04
Record visual scope
Keep role/date, reasons and open material/technical requirements distinct from physical approval.
Workflow comparison
| Revision field | Manual reference | Not guaranteed |
|---|---|---|
| Request/version | Actual supplied change and source/product version | No inferred redesign or physical approval |
| Intended change | Declared visual direction and actual catalog selection | No exact editing or per-panel feature |
| Unchanged identity | Outline, modules, hardware, seams and labels | A nice texture does not excuse altered product |
| Attempt status | Reported issue and actual account/generation state | No free retry, refund or convergence promise |
| Review decision | Actual candidate, purpose, reviewer/date and reasons | Image count is not a usable-result or buyer acceptance rate |
| Open physical gate | Real samples/specifications and responsible owner | No automatic approval log or production authorization |
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 one requested change guarantee nothing else changes?
No. Review the whole candidate against its source and declared use; exact editing or preservation is not guaranteed by a written request.
Does a failed revision entitle me to a free retry?
No policy is created here. Check actual error, generation/account state and current terms before another request; access and credit requirements still apply.
Is this an automatic customer approval or version-control feature?
No. It is a manual reference and decision method through the team's approved process, not a new public approval system.
Does the buyer's visual preference approve the actual material?
No. Physical samples, specifications, fit/construction evidence and responsible approval remain separate from an image direction.
Bound the reference and change before previewing
When rights, visible scope, sign-in and credits are clear, compare one available catalog direction and review the actual result without a retry guarantee.
Open the fabric preview workflow