If you run an online store with WooCommerce, Lang Forge PRO extends its translation capabilities across the core shopping experience — product catalog, product metadata, categories, attributes, core store pages, cart language switching, checkout strings, and order-language tracking. Your customers can browse products, read descriptions, add items to their cart, and complete checkout in their preferred language when the store uses the supported WooCommerce core flow.
WooCommerce translation involves more than just translating product descriptions. There are product categories, attributes (like “Size” and “Color”), variation labels, store pages (Cart, Checkout, My Account), transactional emails, and dozens of interface strings that all need attention. Lang Forge covers the core WooCommerce pieces in this section; advanced WooCommerce extensions, custom checkout plugins, subscription/booking flows, payment-provider emails, shipping calculators, and heavily customized transactional email templates should be verified per store before launch.
What gets translated in a WooCommerce store
Product content:| Element | How it is translated |
|---|---|
| Product names and URL slugs | Through the standard post translation workflow or AI translation |
| Long and short descriptions | Through the post editor, Visual Editor, or AI translation |
| Product categories and tags | Through the taxonomy translation interface |
| Product attributes (“Color”, “Size”) and their values (“Red”, “Large”) | Through the attribute translation interface |
| Variation descriptions | Through the parent product translation |
| Product image alt text | Through the post editor or Visual Editor |
| Page | How to translate |
|---|---|
| Shop page | Create a translation of the Shop page like any other Page |
| Cart page | Create a translation — WooCommerce shortcodes adjust automatically |
| Checkout page | Create a translation — form labels come from string translation |
| My Account page | Create a translation — navigation labels come from string translation |
| Terms and Conditions | Create a translation linked to the original |
- “Add to Cart”, “Proceed to Checkout”, “Apply Coupon”, “Update Cart”
- Cart table headers, checkout form labels, account page navigation
- “Out of Stock”, “On Sale”, “Related Products”, “Description”, “Reviews”
- All translated through Lang Forge > String Translation
What stays synchronized across languages
Product data that should not change between languages is automatically kept in sync:
| Data type | Behavior |
|---|---|
| Price | Same in all languages (displayed in store currency) |
| SKU | Same in all languages |
| Stock quantity | Shared — if 10 units are in stock, that applies in every language |
| Weight and dimensions | Same in all languages |
| Sale status and dates | Synchronized — a sale in English is a sale in all languages |
| Product images | Shared by default (can be overridden with language-specific images) |
Step-by-step: Setting up WooCommerce translation from scratch
- Make sure both WooCommerce and Lang Forge PRO are installed and activated
- Go to Lang Forge > Settings and scroll down to Translatable Content. Verify that Products is checked. If it is not, check it and click Save Settings
- Start with your core WooCommerce store pages. Go to Pages > All Pages and find the Shop, Cart, Checkout, My Account, and Terms and Conditions pages
- For each store page, click Edit, then click Create Translation in the Language & Translations metabox for your target language. WooCommerce shortcodes in these pages are automatically adjusted to work in the correct language
- Translate the page content (for Cart and Checkout pages, the visible content is minimal — most text comes from WooCommerce strings which you will translate in step 8)
- Translate your product categories. Go to Products > Categories, click on each category, and provide the translated name, slug, and description for each language
- Translate your products. There are two approaches:
– In bulk: Go to Lang Forge > Translation Status and click “Duplicate + AI Translate” for your target language. This creates translated drafts of all products at once
- Translate WooCommerce interface strings. Go to Lang Forge > String Translation, filter by Source “WooCommerce”, and translate strings like “Add to Cart”, “Proceed to Checkout”, “Out of Stock”, “Reviews”, and all checkout form labels. Or use AI Translate All to process them in one batch
- Test the complete shopping flow. Browse the store in the translated language, add a product to the cart, proceed to checkout, and verify that every label, button, and message is in the correct language
- Publish all translated products and store pages when you are satisfied with the results
How the cart works when customers switch languages
One of the most common questions about multilingual WooCommerce is what happens to the shopping cart when a customer changes language mid-session. In the supported core WooCommerce flow, the cart is preserved:
- Items in the cart automatically update to show the translated product name and description
- The cart total, shipping costs, taxes, and discount calculations remain unchanged
- If a customer adds a product while browsing in English, then switches to Spanish, the same product appears in the cart with its Spanish name and description
- Coupon codes work in any language — they are not language-specific
Order language tracking
When a customer places an order, Lang Forge records which language they used during checkout. This affects:
- Order confirmation emails can use the customer’s checkout language when the email template uses WooCommerce/core translated strings; custom email builders and payment-provider emails need separate testing
- Order notes visible to the customer display in their language
- My Account order history shows order details in the language the customer used
- Admin order view shows the customer’s language so your support team knows which language to respond in
Real-world example: Translating a specialty food store
A gourmet food shop based in the US wants to sell to customers in Mexico and France. They have 120 products, 15 categories, and 8 product attributes (Weight, Origin, Ingredients, Allergens, etc.). The content manager sets up Spanish and French in Lang Forge, checks Products in Translatable Content, and translates the 5 core WooCommerce pages first. She then sets up the Glossary with terms like “organic” (organico / biologique), “free-range” (de corral / elevage en plein air), and keeps the brand name “Golden Harvest” as Do Not Translate. She runs Duplicate + AI Translate for both languages, which creates and translates all 120 products in about 45 minutes. She then reviews the product translations using the Frontend Visual Editor, translates WooCommerce strings, sets up translated menus, and publishes everything. The entire project takes about two days, compared to weeks with manual translation.
What happens on the Free plan
WooCommerce integration is not active on the Free plan. Product post types are not available for translation, and WooCommerce-specific strings are not collected in the String Translation page. Your store operates only in your default language.
Common mistakes to avoid
- Forgetting to translate product attribute values. Translating the attribute name “Color” to “Color” in Spanish is only half the work — you also need to translate values like “Red” to “Rojo”, “Blue” to “Azul”, etc.
- Not testing the checkout flow end to end. A mistranslated checkout field label or missing “Place Order” button translation can cause cart abandonment
- Translating prices or currency symbols. Prices are synchronized automatically. Do not add price translations manually — they will create conflicts
> Tip: Translate your highest-traffic products first. Check your WooCommerce analytics to identify your top 20 products by page views or sales, and prioritize translating those. You can translate the rest progressively.
> Good to know: If you use WooCommerce product variations, you only need to translate the parent product. Variation-specific content (like attribute labels “Small”, “Medium”, “Large”) is translated through the attribute translation system, not on each variation individually.
[Screenshot: A translated WooCommerce product page showing the product name, description, and “Add to Cart” button in Spanish, with the language switcher in the header]
—