SKU-safe by construction
Identifiers are structure, not text. They survive the round trip so your variants still map to the right products.
Supported formats:.csv.xlsx.tsv
Translate product catalogs without breaking the import
Export from your store, choose the customer-facing fields, apply your product glossary, and get a file back that imports cleanly. SKUs, prices and stock levels are read for context and returned untouched.
Drop your CSV file here
Up to 10 MB, five files a day. Nothing to install, no account.
Built for catalogs, not for sentences
Titles, descriptions and SEO fields get rewritten for the market. SKUs, barcodes, prices, weights, dimensions and category IDs are read so the translation makes sense, then written back exactly as they arrived.
Terminology that holds across the range
Materials, finishes, sizing vocabulary and brand names keep one translation across every product and every future batch.
SEO fields in the same pass
Meta titles and descriptions are translated alongside the product copy, with their length budget respected.
Whole ranges at a time
Thousands of products and variants in one run, with progress you can watch, instead of a spreadsheet split by hand.
From store export to localized catalog in 3 steps
Thousands of products, one job, one glossary applied to all of them.
Upload your catalog export
CSV or Excel from Shopify, Magento, WooCommerce, PrestaShop or your PIM. Product feeds in XML work too.
Upload an export →product-catalog.csvwebsite-content.xlsxmobile-app.xliffcourse-subtitles.zip
Say what to translate and how
Titles and descriptions in your brand voice, material and care terms held to your glossary, SKUs and prices left alone. Written once, applied to every product.
Write your instructions →How to translate this file?
Translate into German and Spanish. Keep product names in English, use our glossary, and make the copy sound natural for e-commerce.
Glossary applied
Translation planReadyUpdated
LanguagesEN → DE, ES
Scope742 cells
Volume8,490 words
Existing translationsKeep unchanged
Start translation
Refine your instructions
Import the localized catalog
Same columns, same row order, same SKU mapping. Your store importer sees the file it expects.
Export result →fr-FR
de-DE
es-ES
ja-JP
website-content_localized.xlsx
Product catalog translation FAQ
Which store exports can AI Glot read?
CSV and Excel exports from Shopify, Magento, WooCommerce, PrestaShop, BigCommerce and most PIM tools, plus XML product feeds. If your platform can export it, AI Glot can usually read it.
Will my SKUs or prices be changed?
No. You decide what gets translated before anything runs, and the plan shows you which fields are being written and which are being left alone. Identifiers and numeric fields stay untouched.
How do I keep material and technical terms consistent?
Save them to a workspace glossary once. "Stainless steel" or "full-grain leather" is then held to the same translation in every product, every language and every batch you run afterwards.
Can I translate product variants and attributes?
Yes. Each row is handled independently, so variants are covered, and attribute names or values are translated when they sit in their own fields.
What about a catalog update that adds fifty products?
Tell AI Glot to keep existing translations and fill only what is empty. The copy your team already reviewed stays exactly as approved.
How long does a large catalog take?
A file of several thousand products is processed in minutes, as one job, rather than days of copy-pasting.
Why not paste the catalog into a general AI assistant?
A catalog export is a contract with your importer. General assistants drop rows, shift columns and misalign SKUs on long files, and the failure is silent until the import errors. AI Glot works on the file as a structure and validates it before returning it.