Consentik Wix: EU Withdrawal in your site's languages
1. Overview
EU Withdrawal gives your buyers a form to exercise their 14-day right of withdrawal from a purchase, and gives you a queue to process each request before the refund deadline.
What it used to do. The form shipped with a single version of its buyer-facing text. Whatever language your storefront was in, and whatever language the buyer was reading the page in, they saw the one version you had configured — in practice, English. A buyer on your German storefront read an English withdrawal declaration.
What it does now. Every word the buyer reads follows the languages you already configured under Translations — the same list your cookie banner and data request form use. Nothing new to buy, nothing new to turn on, and no new language settings to keep in sync.
This matters more here than on a banner. Under EU Directive 2023/2673 Article 11a, the withdrawal form is a legal declaration, and its wording has to read as a confirmation of withdrawal rather than a cancellation. A buyer who cannot read the declaration they are ticking is the exposure this change removes.
With this update you can:
- show the withdrawal form, its buttons, its placeholders and its error messages in the language of the page the buyer is on
- send the buyer's confirmation email in the language they submitted in
- edit every language yourself, string by string, on the Design and Email template tabs
- see, on each request, which language the buyer actually read
- keep the exact wording you had already written — editing it is never required
Consentik translates and displays your withdrawal content and records the requests your buyers submit. It does not verify orders, issue refunds, or decide whether a request is valid — those stay with you.
2. How it works
- A buyer on your site clicks your withdrawal link.
- The form opens in the language your cookie banner already resolved for that page view. If that language is not one you serve, it opens in your site's default language.
- The buyer fills in the form, ticks the confirmation checkbox and confirms — all of it in that language, including any validation errors.
- Consentik records the request with the language of the page, the language that was actually shown, and the exact confirmation wording the buyer ticked, saved word for word.
- The buyer gets their acknowledgement email in that same language. Your own notification email arrives in one language, as before.
- The request appears in your queue, where you process it exactly as you do today.
Your buyers are never asked to pick a language for the form. It follows the page they are already on.
3. Where languages come from
You do not configure languages for the withdrawal form. It uses the ones already set up in Translations, on the same plan and the same quota as your banner.
- Add a language there and the withdrawal form gets it.
- Remove it there and the withdrawal form stops serving it.
- If your site runs in one language, nothing about this update changes what you or your buyers see.
Each language you add starts from a ready-made translation, so a new language is usable the moment you add it. You can rewrite any of it.

4. Your existing wording is kept
This is the part worth reading twice.
When your languages are set up, the default language of your site starts from its ready-made translation, with every string you had edited laid over it. So:
- anything you wrote yourself stays exactly as you wrote it, character for character
- anything you never touched arrives translated instead of staying in English
Every other language starts from the ready-made translation alone.
You do not have to do anything for this. Sites that already had languages configured were set up when this update was released.
5. Editing a language
Open EU Withdrawal and go to the Design tab. A card called Edit language sits at the top.
- Pick a language. The editor fields and the live preview beside them both switch to it.
- Edit any field: the link text buyers click, the form title and body, the four field labels, the confirmation checkbox, the confirm button and the success screen.
- Save.
A few behaviours to expect:
- Your site's default language is marked Default in the list.
- With unsaved changes, the language picker is locked until you save or discard. This is deliberate — it stops you from losing an edit by switching away mid-sentence.
- With only one language configured, there is no picker. You are editing that language, and a line under the heading tells you so and links to Translations.

6. Settings that apply to every language
Colours, the form's position, the email address that gets notified and the deadline settings are not per-language. There is one set of them for your whole site.
While you are editing a language that is not your default, those fields stay visible but locked, with a note saying why. You can still see what they are set to; switch to your default language to change them.
7. The buyer's email
On the Email template tab, the same language picker governs the buyer's confirmation subject and message. Pick a language on Design, switch to Email template, and you are still in that language.
- Send test email sends the language you currently have selected, so you can check a German email by selecting German.
- The request ID and the submission date appear in every language — that is what makes the email a record the buyer can keep.
- Your own notification email is not translated. It is written to you, not to the buyer, so it stays in one language no matter which language the buyer used. The fields for it are marked in the editor.

8. Seeing which language a buyer read
Open any request from the list. Alongside the buyer's details you now see two things:
- Locale — the language of the page the buyer was on
- Language shown — the language the form was actually rendered in
When they match, the buyer read your site in a language you serve. When they differ, the buyer was on a page in a language you have not added, so they read your default language instead. The request detail says so and points you to Translations.
A run of requests where the two disagree is the clearest signal you have that a language is worth adding.
The confirmation wording stored on a request is the wording the buyer ticked at that moment. Editing that language later never changes it, so the record stays a record.

9. Adding and removing languages
What you do | What happens to the withdrawal content |
|---|---|
Add a language | It arrives ready-made and you can edit it |
Remove a language | Buyers on pages in that language see your default language instead |
Remove it, then add it back | Your edits in that language are gone and it starts from the ready-made translation again |
Remove and re-add your default language | Your own edited wording is laid back over the fresh translation |
Your plan loses multi-language, or you switch Translations off | Buyers immediately see your original single version again. Nothing you wrote is deleted |
Updated on: 09/11/2026
Thank you!