Arabic Listings on Noon (2026): Why English-Only SKUs Lose Sales, and Exactly Which Fields Need Arabic

There is one sentence in noon's seller help centre that quietly decides how much an Indian brand sells in the Gulf: "We are not providing translations for the Seller SKU products. Every seller is responsible to create the content in both languages if needed." Read alongside noon's country table, which marks Arabic as optional in the UAE and KSA, most sellers conclude that Arabic is a nice-to-have and move on. That conclusion costs them half their addressable market, because the same help centre page also warns that "if you only provide English content for a product being sold on the UAE website, that product might only get shown on the English website and be hidden from the Arabic one".

This page is for both of the readers we usually meet: the Indian brand exporting into the UAE or KSA, who has never had to think about a second language in a catalogue, and the seller already based in the Gulf, who knows Arabic matters but wants the field-by-field rules. If you have not built a noon catalogue before, read our noon listing guide first for titles, images and the bulk upload sheet; this page goes deeper on the language layer alone. If you would rather not do it yourself, our Noon account management team builds bilingual catalogues every week.

Does noon translate my listing for me?

No, and this is the single most important fact on this page. Noon's language requirements article answers the question "Is noon providing the translation for the content of the Seller SKU?" with "We are not providing translations". What noon does translate is the structured part of the template: the dropdown attribute values you pick from a list, such as a colour family or a size, appear in Arabic automatically because noon holds both versions of that value. Everything you type freely, which is the title, the description, the feature bullets and any free-text attribute, appears exactly as you typed it and nowhere else.

So a Seller SKU built from an English-only sheet is a live, approved listing that a shopper browsing in Arabic may never see. Nothing fails, nothing is flagged, and the catalogue looks healthy in Seller Lab. That is what makes this error durable: it produces no error message.

What does "Arabic optional" actually mean on each noon site?

Noon's own table is short, and worth reproducing exactly before we interpret it:

In the UAE and KSA, noon says your English content has to be approved for the product to be eligible to go live, and then adds its own advice: "It's advisable for you to at least provide the Arabic title, if not the other content." Egypt is the only market where the two languages are interchangeable, and one of them must clear review.

The practical reading is that "optional" describes noon's approval gate, not the shopper's experience. Arabic is optional for going live and close to mandatory for being found. Noon does not publish the split of its UAE or KSA traffic between the English and Arabic interfaces, so any agency quoting you a precise percentage is guessing. What we can say is that Arabic titles are the cheapest content change on this marketplace and the one most Indian sellers have not made.

Which fields need Arabic, and which should stay in English?

Treat the template as four kinds of field. This is the table to keep next to the upload sheet.

If budget forces a choice, the order of return is: Arabic title first, then bullets, then description. A SKU with an Arabic title and English bullets is visible on the Arabic site. A SKU with neither may not be.

Translate or transliterate? The brand-name trap

Noon's brand creation guidelines are unusually specific here, because it is where most brand requests die. When you register a brand you supply the name in English and in Arabic, plus a website or social link and a logo image, and noon requires the Arabic field to be a transliteration, the same sounds in Arabic letters, not the meaning. Noon's own example: the brand ICONIC transliterates to a form reading "ikonik"; supplying the Arabic word for "creative" instead is a rejection.

Three further rejection causes from the same page are worth memorising, because each one is a week lost while the brand sits in Pending and your SKUs stay invisible:

• N/A in the Arabic field. Noon states plainly that "NA" or "N/A" in the Arabic brand name is a rejection. There is no opt-out.
• The English name repeated in the Arabic field. Also an explicit rejection. Pasting Latin characters into the Arabic box does not satisfy the requirement.
• Casing, spacing and hyphens must match the official site exactly. Noon's examples are SUNTOP rejected as SunTop, SPACESHOW rejected as SPACE SHOW, HI-TECH rejected as HITECH. Once the brand is approved you cannot edit either name yourself; you have to go through support.

Two more rules catch exporters: a verification link pointing at a competing marketplace is rejected, as is a service brand with no physical product. Use your own domain or social page, and make sure the image shows the logo on the product itself.

What RTL pitfalls break Arabic noon listings?

Arabic is a right-to-left script with joined letterforms, and a catalogue pipeline built for English quietly damages it. The failures we see most:

• Excel and CSV encoding. Save the upload sheet as UTF-8. Excel's default regional encoding turns Arabic into question marks or mojibake, and noon receives a string of nonsense that its reviewer rejects without explanation. Check one Arabic cell after saving, not before.
• Copy-paste from PDFs and images. Arabic lifted out of a PDF or run through OCR often arrives with the letters separated instead of joined, which a native reader sees instantly as broken text. Take Arabic only from a text source you can retype.
• Latin fragments inside an Arabic string. A model number or unit inside an Arabic title flips position depending on the renderer. Put identifiers at the end of the Arabic title rather than the middle, so a bidirectional reordering cannot separate a number from its unit.
• Numerals. Use Western digits (1500) rather than Eastern Arabic-Indic digits (١٥٠٠). Noon's own Arabic pages use Western digits, and shoppers search with them.
• Character counts. Arabic usually needs fewer characters than English, which helps against noon's title limit. Do not pad the Arabic title to match: noon's rules against repeated words apply in both languages.
• Machine translation. Raw output from a free translator is the commonest cause of a rejected Arabic block, and a rejected Arabic block holds up the whole SKU. If you must use a machine draft, have a native speaker edit it before upload.

Where Indian marketplace habits actively mislead you

This is the point worth saying without hedging. On Indian marketplaces, localisation is something the platform does to your listing. Flipkart and Amazon India render their interfaces in a dozen languages and handle the translation layer themselves; a seller in Bengaluru or Tiruppur has never once been asked to supply a second-language title, and has no process, vendor or budget line for it. That habit is correct in India and wrong on noon. Noon has told you in writing that it does not translate, and noon's Arabic site is not a translated view of the English one but a separate surface your SKU either appears on or does not.

Two related habits travel badly. First, the assumption that a brand name is a free-text field: on noon it is a controlled, reviewed entity that needs an Arabic transliteration before anything goes live. Second, the assumption that a catalogue can be uploaded once and enriched later. It can, but every edit to content triggers another round of noon's content checks, so a second pass to add Arabic costs review time you could have spent selling. Build the bilingual sheet once.

What does Arabic content cost, and how do I get it done affordably?

A worked example, with our assumptions labelled. Rates used: AED 1 = INR 24, SAR 1 = INR 23.5, as of September 2026; these move, so redo the sum with the rate on the day.

Say you are listing 250 SKUs of home textiles on noon UAE, with a title and five feature bullets each, roughly 60 words of copy per SKU.

Three ways to keep the cost down. Translate at the template level rather than the SKU level, since a 40-SKU bedsheet range shares most of its bullet copy. Keep a glossary of recurring terms, so a second vendor does not translate "microfibre" three ways and fragment your Arabic search matches. And translate your best sellers first. Note that prices you enter are inclusive of VAT where you are registered while noon's rate-card fees are exclusive of it, so keep language work and pricing work in separate columns.

FAQ

Is Arabic mandatory to sell on noon? Not in the UAE or KSA, where noon marks English mandatory and Arabic optional; in Egypt one of the two must be approved. But noon warns that English-only content may be hidden from the Arabic site, so optional applies to approval, not to visibility.

Does noon translate my titles and descriptions? No. Noon's language requirements page states that it does not provide translations and that every seller is responsible for creating content in both languages. Only dropdown attribute values are rendered in Arabic automatically.

Should I translate or transliterate my brand name? Transliterate: the same sounds written in Arabic letters. Noon's brand guidelines reject a meaning-based translation, an N/A, or the English name repeated in the Arabic field, and once a brand is approved you cannot change either name yourself.

Can I add Arabic content after my SKUs are live? Yes, through an edit or a re-import on the same Partner SKU, but any content change triggers another round of noon's content review, so the SKU can go back into a queue. Building the bilingual sheet at first upload is cheaper.

Is machine translation good enough for noon? Not on its own. Literal machine output is one of the most common reasons an Arabic content block is rejected, and a rejected Arabic block delays the whole SKU. A machine draft edited by a native speaker is the affordable middle route.

How much Arabic traffic will I gain? Noon does not publish the split between its English and Arabic interfaces, and we will not invent a number. Treat Arabic titles as a low-cost change with a plausible payback and measure the lift on your own SKUs after the first batch.

Getting your noon catalogue bilingual

The work is small and the order is fixed: register the brand with a correct Arabic transliteration, translate titles for every SKU, add bullets for the range that sells, keep identifiers in Latin characters, and save the sheet as UTF-8. If you would rather hand the whole language layer to a team that has done it before, see our Noon account management service.