How can I make the product price on Woocommerce multilanguage translatable so I can set different prices in different languages? I know there's some custom coding that allows to do that, but I'm not sure where to start checking
More information: it's a very specific scenario where prices and stock status need to be modified across languages. We are not going into this wormhole for pleasure but for a good reason: depending on the language, the product is shipped from a hub/warehouse in one country or another, and this hub/warehouse has small variations in prices, product variations stock and stock status for some products. I've seen some support threads around that but not a solution that we can apply, or something that guides us a bit to start working a custom solution. So far, we have unlocked system custom fields and now custom fields like _price, _sale_price and so one appear on the "Custom Fields Translation" section at WPML > Settings. How can I guide our developer into achieving this?
I’d be happy to prepare a solution for your issue. The approach you described seemed correct, but since you mentioned that you’ve already tried to solve this and it’s “related to business logic,” I decided to create a sandbox with a ready-made solution - so we can both confirm that everything works as expected.
While preparing the sandbox (which I’ll share via private message in this thread), I encountered issues with setting different prices for product translations. I need to consult this behavior with the team.
I’ll keep you updated as soon as I have more information.
We discussed your idea of gathering different proposals, and in general, the concept can generate a lot of “edge cases” that could be problematic. We once had a client who tried to achieve this effect, and it was quite difficult to maintain - I’m not sure it wouldn’t be better to try to simplify it using the mechanisms available in WC itself.
The first thing that stands out is that changing the language could allow a customer to order something “cheaper” in another language/translation - this needs to be considered. Also, there are countries that share the same language but are geographically different.
Proposal 1:
Not supported out-of-the-box; modification would be needed - you could add different “Euro” currencies for each country, so each product for a given country could have an individual currency.
* You’d need a mechanism to “force the correct currency for that customer”
* You’d probably need to modify payment gateways to support these “Euro variants”
* Advantage: translations would not affect the price
Proposal 2:
Most of it should be ready. Each product is a “separate product” — then it’s easy to set its price and stock (independent).
* Disadvantages: if a product is added to the cart and the customer changes the language, there could be issues - you’d probably need to set WCML to clear the cart on language change.
Workflow:
Create a product, translate it, then “disconnect translations” so it becomes an “individual product” — everything can then be set individually.
If a “uniform translation” is needed, you can reconnect it (but some information may need to be reset because it will be overwritten).
