Translate WooCommerce emails
POM Translate provides a dedicated workspace for the configurable fields of emails registered by the active WooCommerce mailer.
Open the workspace
- Go to Translations → Other translations.
- Open WooCommerce emails.
- Choose the target locale.
- Select an Email template.
The selector lists WooCommerce core and extension email objects currently registered with the mailer. It preserves exact email IDs because third-party IDs can be case-sensitive. When two templates have the same title, Admin or Customer is added to distinguish their audience.
The workspace reports overall completion and completion for each template. A configured source field counts as complete only when the target field contains a saved translation.
Editable fields
Each template can expose:
- Subject;
- Heading;
- Additional content.
The Shared email footer is managed separately and is used by all supported WooCommerce emails. An empty translation intentionally falls back to the source field.
Required placeholders appear beside their source. Use the insert buttons rather than retyping tokens. Saving, previewing, and test sending reject missing or unexpected placeholders.
When POM AI is available, its per-field action fills an empty target field as an unsaved draft. Review the result and save the form to publish it.
Preview and test
Choose a recent order or enter an order ID, then generate an HTML or plain-text preview. The preview:
- uses current unsaved field values;
- shows the translated subject;
- replaces customer details with sample data;
- prepares order, account, note, refund, and supported extension contexts;
- does not call the email's delivery trigger.
Changing a field, template, order, or format marks the preview as stale. Regenerate it before approving the translation.
Send test email uses the same unsaved values and requires an explicit recipient. A successful preview or test does not save the form.
Runtime scope
Supported customer emails use the order locale when available. Gateway and PDF invoice or packing-slip templates are excluded by default and retain their own locale lifecycle.
Continue with email language context and email body strings.