How to translate a WooCommerce product CSV without breaking imports

A WooCommerce product CSV is not just text. It is the database map of your store.

That is why WooCommerce translation can go wrong quickly. Your export contains product names and descriptions, but it also contains SKUs, IDs, stock status, image URLs, parent products, categories, prices, tax settings, and plugin metadata.

If you send the whole file through a generic translation tool, you risk damaging the fields WooCommerce needs to re-import the catalog.

The safer path is to translate the customer-facing content columns and leave the operational columns untouched, the same structure-safe logic behind product catalog translation.

Step 1: Export your WooCommerce products

In WordPress, go to Products > All Products and click Export.

For most localization projects, export all columns the first time. This gives you a complete view of the structure and helps you identify plugin-specific fields, including SEO metadata from tools like Yoast or Rank Math.

Download the CSV and keep a backup of the original file before making any changes.

That backup matters. If an import mapping goes wrong, you want the original source of truth close by.

Step 2: Identify the fields that should be translated

Start with the columns customers actually read.

Good candidates for translation:

1. Name
2. Description
3. Short description
4. Categories, only if your localized store uses translated category names
5. SEO title fields from your SEO plugin
6. SEO meta description fields from your SEO plugin
7. Attribute labels or values, only when they are language-specific

Be careful with product attributes. A color like “Black” may need translation, but a size code like “XL” probably should not.

Step 3: Protect the fields WooCommerce needs

Some fields should usually stay exactly as they are.

Do not translate:

1. ID
2. SKU
3. Type
4. Published
5. Regular price
6. Sale price
7. Stock
8. Images
9. Download URL
10. Parent
11. Internal slugs or handles, unless you have a deliberate SEO slug strategy

These fields are the import machinery. If they change, WooCommerce may create duplicates, lose variants, detach images, or update the wrong product.

Put the two lists together and a correctly translated product row is mostly unchanged, which is the point.

Step 4: Translate the right columns with AI Glot

Upload the WooCommerce CSV to AI Glot and describe the job in one sentence. If you are new to this workflow, the general CSV translation guide explains how AI Glot reads columns and headers.

Name only the content fields to translate. Ask AI Glot to leave the operational fields alone.

For example, tell it: “translate Name, Description, and Short description. Leave ID, SKU, Images, and Regular price unchanged.”

AI Glot then shows you a plan before it runs, listing the columns it read as translatable, the languages, the word count, and the cost. Check the plan, then approve it.

This lets AI Glot focus on the language work while preserving the import structure WooCommerce expects.

There is no WooCommerce mode to find. A product export is an ordinary CSV here, so the whole round trip is six steps, and only one of them costs anything.

Everything before the approval step is free, including correcting a plan that read your file the wrong way. So there is no reason to guess at your column names.

Step 5: Add glossary rules for product language

WooCommerce catalogs often repeat the same brand, material, feature, and sizing terms across hundreds of products. A small translation glossary keeps those repeated terms stable from row to row.

Add glossary rules before translating:

1. Brand names that should stay unchanged.
2. Product line names.
3. Materials like “vegan leather”, “stainless steel”, or “organic cotton”.
4. Warranty terms.
5. Feature names that should use approved translations.

This helps the translated catalog feel consistent instead of stitched together row by row.

Step 6: Re-import and update existing products

When the translated CSV is ready, go back to Products > All Products > Import.

Upload the translated CSV and choose the option to update existing products. Match records by ID or SKU, depending on how your store is organized.

That match is the whole reason the protected columns matter. WooCommerce looks up an existing product by one identifier, then overwrites the rest of the row with what you uploaded.

During the mapping step, confirm that translated fields are mapped to the correct WooCommerce fields. Do not rush this screen. It is the last checkpoint before the database changes.

After import, review a small sample:

1. A simple product.
2. A variable product.
3. A product with HTML in the description.
4. A product with SEO metadata.
5. A product with images.

If those look clean, the full catalog is usually in good shape.

The safest WooCommerce translation pattern

WooCommerce localization works best when you treat the CSV like a product database, not a translation document.

Translate the visible product content, preserve the operational fields, and use a glossary to keep product language consistent across the catalog.

Ready to localize your WooCommerce export? Try AI Glot and translate your product CSV with a plain-English instruction, glossary control, and a clean re-import workflow.