MultilingualPress turns a WordPress Multisite network into a multilingual store. Each language runs as its own WordPress site with its own WooCommerce installation, and MultilingualPress connects the equivalent products, categories, and pages across those sites.
Because every language is a real WordPress site, each store keeps its own currency, tax rules, shipping, and prices. Your content stays ordinary WordPress content: deactivate MultilingualPress and every store keeps working on its own.
Full documentation lives at docs.multilingualpress.org. This page covers what you need to get a store running and links to the rest.
Before you install: MultilingualPress requires WordPress Multisite
↑ Back to topMultilingualPress does not work on a standard single-site WordPress installation. It needs a WordPress Multisite network, because the model is one language per site.
If your store is a single WordPress site today, converting it to Multisite is a planned migration, not a setting you switch on. Read Can I use MultilingualPress on a single site? and Migrate to Multisite before you buy.
Requirements
↑ Back to topMultilingualPress runs on current WordPress, PHP, and WooCommerce versions, and must be network-activated. For the exact minimums, see the compatibility matrix.
Installation
↑ Back to top- Download the extension from your WooCommerce.com account, or install it through Plugins → Add New → Upload Plugin.
- Go to Network Admin → Plugins and choose Network Activate.
MultilingualPress must be network-activated. Activating it on a single site in the network is not enough.
Extensions bought on WooCommerce.com are entitled through your WooCommerce.com account. Connect that account to your store and updates are handled for you, with no license key to enter. See Installation and activation.
Quick start for a WooCommerce store
↑ Back to topThis gets you from a working single-language store to a second language with a translated product.
- Set up the network. Convert your installation to Multisite and confirm your existing store is the main site. See Set up a WordPress Multisite network.
- Network-activate MultilingualPress, then open Network Admin → MultilingualPress to review the settings.
- Turn on the WooCommerce module. On the Features tab, enable WooCommerce. It is available whenever WooCommerce is installed. See Enable WooCommerce support.
- Enable the product post type and its taxonomies under Translatable Post Types and Translatable Taxonomies, so products, categories, and tags can be connected.
- Create your second language store. Go to Network Admin → Sites → Add New, set the language, and under Based on site choose your existing store. Select Copy Attachments and Connect content to bring media and relationships across. See Create a language version of your site.
- Configure the new store. WooCommerce settings are per site, so set the currency, tax rules, shipping zones, and payment methods for that market.
- Translate a product. Edit a product on your main store, open the MultilingualPress panel, pick the target store, and either connect an existing product or create one. Enter the price and SKU for that market. See Translate WooCommerce products.
- Add a language switcher so customers can move between stores. See Add a language switcher.
What MultilingualPress does not do
↑ Back to topWorth knowing before you plan a build:
- It does not convert prices. Each store holds its own prices, in its own currency. That is deliberate: rounded local pricing protects your margin. Use a currency conversion extension if you want rates applied automatically.
- It does not share the cart or checkout. Each language store is a separate WooCommerce installation with its own cart, orders, and customers.
- It does not share stock by default. Each store counts its own inventory. Central Stock for WooCommerce adds one shared stock value across the network.
- It does not translate by itself. You translate manually, or connect a machine translation provider you hold an account with. See How AutoTranslate works.
- It does not translate theme or extension interface text. That comes from WordPress language packs on each site.
Documentation
↑ Back to top| Topic | Link |
|---|---|
| Start here | Overview |
| Quick start | Quick start |
| Running a multilingual store | Manage a multilingual WooCommerce store |
| Products and variations | Translate WooCommerce products |
| Product attributes | Connect and translate WooCommerce attributes |
| Multi-market strategy | Multi-market eCommerce |
| Compatibility | Compatibility matrix |
| Developers | API overview and WP-CLI commands |
| All questions | Common questions |
Support
↑ Back to topYour license includes premium support in English, Monday to Friday during CET business hours.
- From WooCommerce.com: open a support request from your account. This route is available to customers who bought MultilingualPress on WooCommerce.com.
- From us directly: contact MultilingualPress support. Include the email address on your WooCommerce.com account so we can confirm your license.
Frequently asked questions
↑ Back to topDo I really need WordPress Multisite? Yes. Each language is its own site in the network. There is no single-site mode.
Can one license cover several stores? A license covers one website, one WordPress installation, however many language sites it contains. A second live website needs its own license. Staging and development copies are free. See Which license is right for me?.
Does my main language count against the language limit? Yes. English plus German is two languages.
Are product variations and attributes translatable? Yes. When you connect a variable product you choose whether to copy attributes and variations from the source, and global attributes are connected per store. See Translate WooCommerce products.
Is the extension the same as the one sold on multilingualpress.org? Yes, it is the same plugin, with the same prices and the same support team.
Will my content survive if I stop using MultilingualPress? Yes. Translations are stored as ordinary WordPress posts on each site. Deactivating the plugin removes the connections between them, and every store keeps its own content and keeps working.