Skip to content

Optional analytics, session recording and advertising stay off unless you accept. You can reject them and use Transglot. Change your choice anytime in Cookie preferences. Cookie Policy

All integrations
spec sheet · cms & commerce

WooCommerce and Transglot, give your products a local voice.

Choose WooCommerce in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.

Import and publish translations
Direction
Import and publish translations
Plan
Starter and up
Scope
products and categories: name, description and short description
Authentication
your store URL and a REST API consumer key and secret
Get started
Connect from your project’s CMS settings.

WC

cms & commerce
the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

  1. Connect WooCommerce

    Choose WooCommerce in the project’s CMS settings. Add your store URL and a REST API consumer key and secret.

    connect
  2. Choose the content and locale mapping

    Select the types and fields you want to localize. The connector reads products and categories: name, description and short description. Map the source and target locales to your project.

    map
  3. Sync and review the translations

    Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.

    review
  4. Publish to WooCommerce

    Use Publish to CMS to send the translated values to the mapped target locales. Check the publish result in the project’s CMS settings.

    deliver
Publish translated values back to the target locales you map in WooCommerce.
what moves

What you can translate and deliver.

Products and categories over the WooCommerce REST API. WooCommerce core has no per locale storage, so reviewed locales are written into one connector owned meta key on the product rather than over your authored copy. Your storefront reads that bundle.
What you can translate and deliver.
SurfaceWhat to expect
Source and scope

products and categories: name, description and short description

Translated output

Publish translated values back to the target locales you map in WooCommerce.

Keep in mind

Only the content types and fields you select are synced. Source content stays in its source locale.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

your store URL and a REST API consumer key and secret.

  • A Transglot project with its source and target locales configured.
  • Save credentials in the connection settings so your team can work without copying secrets between files.
  • Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.
  1. Create a Transglot project with the source and target locales you need.

  2. Open the project’s CMS settings and choose WooCommerce.

  3. Provide your store URL and a REST API consumer key and secret.

  4. Save the connection, select the supported content, map locales, then run Sync from CMS.

same project, more possibilities

Connect the rest of your workflow.

Your translations stay in one project as they move between tools.

works with what you already run

41 connectors, already built.

bring your workflow

Your content, ready for every locale.

Connect your tools, translate with your team, and publish reviewed content.