How do I bulk translate product listings?
Bulk translate product listings by exporting titles and descriptions with a stable product key, translating in batches with a glossary (brand names never translated), spot-checking bestsellers, then importing to each marketplace. CrossKit Batch Translate is for many records; Listing Translator is for a full listing; Smart Translator keeps formatting; CSV Formatter cleans the file first.
Speed without a glossary creates a catalog that looks machine-made—and shoppers discount it.
Steps
-
Export with a join key
SKU or handle in the first column, never translated.
-
Write a 20-line glossary
Brand, materials, “pack of”, model names.
-
Translate titles first
They are the highest-risk field. Then descriptions.
-
Sample 10 SKUs in-market
Search those titles on the target store. If nobody searches that phrasing, rewrite.
-
Import and run a listing check on the top SKUs
Then move on. Perfect is the enemy of 500 live SKUs.
-
Build the do-not-translate list before the first batch
Brand, SKU codes, material codes, connector names. One missed line becomes a thousand wrong titles.
Key, glossary, titles first, then bodies
Export with a join key (SKU or handle) that is never translated. Write a short glossary: brand, materials, “pack of”, model names. Translate titles first—they are the highest-risk field—then descriptions. Sample about ten SKUs in-market: if nobody searches that phrasing, rewrite. Import and listing-check top SKUs; perfect is the enemy of 500 live products. CrossKit Batch Translate is row-oriented; Listing Translator is for a full listing; Smart Translator keeps line breaks and bullets; CSV Formatter cleans the file first. The process is the same on Amazon, Shopify and TikTok Shop; field names and keywords differ per channel.
Safety rails at catalog scale
Do not translate image filenames used as URLs unless you also rename files. Do not run one model pass on cosmetics, kids or electrical without a reviewer. Speed without a glossary creates a machine-made catalog shoppers discount. After the first market, reuse the glossary so the brand sounds like one voice. Spot-check option names and infographic text left in images.
How CrossKit fits this job
Batch Translate for rows, Listing Translator for a full listing, Smart Translator for formatted bullets, CSV Formatter before any of that. Lock a glossary so brand names never translate. Spot-check bestsellers in the target market before you import the rest of the catalog.
Example
80 kitchen SKUs EN→ES. Glossary: brand “Acme”, “stainless steel” → “acero inoxidable”, never translate “SKU-1044”. Batch Translate titles, fix gender on “botella/bote”, then bodies. Handles stay English slugs.
Common mistakes
-
Translating image filenames that are used as URLs
Links break. Translate alt text, not the file path, unless you also rename files.
-
One language model pass with no reviewer on regulated categories
Cosmetics, kids, electrical. Get a human.
-
Translating handles so each language gets a new URL key
Merges fail and links break. Keep the key stable; translate titles and bodies only.
Recommended tool
Batch Translate
CrossKit Batch Translate translates multiple product records. Use Listing Translator for richer single listings.
Frequently Asked Questions
Will formatting survive?
Smart Translator is the tool aimed at keeping line breaks and bullets. Batch Translate is row-oriented.
Amazon vs Shopify vs TikTok Shop?
The process is the same; field names differ. Localize keywords per channel.
Will HTML formatting survive batch translation?
Not always. Smart Translator is aimed at keeping bullets and breaks. For HTML bodies, translate visible text and keep tags intact, or use a listing-level tool on bestsellers.
How do I update translations when English changes?
Re-export the delta for changed SKUs. Do not retranslate the whole catalog and overwrite good local keywords you already researched.