Your team commissions localized product images from a studio in China. The retailer’s page looks correct at handover. Later, supplier creative appears again. Ordering another set of exports may repeat the problem: the missing decision is who can still write to the product information after delivery.
For brands and retailers using Shopify Collective, ONCE recommends agreeing on field responsibility before scaling creative production. Identify the data that stays connected to the supplier, the adaptations maintained locally and the person who checks the storefront after an update.
An editable field is not necessarily a permanent local override
Shopify Help Center’s Product policies in the Shopify Collective app says retailers can select additional details for continuous supplier sync, including titles, descriptions and media; inventory is always synced. It also warns that updating policy settings applies updates to products and can overwrite modified information with supplier information. We checked the undated page on November 9, 2026.
This does not mean all media continuously syncs by default. Inspect the actual retailer policy, supplier coverage and selected fields. Nor does it describe every Shopify store, third-party connector or merchant’s eligibility. It is a current documented workflow, not a newly announced feature.
The procurement implication is specific: if the same media field can receive supplier information again, a successful launch screenshot does not establish that localized creative has an ongoing maintenance arrangement.
ONCE’s field-responsibility brief
Imagine a homeware retailer importing a supplier’s product and commissioning local-language explanatory images. This is a hypothetical planning example, not an ONCE case study. The supplier owns the product knowledge, the retailer selects its presentation and the studio delivers the files. Without a shared explanation of the update process, all three may consider the job finished.
| Record | Question | Procurement consequence |
|---|---|---|
| Product and field | Which product, media or description field, and which storefront location? | Delivered file count is not maintained page count. |
| Source and writing process | Does the value come from the supplier, a local edit or another confirmed process? What can write again? | Verify settings rather than infer behaviour from filenames. |
| Permitted local adaptation | Translation and layout, a local use explanation, or changed product facts? Who approves? | Separate presentation work from factual revalidation. |
| Maintenance and review | Who receives changes, compares versions, handles overwrites and inspects the page? | Quote initial production and continuing service separately. |
Mark unknowns as unresolved. A shared document is enough; do not describe an unverified connection as an automated system. The authorized store owner should confirm policy settings. A studio should not alter business or inventory settings merely to preserve an image.
Even one supplier’s catalogue may contain different creative requirements. Have the implementation owner explain how existing policies cover those products before proposing a configuration change. Do not assume arbitrary per-image sync controls or promise that one generic app fits every store.
Preserve local expression without freezing old product facts
“Stop syncing” is not a complete solution. Supplier updates can carry information the retailer needs, while locally maintained material can become outdated. Establish whether a change concerns presentation style or actual packaging, included parts, specifications or use conditions.
For a language or layout difference, assess how to maintain an approved local adaptation through a confirmed process. If the product itself has changed, restoring an old localized image is not necessarily correct. Confirm the new facts first, then decide whether to amend text, replace a photograph or commission pickup shots.
Deliver clean product photography, editable text and layouts, the corresponding factual version and approval records where agreed. These make the next change easier to locate. They do not guarantee that reshooting will be unnecessary; an altered physical product may make the old base image unsuitable.
Also separate localization display from update ownership. A language-specific image can appear in the right place and still be vulnerable to a later writing process. The question “Which file does this page display?” differs from “Who can change the source later?” Both need an owner.
Use a controlled update review before expanding the order
Within a test scope approved by the store owner, choose a representative product and record supplier information, the actual policy, local files and the storefront state. Have the implementation partner define the intended change and the products and fields it could affect. Do not change a broad catalogue policy merely to test one image.
If the review includes a supplier update or policy adjustment, agree in advance on responsibility, scope, observation and recovery. After the relevant update has completed, compare the admin information, linked files and actual page. Keep untested situations explicitly open. No store was tested for this article, and we do not prescribe an unverified refresh deadline.
Divide acceptance into three responsibilities: the studio supplies approved, maintainable creative; the implementation partner explains and verifies the writing process; the brand or retailer approves the resulting page after the update. A correct file overwritten later calls for investigation of that process. A file invalidated by new product facts calls for a content change. Those are different reasons for additional work.
Compare quotes across initial production, information review, sync-related configuration, post-update checks and subsequent adaptation. Estimate actual products, fields and change effort. “Images per month” cannot describe every maintenance responsibility, and this method makes no claim about typical savings.
For an overseas brand coordinating Chinese production and retail partners, the practical next step is a short brief naming the product fields, approved local changes and next update owner. Our video marketing articles address related planning; this review specifically concerns who can replace information after the creative has been delivered.
For ONCE’s progression toward managed content, the durable asset is the relationship between product facts, approved adaptations and observed update results. It helps the next operator understand what changed and helps the client decide whether to buy redesign, a limited adaptation or better information management. The brief and review method are ONCE’s proposals, not tested client outcomes. The cover is an original conceptual image.
