4 min read
Categories Guides

How to Choose a WooCommerce WPML Import Plugin

The best import tool is not the one with the longest feature list. It is the one that can take your real catalog, match the right records, preserve multilingual relationships, and give an operator enough evidence to trust the result.

Start with a representative data sample, not a sales page. Include the awkward parts: a variable product, translated categories, an image, an SEO field, a missing translation, and a record that already exists on the destination.

Test identity before translated copy

An importer needs to know whether a row creates a product or updates one. For a standard cross-store WooCommerce workflow, SKU is the most useful stable key. WordPress post IDs should be treated as local to the source store.

In a multilingual Matrix workflow, Matrix ID / External ID can provide stable source identity across language versions. Ask the tool to process the same small file twice. The second run should update the intended records rather than creating a second catalog.

Confirm how translations are represented

WPML needs separate content records connected in translation groups. A useful workflow should make both the language and the relationship visible.

Shirely Matrix Mode uses language-suffixed fields such as title|en and title|pl beside shared values such as SKU and price. That keeps corresponding translations in one row shape. It does not generate translations; the CSV or Sheet still needs the approved text.

If your team prefers one file per language, test exactly how records are linked and how a missing or reordered row is handled. Do not rely on row position unless the workflow explicitly guarantees it.

Include variable products in the test

A tool that handles simple products may still fail your actual catalog. Variable products require parent and variation relationships, stable SKUs, attributes, and careful update behavior.

Build a test parent with two variations. Confirm that the destination creates the right structure, preserves attributes, and updates the same variations on a repeat run. If the store uses WPML/WCML, check translated product pages and the language switcher as well.

Test categories as a hierarchy

Category names alone are not enough. A multilingual catalog needs parent-child relationships and translated term groups.

Look for source-oriented fields such as source_id and parent_source_id, then test a parent and child in more than one language. Destination term IDs will differ between sites, so an importer should not require you to copy local IDs from one environment into another.

Shirely 1.3 also has an explicit WCML Matrix opt-in for translating global attributes. The attribute taxonomy must already be configured as translatable in a supported WPML/WCML setup; the import tool should not silently change that site configuration.

Check Google Sheets boundaries

“Google Sheets support” can mean several different things. Ask:

  • Can a public published Sheet be imported without credentials?
  • How are private Sheets authenticated?
  • Does every export require a Service Account?
  • Is the workflow manual, scheduled, or real-time?
  • Can the operator see what happened after a run?

Shirely imports public published Sheets without credentials. Private imports and every export require a Google Service Account. Shirely 1.3 adds saved import and catalog/content export slots with Run now, Run History, and WP-Cron or WP-CLI execution. Each direction is a separate job; a cell edit does not immediately change WooCommerce.

Evaluate failure and concurrency behavior

Preview and result reporting matter as much as raw speed. Confirm that warnings are visible before and after the write, and that a test interruption has a documented recovery path.

For scheduled work, understand the lock boundary. A same-slot lock is not the same as globally serializing every import on the site. Jobs that can update the same products, terms, or WPML/WCML translation groups should run sequentially.

WP-Cron is traffic-driven and does not guarantee an exact start time. For large or time-sensitive tasks, system cron calling Shirely's WP-CLI command is more predictable.

Compare the complete operating cost

Include licensing, but also count:

  • the number of tools and add-ons in the path;
  • recurring file preparation;
  • translation and catalog review;
  • staging and rollback work;
  • debugging across tool boundaries;
  • onboarding another person to run the process.

Shirely's current plans cover 1, 5, or unlimited sites. The installed plugin continues to work after cancellation; renewal for updates and support is discounted by 30%, and the plans include a 14-day money-back guarantee. Check the current pricing page before purchasing.

A compact evaluation checklist

Before choosing, verify that your candidate workflow can:

  • match products by the keys you actually own;
  • preserve WPML translation relationships;
  • handle your variable-product shape;
  • rebuild translated category hierarchy;
  • expose warnings and results;
  • repeat an import without duplicating the sample;
  • support your real Google Sheets and automation needs without overstating them;
  • fit the number of sites and operators involved.

Run that proof on staging. The WPML import overview and Shirely documentation show the supported workflow in detail.