Batch translate vs one-by-one listing translation
Batch translation covers volume after a glossary exists; a one-by-one listing pass is safer for bestsellers, titles and regulated claims.
Volume vs risk
One-by-one (Listing Translator) keeps title, bullets and description together so you can fix a unit error before it multiplies. Batch Translator is row-oriented: hundreds of titles after Handle or SKU is locked. Batch without a glossary creates a machine-made catalog shoppers discount. This is a workflow comparison, not a ranking of unnamed agencies.
What must never ride along in a batch
Do not translate Handle, SKU, image URL, HTML tags or Liquid. Do not run cosmetics, kids or electrical catalogs without a reviewer. Titles first, then bodies. Sample about ten SKUs in-market: if nobody searches that phrasing, rewrite before you import the rest.
A fair sequence
Clean the CSV, freeze a glossary, translate bestsellers one-by-one, then batch the long tail. When English changes later, re-export the delta—do not overwrite local keywords you already researched. AI copy remains a draft for human review.
How CrossKit splits the job
Batch Translator for rows, Listing Translator for a full page. Neither publishes to a marketplace. CSV Formatter belongs before either tool if columns are messy. Speed is not a user-count claim; it is the number of rows you choose to review.
Related CrossKit tool
Batch Translator
Open this browser tool after you read the article.
Frequently Asked Questions
Will HTML survive batch translation?
Not always. For HTML bodies, translate visible text and keep tags intact, or use a listing-level pass on bestsellers.
Which should I use for 20 SKUs?
If they are heroes, one-by-one. If they are simple accessories with a glossary, batch and spot-check.
Does batch translate publish to Shopify?
No. It prepares text in the browser. You import or paste through your own listing workflow.