3 min read
Categories Guides

What Is WPML, and Do You Need It for WooCommerce?

WPML is a multilingual system for WordPress. In a WooCommerce store, it helps the site maintain language versions of products, categories, pages, and other content, then connect those versions so visitors and site tools know which records belong together.

You do not need WPML simply because you import WooCommerce products. You need it when the store itself must maintain WPML translations and you want Shirely to create or update those multilingual relationships.

A translated product is several connected records

The storefront makes translation look simple: switch language and see the same product in different words. Behind the interface, each language version has its own WordPress post ID and language code. WPML connects those records in a translation group, commonly identified by a trid.

This separation lets a translated title, description, slug, and SEO text differ by language while product operations can share values such as SKU, price, or stock according to the store's configuration.

An import therefore has two jobs: write the correct content and preserve the correct relationship. Creating four unrelated products with similar SKUs is not the same as creating one four-language WPML product set.

When Shirely needs WPML

WPML must be active when you use Shirely's Matrix Mode or WPML-specific multilingual features.

Matrix Mode uses language-suffixed columns:

sku,title|en,title|de,description|en,description|de,regular_price
DRILL-100,Power Drill,Bohrmaschine,18V drill,18V Bohrmaschine,149.99

Translated fields appear once per language. Shared operational fields appear once per row. Shirely uses the source structure and WPML-aware paths to create or update the language records and their relationships.

For translated categories, use stable source identifiers rather than copying local term IDs between stores. source_id and parent_source_id can describe the hierarchy in a portable way.

When you do not need WPML

Standard Shirely workflows do not require a multilingual plugin. You can work with non-translated products, posts, pages, categories, orders, customers, coupons, and reviews within their supported field contracts.

If a store has one language, or if the task is a normal single-language product update, Matrix columns add complexity without adding value. Use a standard CSV with a stable SKU and only the fields you intend to change.

WPML is also not an automatic translation service inside the Shirely import. Your CSV or Google Sheet must contain the translated copy you want to publish. WPML supplies the multilingual structure; your source supplies the words and business data.

What is translated and what is shared?

Common translated fields include titles, descriptions, excerpts, slugs, category names, and SEO text. SKU, prices, stock, and other operational identifiers are commonly shared, though the actual WPML/WCML settings on the store determine important details.

Global WooCommerce attributes need particular care. Shirely 1.3 keeps the shared attribute path as the default and offers an explicit Translate global attributes (WCML Matrix opt-in) for Product Matrix. The taxonomy must already be configured as translatable in the supported WPML/WCML stack; Shirely does not change that configuration for you.

Decide before building the source file

Before an import, answer:

  • Which languages are configured in WPML?
  • Which fields need different values per language?
  • Which values must remain shared?
  • What stable key identifies the product outside WordPress?
  • How will categories and attributes be represented?
  • Who approves translations before publication?

Then run a small staging sample. Check each translated product page, category archive, variation, attribute, and language-switcher destination. Re-import the sample to prove that it updates the same records.

WPML is one layer of the store

WPML structures multilingual content. It does not replace decisions about tax, currency, payments, shipping, legal text, or translation quality. WooCommerce and its extensions still govern those areas, and each market needs its own review.

For a concrete implementation, read the Shirely WPML import overview and the guide to importing products with WPML translations. The documentation contains the field and workflow details.