Correct a WooCommerce email language

POM Translate stores the order locale during supported checkout flows and restores it while WooCommerce builds managed transactional emails.

Check the order context

1. Open the affected order and identify the language used during checkout.
2. Compare a newly created order with an older or manually created order.
3. Confirm the checkout request carried the expected locale.
4. Check whether a third-party checkout, import, or API created the order without the normal locale-capture hooks.

An email generated from an order without a usable stored locale may fall back to the current or base context.

Check translated fields

Confirm the exact email ID and audience, then review its translated subject, heading, additional content, footer, and stable body strings. Extension emails can use different IDs even when their displayed titles are similar.

Preserve WooCommerce placeholders. Invalid or missing target values fall back rather than producing a broken message.

Reproduce delivery, not only preview

Test the actual trigger with a safe test order. Include queued follow-ups, refunds, notes, subscriptions, and both HTML and plain-text variants. Two consecutive messages for different locales must not leak context.

If only an extension email is wrong, confirm it uses standard WooCommerce email filters. Custom code that builds or sends content outside those hooks needs an explicit locale integration.