Cross-factory source decision
Do not let one SKU erase the real factory and sample behind each base image
For a supplied dual-factory SKU, retain actual sample/frame/batch identifiers, base-image source ownership and documented cross-factory declarations. Review visible differences and the intended representation before deciding common, separate or held references. This manual decision does not recognize factories, measure tolerances, prove frame equivalence or authorize hiding real product differences behind a batch note.
By XinVise TeamPublished Updated


Built for this workflow
- Keep actual factory/sample and source ownership traceable
- Treat tolerance declarations as real scoped records, not invented image metrics
- Separate reference-use decisions from physical interchangeability
Identify the actual factory, sample batch and base source
Keep actual permitted factory/source identifiers, frame/sample batch references, product/variant and image versions. A shared SKU, similar silhouette or file label does not establish the same physical frame or which factory supplied a sample.
Do not infer factory origin from appearance. If ownership or batch mapping is unknown, keep the proposed shared reference held rather than assign a plausible factory.
Use the BOM reference precheck for actual product/component identity.
Record source-backed differences and actual declarations
Compare actual visible seam layout, upholstered curvature, corner profile, components and product features with their own factory references. Distinguish real known product differences from generated or retouched changes.
Keep any actual cross-factory visual-tolerance declaration, responsible authority and relevant method/scope. Do not invent a numeric allowance, measure manufacturing tolerance from pixels or treat a generic statement as physical equivalence.
Use the image-quality checklist before interpreting a candidate difference.
Choose common, separate or held references without masking truth
A common reference needs actual evidence and authorized scope that support accurate representation for its intended use. If factory differences matter or remain unresolved, retain factory-specific sources or hold the task instead of assuming one base fits both.
A batch note does not cure misleading product imagery. Do not retouch away actual differences and call the frames identical; physical interchangeability and technical/commercial approvals remain separate.
The evergreen-frame reconciliation owns seasonal continuity; this page owns simultaneous cross-factory source ownership and use.
Handoff factory-specific source decisions and limits
Retain factory/sample/batch/source/declaration versions, actual decision authority, intended use, reviewer/date and unresolved differences. A new factory, batch or source needs relevant re-review rather than inherit a common-base pass.
Public generation needs sign-in, credits and catalog scope. It adds no factory detection, automatic frame matching or equivalence certification. Use minimal approved identifiers without private supplier contents or credentials; no accuracy, tolerance or savings result is measured here.
Use the claim-to-evidence review before describing the common or factory-specific images.
Recommended process
- 01
Identify actual factory/source ownership
Keep sample/frame/batch and base-image versions without inferring origin from a SKU or silhouette.
- 02
Record real differences and scoped declarations
Retain actual seam/curvature observations and authorized records without inventing tolerance metrics.
- 03
Decide supported reference use
Use common sources only within actual accurate scope, otherwise separate or hold; notes do not cure misrepresentation.
- 04
Deliver source-specific status
Keep versions, authority, reviewer/date and unresolved physical/commercial questions.
Workflow comparison
| Dual-factory field | Actual evidence | Cannot be inferred |
|---|---|---|
| Factory/sample batch | Actual permitted identifiers and product/frame references | Same SKU does not identify origin or identical frames |
| Base-source ownership | Real factory/sample and source-image version mapping | No guessed ownership from appearance |
| Visible differences | Actual seam, curvature, corner and component references | Generated changes are not measured factory differences |
| Tolerance declaration | Actual authority, record/version and method/scope | No numeric allowance or physical equivalence from pixels |
| Share/split/hold | Evidence-backed accurate use and actual authorized decision | A note cannot conceal misleading product differences |
| Handoff | Factory/batch/source/decision versions, use, date and holds | No detector, matching accuracy or interchangeability approval |
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 SKU mean both factories made an identical frame?
No. Confirm actual sample/frame/batch and source ownership records, retaining unresolved differences.
Can image comparison create a cross-factory tolerance?
No. Use actual authorized declarations and relevant technical evidence; this guide supplies no manufacturing measurement or allowance.
Can a batch note justify a misleading common image?
No. Preserve accurate product representation; use separate sources or hold unresolved scope rather than hide differences.
Does this identify factories or approve physical interchangeability?
No. It is manual source-use review, not detection, automatic matching or technical/commercial equivalence approval.
Discuss actual factory and base-source references
Bring minimal approved sample/batch/source identifiers and real declarations, not private supplier contents or assumptions of frame equivalence.
Discuss dual-factory scope