Kuwaiti dialect sells food; formal Arabic reads like a ministry circular
Formal Arabic is the language people read in a ministry circular, not the language they use when they are hungry. Write اطلب الحين and it lands. Write اطلبوا الآن عبر منصتنا الإلكترونية and the thumb keeps moving. In most restaurant accounts we run in Kuwait, the same offer written in dialect costs 20–40% less per order than the MSA version. Nothing else changes — same photo, same audience, same budget, same landing page. The dialect version simply reads as a person talking, and food is bought by someone who is already deciding in the next thirty seconds.
Dead copy is almost always a process problem, not a writer problem. Someone writes the ad in English, hands it to a translator, and the Arabic comes back grammatically perfect and emotionally flat. Jokes do not survive translation. Rhythm does not survive it either. Melt-in-your-mouth becomes a phrase nobody in Kuwait has ever said out loud. Write the Arabic fresh instead, in a real Kuwaiti voice — the kind of person who would say ما تفوتك or طلبيتك بنص ساعة. Two originals beat one original plus a translation every single time, and the difference costs about fifteen minutes.
English is not dead here, its job is just narrower. Sushi, specialty coffee, poke, brunch and anything priced above 6 KD a head performs fine in English, especially in Salmiya, Mahboula, Fintas, Mangaf and around the Avenues, where the audience skews expat plus young Kuwaitis who scroll in English anyway. Below roughly 3 KD a head — shawarma, breakfast, machboos, family trays — dialect Arabic wins almost everywhere, including Jahra, Farwaniya and Sabah Al Salem. Let the neighbourhood and the ticket size tell you which language leads, not what sounds more premium in the meeting room.
Ready to start your Shopify store?
Start a free trial and try the platform for yourself.
Run Arabic and English as two ad sets, never as one bilingual ad
Do not build a bilingual ad. One image with Arabic stacked on English halves the size of your headline and doubles the time it takes to read, and the platform ends up optimising against a blended audience. Build two ad sets instead: one Kuwaiti dialect, one English, same offer, same ordering destination, separate creative. Start the budget around 70/30 in favour of Arabic for a mass-market menu, or 50/50 for a specialty concept. Give each side at least 40–50 KD before you judge it. Under that you are reading noise, not a result.
After a week the numbers decide, not the owner's taste. Look at cost per order, not clicks, not saves, not reach. In most accounts one language pulls clearly ahead and takes 70–80% of the budget within two weeks, while the other keeps a small floor so you do not lose that audience entirely. Layer area targeting on top of the split: the Arabic set on Jahra, Farwaniya, Sabah Al Salem and Andalous; the English set on Salmiya, Mahboula, Fintas and Kuwait City. Same money, two conversations, and the platform stops averaging them into mush.
Check the split per platform and per hour, not as one blended number. Snapchat audiences in Kuwait skew younger and Arabic-first, and the dialect ad often carries almost everything there. Instagram can go either way depending on the concept. Dayparts matter just as much: the 11pm to 2am order rush is heavily Arabic, while the 8am to 11am coffee window leans English in the expat belt. If your reporting only shows one average, you will keep funding the losing language at the exact hour it is losing, and you will never see it.
Never translate the dish name, and decide the menu language separately
Never translate the dish name. مجبوس is machboos, not spiced rice with chicken. Shawarma, harees, tashreeb, mutabbaq, luqaimat, balaleet — write them the way people actually order them, in whichever script the ad is running in. The rule runs the other way too: do not turn poke bowl into وعاء سمك نيء or cold brew into قهوة مخمرة باردة. Carry the sound across, not the meaning — بوكي بول، كولد برو. People search and speak the sound. If your ad uses a word nobody types into a search bar, nobody finds you, and the ad is doing half a job.
The menu is a separate decision from the ad, and most owners get it backwards. Your printed and delivery-app menu should be bilingual: dish name transliterated in both scripts, description written once per language rather than translated. Your ordering page should open in the language of the ad that sent the customer there — when an Arabic ad lands on an English-only checkout we usually see a 10–20% drop at the last step. If you want to own that ordering flow instead of paying Talabat 25–30% forever, Shopify runs an Arabic and an English storefront off one store with KNET at checkout.
One more thing owners underrate: the reply language. If someone comments or DMs you in dialect and the account answers in polished MSA or English, the conversation ends there. Answer in whatever language they opened with, dialect included, and keep the reply under two lines. Same for WhatsApp order confirmations and Instagram story replies. This costs nothing — it is the cheapest thing on this page — but it is where the trust behind a 3 KD order is built or lost, long before anyone looks at your ad creative again.