How do I store translations in my spreadsheet?

Either way you already work. Keep a column per language beside the SKU, such as name_en, name_de and name_tr, or keep one row per product per locale with a locale column. The data transform reads both shapes.

What if a translation is missing for one product?

You choose the fallback. Most catalogs fall back to the English string so the page still sets and you can flag the gap on the page during drafting so it is easy to find before export.

Translated copy is longer. Will the layout break?

The preview paginates real print pages, so a longer paragraph reflows and pushes the page break exactly as it will on press. Product copy commonly runs up to a third longer than the source it was written from, so size the frame against your longest language once and every shorter one fits inside it.

Can it translate the copy for me?

The assistant can draft translations from your source column and write them back to the document and it can check the rendered pages afterwards. For copy that carries legal or technical weight, put a human reviewer in front of it. Most teams paste in translations they already own.

Do prices convert between currencies?

Formatting is automatic, conversion is not. The figure 1299 becomes 1.299,00 € or €1,299.00 from the locale. If a market has its own price rather than its own format, keep it in its own column and read that column for that edition.

Do you support right to left languages like Arabic and Hebrew?

Yes. Reading direction is a stylesheet rule, so the columns, margins, gutters and running headers mirror for those editions while the product data stays exactly where it is.

Do all the editions have the same page numbers?

They do when you want them to. Every edition runs the same product order and the same break rules, so page 118 is the same product everywhere. If a language needs extra pages you can let it flow instead.

What about languages that need a different font?

Fonts are set per edition in the stylesheet and embedded in the exported PDF, so Greek, Cyrillic, Turkish and CJK editions carry the glyphs they need and nothing falls back to a missing character box.

Can I export only the languages that changed?

Yes. Pick any subset of locales for a run. A single corrected price in the Spanish edition does not force you to re render the other eight.

Does each language count as a separate export?

Yes, one rendered PDF is one export against your plan. Drafting and previewing every edition costs nothing, so you only spend an export on the file you actually send to the printer.

Multilingual Catalog Generation and Automation

Automate multilingual product catalogs cattalog.ai produces a print ready PDF product catalog in every language you sell in, from one spreadsheet and one design. Keep a column per language beside the SKU, point the document at a locale and export the whole set as CMYK PDFs with the same page count and the same layout. Copy that runs longer once it is translated reflows against real print pagination. Prices, dates and measurements are formatted for the locale from a single cell. SKUs, range names, standards and trademarks are held out of translation. Right to left editions mirror the page and per locale fonts are embedded in the exported file. Back to the cattalog.ai home page