Localisation is an architecture decision covering interface direction, taxonomy, search, payments and content operations. Translation is just swapping the words, which is why translated-only stores usually underperform.

RTL-native layout, Arabic product taxonomy built for how customers search rather than translated literally, Arabic search configuration, local payment methods, and content operations that sustain quality in Arabic over time.

As an architectural decision built into the theme and app layer from the start, not a stylesheet flip applied afterwards, so navigation, forms, imagery and iconography all work correctly in a right-to-left layout.

We build taxonomy around the terms Arabic-speaking customers actually search with, and configure search indexing, stemming and synonyms specifically for Arabic rather than reusing English search configuration.

Typically mada, STC Pay, KNET, BENEFIT, NAPS, Thawani, Tabby, Tamara and cash on delivery, depending on which markets the storefront serves.

By building content operations that can sustain both languages long-term, not just launch them, including workflows and ownership for who maintains the second language after go-live.

Most programmes run 8 to 12 weeks for the first language, with each additional market or language adding a smaller, defined increment.

Yes. Our multilingual architecture work extends beyond Arabic, including European-market storefronts across multiple languages and currencies.