Most multilingual WooCommerce import problems come from a small set of causes: missing WPML relationships, unstable identifiers, category hierarchy errors, wrong language context, or variation data that is not tied back to the right parent product. 1. Products import but translations are not linked WPML needs translation rows for each language version. In Shirely, use … Read more
Import a translated WooCommerce category tree from one Matrix CSV using source and parent source IDs, then verify hierarchy in every language.
Keep WPML product and category translations in one Matrix source with stable identifiers, explicit language columns, repeatable imports, and QA.
Plan a full server migration separately from a Shirely catalog or store-data round trip, with backups, staging, IDs, URLs, WPML, and launch QA.
Google Sheets can give translators, product owners and reviewers one structured workspace for WooCommerce product translations. The sheet holds shared identifiers and language-specific text side by side; Shirely imports the approved version in a deliberate run or through a reviewed Automation slot. The sheet serves as … Read more
Convert a Shopify product export into a reviewed WooCommerce/WPML source by mapping identity, variations, categories, images, and translations.
WPML and Polylang use different WooCommerce translation workflows. Here is the practical compatibility boundary to know before using Shirely.
Plan the real cost of multilingual WooCommerce: software, translation, catalog maintenance, QA, market operations, and repeatable data workflows.
Build a reviewable multilingual WooCommerce catalog with stable product identity, WPML Matrix fields, local review, and controlled updates.
Maintain multilingual B2B products with stable keys, structured technical data, Matrix translations, controlled price updates, and reviewable imports.