3 min read
Categories Guides

Multilingual WooCommerce Launch Checklist

A successful import proves that data was written. A launch needs broader evidence: visitors can find the right language, products behave correctly, checkout completes, and the business owners have approved what the store says and sells.

Use a representative sample in every language, then record who signed off each area. Do not leave all QA for the final hour.

Catalog identity and structure

  • Products have stable, unique SKUs or the documented Matrix ID / External ID used by the workflow.
  • No cross-store process depends blindly on local WordPress post or term IDs.
  • Variable products have correct parent and variation SKUs.
  • Translated categories use a verified source hierarchy.
  • Prices, stock, tax classes, dimensions, and identifiers match the approved source.
  • Images load, keep the intended order, and use appropriate alternative text.

Re-import the staging sample. It should update the intended records rather than create a duplicate catalog.

WPML and WCML

  • WPML is active before Matrix Mode imports.
  • Source suffixes match the configured language codes.
  • Each product's language switcher opens the corresponding translation.
  • Translated category archives show the correct products.
  • Shared fields behave consistently across translations.
  • Global attribute behavior matches the site's WCML configuration.
  • If Shirely's Translate global attributes (WCML Matrix opt-in) is used, the taxonomy was already configured as translatable and the selectors were tested.

Check a simple product, a variable product, a parent and child category, and any long translated labels on mobile.

Content and product claims

  • Titles and descriptions are complete in every launch language.
  • Technical terms are consistent.
  • Product claims, units, warnings, and compatibility statements have an accountable reviewer.
  • No placeholder copy, frontmatter, internal notes, or source comments are visible.
  • Downloads and diagrams are suitable for the relevant market.

An import tool moves content; it does not approve its meaning.

SEO and discoverability

  • Every indexable page returns the expected HTTP status.
  • Canonicals point to the intended public URL.
  • Robots directives match the launch decision.
  • Language relationships and switcher URLs are correct.
  • SEO titles and descriptions render in the right language.
  • Internal links do not point to staging or draft-only URLs.
  • Sitemaps contain only the intended public pages.
  • Structured data is present and does not contain stale local values.

If Yoast or Rank Math fields are imported, compare both the stored fields and rendered HTML.

Pricing, tax, shipping, and checkout

  • Buyer-facing prices and currencies are correct in each supported configuration.
  • Tax display and calculation have qualified business review.
  • Shipping zones, methods, restrictions, and messages are tested.
  • Payment success, failure, cancellation, and refund paths are understood.
  • Guest and account checkout behave as intended.
  • Order emails use the right language and accurate commercial information.
  • Returns, support, privacy, and other required customer information are accessible.

Place real test orders using representative markets, devices, and payment modes.

Accessibility and browser QA

  • Navigation and language switching work with keyboard focus.
  • Pages have one clear H1 and a logical heading order.
  • Forms have readable labels and errors.
  • Tables and galleries do not overflow on a real mobile viewport.
  • Images retain their aspect ratio.
  • Buttons and links remain visible at zoom.
  • Long translations do not overlap menus or checkout controls.

Import, Automation, and rollback

  • A current database backup exists and its location is recorded.
  • The exact approved source file or Sheet is preserved.
  • Mapping and preview were checked.
  • Result counts and warnings are recorded.
  • Other writers touching the same products, terms, or WPML/WCML groups are paused.
  • A rollback owner and trigger are known.

For Shirely 1.3 Automation, test with Run now and inspect Run History. WP-Cron is traffic-driven and does not guarantee an exact start time; system cron with WP-CLI is more predictable for large or time-sensitive work.

Final go/no-go

The final decision should answer four questions:

  1. Is the catalog accurate?
  2. Can a customer complete the intended journey in every launch language?
  3. Have commercial, technical, and legal owners approved their areas?
  4. Can the team detect and reverse a bad release?

If any answer is unclear, hold the launch and fix the evidence gap. For the import-specific preparation, use the first-time Shirely setup and the full documentation.