A J2Commerce product and its SKU are linked to a single Joomla article. The native Joomla multilingual system requires creating a separate associated article for every language. Because each article is treated by J2Commerce as an independent product, a translated version receives its own product record, variants, price and inventory quantity. Instead of remaining a translation of the original product, it effectively becomes a separate product in the database.
For stores selling unique or limited-stock products, maintaining separate inventory for every language version is, frankly speaking, a very poor and unsafe solution. A customer could purchase the English version while the Polish version remains available because both products have separate stock records.
The only sensible architecture appears to be using Falang, which translates the content of the existing Joomla article while preserving one article, one J2Commerce product, one SKU and one shared inventory record.
I would therefore like to suggest extending RO CSVI support for J2Commerce by adding integration with Falang. Ideally, J2Commerce product exports and imports could include Falang translations for article fields such as:
- title and alias;
- introtext and fulltext;
- meta title and meta description;
- other translatable Joomla article fields.
This would make RO CSVI a complete migration and catalogue management solution for multilingual J2Commerce stores without duplicating products and creating potentially dangerous inventory inconsistencies.
