Heads-up: FluentCart translations may need a native-speaker review across all languages
While testing FluentCart in Spanish, I noticed terminology that is not only unnatural but potentially misleading in an ecommerce and tax context.
Also, incomplete for many strings.
For example, the checkout tax breakdown translates “Tax” or “Tax rate” as “Tasa.” In Spanish:
- Tax should normally be “Impuesto.”
- Tax rate should be “Tipo impositivo.”
- Tasa has a different legal and fiscal meaning and may also be understood as a fee.
This makes me wonder whether similar issues may exist in other translations..., particularly if they have been translated literally or without review by native speakers familiar with ecommerce terminology.
This is especially important in:
- Checkouts and tax breakdowns
- Receipts and invoices
- Payment and refund statuses
- Customer account areas
- Legal and VAT-related fields
I think FluentCart would benefit from a review of every localization by native speakers, ideally using a shared glossary for tax, invoicing and ecommerce terminology.
These may appear to be small wording issues, but unclear translations in financial documents and checkout flows can confuse both customers and store owners (and may create avoidable compliance concerns).
Hope this feedback helps.
Since a couple of months ago, "somebody" translates all Fluent plugins with AI 🤮
De vez en cuando I take time to "fix" some awful translated strings...
Jose Luis Duron That explains a lot 😂
There’s so much AI slop out there already… we definitely don’t need it in tax terminology and interpretations too 😩
Yeah, the Dutch translation from wp.org is absolute slop as well. It's so bad it really shouldn't be shipped and it makes FluentCart look bad. I've tried to do something about it but they wouldn't make me a translation editor so now I just roll my own translation privately.
F. C. That’s exactly the issue.
Shipping it like this, with such obvious quality problems, just doesn’t feel great. I was actually fine with the native English version (which was mostly correct in terms of terminology) and handling the translations myself - like with all the Fluent Plugins.
But since the change, it feels a bit messy, especially because there’s no clear way to override or properly manage the translations from the main plugin. Right now, you end up with a mix of translated strings and English wherever strings are missing. 😅
Jorge de los Reyes FC aren't responsible for the translations though. They come from wp.org and are community created. Or am I misunderstand what you mean?
F. C. Yes, I understand they come from the WordPress.org community.
My point isn’t really who originally translated each string, but that these translations are automatically delivered as part of the FluentCart experience (and are not reviewed, and have misleading and potentially problematic points).
If tax, invoicing or checkout terminology is inaccurate, I think it would still be worth FluentCart reviewing the official localizations with native speakers or providing a vetted glossary.
As other users also experienced, this affects the overall experience.
So yes, community-created , but the quality issue for FluentCart users remains the same 🙂↕️
Jorge de los Reyes I'm enrolled as a contributor on some Fluent projects BUT I can't do it now on FluentCart.
At least in Spanish some contributors are doing a VERY BAD work (awful use of AI).
You can contribute HERE too (link goes to Spanish from Spain version).
Jose Luis Duron Thanks for sharing! I’ll review the Spanish strings and submit corrections for the mistranslations and missing translations I find. Hopefully FluentCart can also help active native contributors become translation editors, so good corrections don’t remain pending.
Jose Luis Duron I’ve just submitted suggestions for six of the most problematic Spanish strings, especially around tax terminology. They’re awaiting review, and this is only a first pass; many stores may still need custom translations in the meantime. Thanks again for pointing me to the project!
i've noticed a distinct lack of readiness for FCPro for a spanish shop setup. At the moment I've reverted to first rinse of AI translations of 8 of the 35 email notifications templates (total of 24 default enabled of 35 listed) , but some are enabled and not even populated in english. Happy to share them and collaborate with other spanish speakers as they code views that combine text strings and variables in the same block.
