If you export to several countries, you probably have multiple catalog versions that no longer match each other. This article is about fixing that.

Why separate versions cause trouble

Suppose a price changes. Now you must edit the Persian, English and Arabic catalogs separately. In practice one gets forgotten, and you spend months quoting a wrong price to a foreign customer.

The right structure: one source, several outputs

Product data (code, price, image, specs) is entered once. Language is only a display layer over that data.

• A price change is done once and applies everywhere.
• Adding a market means one more output, not one more project.

What should be translated and what should not

Translated: product name, category, description, and the catalog's own labels.

Not translated: product code, the price number, units of measurement (20W, IP67, 3.16 inch), and brand names.

If a tool "translates" your product code, a foreign customer cannot place an order.

A note on writing systems

Arabic and Persian are right-to-left; Chinese and Japanese need their own fonts. A Chinese catalog built with a Latin font shows empty boxes instead of text.

How it works in practice

Enter the product list once and export one version per market with the multilingual catalog maker.