Keep order output in the purchase language

An order is never duplicated for translation. POM Translate stores the checkout locale on the original order and uses that context when customer-facing order text is rendered.

Purchase-language snapshot

Both classic and Store API checkout preserve the normalized active locale with the order. This snapshot takes precedence over the administrator's current locale when POM Translate renders managed customer email content.

Legacy orders without a stored purchase language use the supported fallback chain: customer locale when available, current POM locale, then the base language.

What can be localized

Under a resolved order locale, POM Translate can translate:

• product names in order items;
• variation and custom metadata display labels and values;
• managed email subjects, headings, additional content, and footer;
• supported HTML or plain-text email body fragments;
• links built while the email locale is active.

Order numbers, quantities, prices, totals, taxes, addresses, notes containing customer data, and payment details remain unchanged.

In the normal WordPress administration order screen, POM Translate avoids replacing item data merely because an administrator uses another language. Order-item translation is activated when a supported customer-facing email establishes its explicit email locale.

Verify an order

1. Place a test order in the target language.
2. Change the current administration language.
3. Translate the products and item metadata used by the order.
4. Complete the email fields for the purchase locale.
5. Generate an HTML preview for that order.
6. Generate a plain-text preview.
7. Send an explicit test email.
8. Confirm the message still follows the purchase language and that item names, metadata, totals labels, subject, heading, footer, and links are correct.

Do not rewrite historical commerce data

POM Translate renders current translations for the original product and term records. It does not create localized order items or mutate stored financial data.

If exact historical wording must remain immutable for legal reasons, preserve the generated transactional document or use an order-document system designed for snapshots. Translation rendering is not a replacement for accounting or compliance archives.