Hi @geloai ,
Thanks for the detailed feedback, the three things you mention are related, so let me answer each one.
1. Emails always in English / following the customer’s language
There is no setting for that today, but let me explain the two layers involved.
The plugin itself is fully internationalized: every string, emails included, is translatable through the official WordPress.org translation system. The reason you currently see English is that, right now, only Spanish (100%) and Croatian (94%) have translations there. No other language has an approved translation yet, so WordPress falls back to the English source strings.
That part you can fix today: translations can be contributed at https://translate.wordpress.org/projects/wp-plugins/eu-withdrawal-compliance/. Once a language reaches 90% approved, WordPress.org automatically builds a language pack and delivers it to every site running that locale, no plugin update needed. If you prefer an immediate or in-house translation, a local one made with Loco Translate (or any .po editor) works too.
On top of that there is a second, multilingual-specific layer: the plugin’s own emails (the acknowledgement of receipt and the status-change notifications) are currently composed in a single language (the site’s default language) rather than in the language each customer selected while browsing with Polylang/WPML. Making those emails follow the customer’s language is now noted on the roadmap.
One thing that will already work in your favor: the withdrawal notice the plugin injects into WooCommerce’s own order emails will come out in the language of the order as soon as a translation exists, because WPML (WooCommerce Multilingual) and Polylang for WooCommerce switch the email language to the order’s language.
2. Printable form
Same first layer: all the strings of the Annex I.B model form are translatable, so once your language is translated, the collapsible model form shown under the withdrawal form will render in the language of the page the visitor is on.
The standalone printable view is a different case: it is anchored to the single withdrawal page configured in the plugin settings, so on a multilingual site it currently renders in the site’s main language only. Making the printable view (and the links pointing to the withdrawal page) language-aware with Polylang/WPML is on the roadmap as part of the same multilingual support package.
3. Emails and WooCommerce styling
That one is by design, for now: the plugin’s notifications are plain-text emails so they work on any site, with or without WooCommerce (the plugin can also run standalone). HTML emails using the WooCommerce template (same header, colors and footer as the rest of your store emails) are already planned on the roadmap. The notice injected inside WooCommerce’s own order emails already inherits the WooCommerce styling, since it is part of those emails.
Summing up: translating the plugin into your language(s) at translate.wordpress.org gives you the form, the page texts, the Annex I.B model form and the notice inside WooCommerce emails in the right language right away. Per-customer email language, a language-aware printable view and WooCommerce-styled emails are noted on the roadmap for future versions.
Thanks again for the report, multilingual setups are exactly the kind of real-world feedback that helps me shape the roadmap.
