How to translate your emails and send them to different customers

ShopMagic's companion plugin Translate WooCommerce Emails enables your store to send messages to your customers in every language. This possibility is managed through integrations with WordPress translation plugins.

All of the currently supported plugins are listed below:

  • WPML

ShopMagic translation plugins integration

Each plugin enabling multilingualism differs a little in its behavior. To bring some details of way, each integration works as described in this article.

ShopMagic integration with WPML

Note, that for seamless integration with WPML plugin you also require WooCommerce Multilingual with the String Translation and the Translation Management modules bundled with Multilingual CMS package in WPML.

You don't need any additional configurations for WPML to work with multiple languages of automations, yet you have to create separate automation for each language you want to send. i.e. sending emails to English users would be only possible from English automations.

For preserving your setup between languages during translation of your automations, don't use Add translation to X because this action doesn't transfer your data, leaving you to set up automation from scratch. Instead, use Duplicate checkbox in WPML metabox in automation editor, which will copy all the data to new post as it is. You will need to click Translate independently after that, ready to prepare your translations with ongoing setup.

Click Duplicate when translating your automation to different languages Translate independently to keep your automations separate

Persisting customers preferred language

Translate WooCommerce Emails enables your store to track your customers' language of preference with ease to send them localized content. You don't have to take any actions - the moment you activate the plugin, your website starts to collect users preferences.

Our extension picks a list of languages, which user communicates in day-to-day by getting browser's preferences. Thanks to that, your customer will always receive email in language that she/he speaks. If your site doesn't support user's preferred language, she/he will find a message in your site's default language in a mailbox.

What does it mean - you get users' browser preferences?

Each browser, while communicating with one's website, sends a bunch of helpful information, like the language you prefer. You can check your browser's settings to see what languages you have selected as preferred. From this list, our plugin tries to match the best language from user's preferences and your site translations, starting from the most preferred language (top of the list in browser's preference). We save that match into user's record for automations processing.

Browser's language settings

How to test messages in multiple languages?

This may seem tricky at first. As preference mechanism is based on browser's setting, you can't easily trigger automations' flow in different languages from WordPress area (though you can always rely on Send test message). Usually, it's a good behavior - you don't want your users to change languages back and forth, triggering various automations not localized to preferred language. Yet, when it comes to testing validity of your automations' setup, it may be troubling.

The easiest way of verifying your automations in different languages would be to temporarily change browser's preferred language. In Chrome, you can to that in Language settings tab, hidden behind Advanced settings; in Firefox, this setting is contained in General tab. After making that change, you need to visit your site again, to sort of confirm the change - preferred language is saved during your visit. That's an important detail, especially if you would like to test, i.e. delayed automation which is already queued, but not yet triggered - if you won't visit your store after making a change in browser, the last saved language will apply for the automation.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us