Mix-reference naming scope
A useful image label preserves the actual mix without inventing included products
For a supplied sofa and pillow/cushion mix, identify actual item roles, article references and source/candidate/final versions before naming or archiving assets. Keep unknown items and commercial inclusions open. This manual reference checklist does not create automatic object recognition, separate fabric assignment, a DAM import or evidence that pictured accessories are included in a sale.
By XinVise TeamPublished Updated


Built for this workflow
- Keep main sofa and actual pillow/cushion roles separate
- Preserve article and image versions through naming
- Distinguish an archive label from commercial inclusion
Identify the actual items and material references
Retain supplied main product/variant and actual throw-pillow or seat-cushion references. Record position or role only when identified; a decorative object in a scene is not automatically a separate sellable item or confirmed material.
Keep main and accessory articles distinct, with unknowns held. Do not infer removable, washable, compatible or included status from a generated cushion or a plausible matching pattern.
Use the BOM reference precheck and option-combination review.
Agree naming fields without changing identity
Keep actual main-product, accessory/role, material reference, view and image version in the agreed naming/reference process. Distinguish original photo, catalog reference, generated candidate and actually reviewed final asset.
A readable label is not permission to relabel old material as a new article or guess an unidentified cushion. Resolve collisions or ambiguous versions through the actual owner rather than assume the newest filename is approved.
Use the supplier namespace precheck before joining short color codes.
Keep archive and editing capabilities separate
Use the actual authorized destination and receiver requirements for source/candidate/final references. This page does not rename or store real files, import a DAM, auto-tag objects or establish access-control/retention software.
Public previews need sign-in, credits and catalog scope; a mix description does not create separate pillow/seat fabric controls or owned-library import. Physical compatibility, construction and commercial bundle terms remain separate.
The DAM checklist owns general delivery, and the scene-bundle review owns inclusion claims.
Confirm actual receipt and open reference gaps
Retain agreed naming fields, actual item/article/file versions, intended use, reviewer/date and receiver confirmation. Planned delivery or an archive label is not proof of receipt, publication or physical set approval.
Share minimal approved identifiers without customer orders or credentials. No asset-matching accuracy, archive coverage, sales result or material equivalence is measured or granted here.
Use the image/copy claim crosscheck before making mix or bundle claims.
Recommended process
- 01
Identify actual mix roles
Keep main product, real accessory/seat roles and articles with unknowns held.
- 02
Agree reference naming
Retain view, source/candidate/final role and actual version without guessing a new identity.
- 03
Use the authorized archive process
Confirm destination requirements without claiming tagging/import or per-object editing software.
- 04
Confirm bounded handoff
Keep receiver/date, actual versions, use and open physical/commercial questions.
Workflow comparison
| Mix-naming field | Actual reference | Cannot be inferred |
|---|---|---|
| Main product | Supplied sofa/variant and actual article | Similar upholstery is not product identity |
| Pillow/cushion | Actual item/position/role and material reference | No guessed inclusion, washability or compatibility |
| Image role | Source/catalog/generated/reviewed-final versions | Candidate label is not approval |
| Naming scope | Agreed actual identifiers, view and version | No relabeling, automatic matching or guessed latest pass |
| Archive process | Actual authorized destination and receiver requirements | No DAM import, tagging or access-control feature |
| Handoff | Versions, use, date, receipt and open questions | No physical bundle, sales or matching measurement |
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 a pillow in the image mean it is included with the sofa?
No. Actual item identity and commercial terms need separate confirmation; a scene or filename is not a packing list.
Can a file label establish a new material article?
No. Keep real supplier/article references and resolve unknowns rather than rename an old image into new physical evidence.
Does this add automatic tagging, archive import or separate cushion editing?
No. It is a manual naming/reference handoff, not a DAM, recognition or per-object fabric-control feature.
Does an archived filename prove receipt or approval?
No. Retain actual authorized confirmation, intended use and remaining physical/commercial holds.
Discuss the actual sofa and cushion reference scope
Bring minimal approved product/article/file identifiers without private orders or assumptions of separate editing and inclusion.
Discuss mix-naming scope