Recently, we removed Dutch and Deutsch but if they are already charged, which seems so, we would like to add them back free of charge. Please advise. Thank you.
Thanks for contacting us. Could you please clarify what you mean by this? When you mention that Dutch and German were “already charged,” are you referring to translation credits that were already consumed for those languages?
Also, to confirm my understanding, you previously removed the Dutch and German languages from your website and are now looking to add them back. Is that correct?
Thanks for your reply. Could you please share temporary access (WP Admin and FTP) to your website? I’d like to check whether the translated languages are still present. If the languages were not fully deleted, the existing translations should still be available, and simply re-adding the removed languages may restore them without any additional steps.
Please ensure you have a full backup of the site beforehand to avoid any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/
) to create the backup.
Any information you share will be treated confidentially and will only be visible to you and me.
I am writing to explain an issue we encountered while using WPML Automatic Translation credits on our website and to kindly request your assistance regarding credit adjustment and a possible refund.
We recently installed the WPML plugin on our website and translated the site into the following nine languages using paid automatic translation credits:
English
Español
Français
Italiano
Türkçe
Português
Русский
Deutsch
Dutch
Unfortunately, by mistake, we added and translated the Dutch language even though we do not need this language on our website. As a result, automatic translation credits were used unnecessarily for Dutch.
While removing the Dutch language from the website, the German (Deutsch) language was also accidentally removed, including all of its translations. This was not intentional.
When we tried to add the German (Deutsch) language again, we noticed that WPML would charge translation credits again, even though the German translations were already paid for previously and were removed only by mistake.
Our Requests:
Please restore or return the translation credits that were already used for the German (Deutsch) language so we are not charged again for re-adding it.
If possible, we kindly request a refund or credit adjustment for the translation credits that were used for the Dutch language, as we do not need Dutch on our website.
For your reference, I have also attached screenshots showing the issue and the credit usage.
We sincerely request your support in resolving this matter, as the removal of the German language was accidental, and we want to avoid being charged twice for the same translations.
Thank you very much for your time and assistance. I look forward to your response.
Thanks for your reply. I’ve checked your website and can see that the German language has been restored.
I also reviewed the Automatic Translation usage reports under WPML → Translation Dashboard → Translation Tools and generated a fresh report. Based on a comparison of the December 2025 and January 2026 reports, I don’t see any duplicate or double charges related to German translations.
Thank you for your reply and for checking the reports. I appreciate your support.
I understand that, according to the Automatic Translation usage reports for December 2025 and January 2026, there do not appear to be duplicate charges for German translations at this time. However, I would like to clarify my concern in more detail.
When we initially set up WPML, the German (Deutsch) language was added and translated along with the other languages, and translation credits were correctly used at that time.
Later, due to a mistake while removing the Dutch language (which we do not need), the German language was also accidentally removed, including all of its translations. This was not intentional.
After restoring the German language, I can now see based on the Pay-as-You-Go details and the attached screenshot that an amount of €42.42 is scheduled to be charged on 1st February 2026. This makes me concerned that we are being charged again for German translations that were already paid for previously, simply because the language was removed and re-added by mistake.
So my concern is not necessarily about past duplicate charges in the reports, but about a new upcoming charge for the same German content that had already been translated earlier.
Additionally, as discussed previously, I would like to kindly request a refund or credit adjustment for the Dutch language translations. Dutch was added and translated by mistake, we do not need this language going forward, and it has been removed from the website.
Summary of my requests:
Please confirm that the €42.42 Pay-as-You-Go charge will not be applied for German translations that were already paid for before.
If possible, please refund or restore the translation credits used for the Dutch language, as it was added unintentionally and is no longer required.
I have attached the relevant screenshots again for clarity.
Thank you very much for your time and understanding. I look forward to your confirmation.
Thank you for rechecking the data and for your detailed explanation. I appreciate your time and support.
Regarding your question:
I did not specifically or manually target the Elementor Pro strings or ElementsKit Mega Menu items for translation. On my website, Automatic Translation is enabled, so whenever I click to translate content or when WPML detects untranslated content, the system automatically uses the available credits to complete any pending or incomplete translations. This is how those credits were consumed, rather than through a deliberate, manual selection of specific strings or items.
Additionally, I would like to kindly follow up on my Dutch language concern, which I have mentioned in multiple previous messages. It seems this part has not yet been addressed.
As explained earlier:
The Dutch language was added and translated by mistake
We do not need Dutch on our website
Dutch has already been removed from the site
Automatic translation credits were used unnecessarily for Dutch
I would really appreciate your clarification on whether it is possible to refund or restore the credits used for the Dutch language translations, as this language is no longer required.
To summarize:
The credits were used automatically due to Automatic Translation being enabled, not by manually targeting specific Elementor or ElementsKit strings.
I am still awaiting guidance or confirmation regarding a refund or credit adjustment for the Dutch language translations.
Thank you again for your continued support. I look forward to your response and clarification on the Dutch language issue.
Thanks for your reply. I’ll investigate why automatic translation was initially triggered for Elementor or ElementsKit strings and why credits were used without your consent.
Thank you for the update and for investigating the automatic translation behavior. I appreciate your support and clarification regarding the Dutch language credits.
I would like to kindly follow up on my remaining concern regarding the German (Deutsch) language.
As discussed in previous messages, the German language was:
Initially added and translated along with the other languages (credits were used at that time)
Later accidentally removed, including all German translations
Then restored again, after which I noticed the €42.42 Pay-as-You-Go charge scheduled for 1st February 2026
My concern is whether this charge includes German (Deutsch) translations that were already paid for earlier, which could result in being charged twice for the same language content.
Could you please confirm:
Whether the upcoming €42.42 charge includes any German translations that were previously translated and paid for, or
If all German-related credits were fully consumed only once and are not being charged again due to the removal and re-addition of the language?
Your clarification on this point would be very helpful.
Thank you again for your continued support. I look forward to your response.
Thanks for your reply. To clarify, the €42.42 Pay-as-You-Go charge is related to the translation of Elementor and ElementsKit strings, not to any German (Deutsch) page translations. You are also not being charged again for the same translations due to the removal and re-addition of the language.
I’m still investigating why automatic translation was initially triggered for the Elementor or ElementsKit strings and why credits were used without your consent. I’ll get back to you as soon as possible.
Thanks for your reply. I’ve checked, and the ElementsKit strings are used for your navigation menu, and I’m not seeing any issues there.
However, I noticed that Elementor Pro and Formidable Forms backend strings are being automatically translated, as shown in the attached screenshot, and credits are being charged for this.
Please allow me to check this with our 2nd Tier Support. I’ll get back to you as quickly as possible.
Thanks for your reply. The report that I've escalated is still in a queue for review by our 2nd Tier Support. I will come back to you once I've feedback.
The topic ‘[Closed] Deutsch’ is closed to new replies.
