A bilingual catalogue needs more than translated navigation. Product identifiers, review comments, artwork layers and delivery names must remain understandable across teams working in Arabic and English.
SKU and asset IDs should not change when the display name is translated. Stable keys keep the source, Arabic output, English output and marketplace result connected.
The interface should support Arabic direction and preserve annotations at image coordinates. Teams can discuss the same visual issue without creating separate undocumented review threads.
Package outputs into predictable locale and channel folders, with a manifest listing identifiers, dimensions and format. This makes downstream PIM or marketplace ingestion verifiable.
They can be, but stable ASCII identifiers are often safer for automated integrations; keep display names in metadata.
Yes. The regional workspace is designed for Arabic and English review context.
The customer should assign a qualified language or regional brand reviewer.
Rupato keeps uploads, specifications, tasks, review and delivery attached to the same production record.
Start an order ↗