Cross-border product image localisation

Cross-border teams usually need dozens or hundreds of product images per market — packaging, badges, and lifestyle shots with printed text. Treat localisation as a pipeline: prepare sources, pick a translation route, run a batch, review exceptions, and archive exports with the SKU record.

The step-by-step mechanics are covered in the batch product-image guide. This page focuses on decisions that are specific to multi-market ecommerce.

Privacy-sensitive or regulated catalogues should stay on the local engine. Optional DeepL or Google APIs send text to those providers. Optional cloud AI uploads images and deducts points per job.

Align the route with your market data policy before you fill the queue. See local vs cloud.

Group images by source language and destination market so OCR and target languages stay consistent. Mixing unrelated markets in one batch increases review cost. Where available, save outputs with a translated suffix, overwrite carefully, or write to a dedicated folder per locale.

Confirm supported languages and formats on the languages and formats page.

Automated translation is a draft. Open images with dense packaging, legal claims, or small badges in the editor. Adjust copy, fonts, colours, and placement so the storefront still looks intentional for that market. See edit translated images.

Export approved files as PNG, JPEG, or WebP. Keep projects and exports with the catalogue record so DAM or marketplace uploads stay traceable. Uploading into a storefront happens outside this app.

For a channel overview, open the cross-border ecommerce solution.

• Sources are grouped by source language and target market.
• Translation route matches the data policy for this set.
• OCR and target languages match the printed text and destination.
• High-risk packaging and claims were opened in the editor.
• Exports use PNG, JPEG, or WebP as required by the destination.