Building for MENA Hospitality: What the Market Actually Needs
Nine years shipping platforms across the Middle East and North Africa taught me what global SaaS gets wrong about this region — and where the real opportunities are.
The Middle East and Africa restaurant POS software market is projected to grow from $328 million to $515 million by 2033. That's a nice number for a pitch deck, but it hides what's actually interesting: most of this growth isn't from new technology. It's from replacing tools that were never built for this region in the first place.
I've spent nine years building digital products for MENA hospitality and e-commerce. Here's what I've learned about what this market actually needs — and why most global SaaS fails here.
When people say "localization" in the context of MENA, they usually mean "translate it to Arabic." That's the easy 10%. The hard 90% is everything else.
RTL is not just flipping the layout. A right-to-left interface affects information hierarchy, gesture patterns, reading flow, and visual weight. I've seen global products that technically support Arabic but feel fundamentally wrong — navigation on the wrong side, icons pointing the wrong direction, form labels that break the reading rhythm.
At Menyo Pro, supporting RTL meant rethinking components from the ground up. A category list isn't just mirrored — the selection state, the drag handles, the expand indicators all need to respect the text direction. It's hundreds of small decisions, and getting any of them wrong makes the product feel foreign.
Currency and pricing conventions differ. The Gulf has multiple currencies (AED, SAR, KWD, QAR, OMR, BHD) with different decimal places. Some menus list prices without currency symbols because the local context makes it obvious — but that breaks any system that expects explicit currency markers.
Payment behavior is different. Cash on delivery is still massive in many markets. Card penetration is high in the Gulf but the preferred methods vary — Apple Pay in the UAE, Mada in Saudi, local payment rails that Stripe doesn't cover. You can't assume a global payment stack works.
Here's something that doesn't show up in market reports: MENA business owners often prefer to buy from someone they can reach. Not a 1-800 number. A person. A WhatsApp message. A local presence.
When a restaurant's POS goes down during dinner service, the owner doesn't want to file a ticket. They want to message someone who responds in five minutes. This is why regional players like Foodics (now serving 33,500+ restaurant branches) dominate despite global alternatives existing.
Trust is a feature. In a market where "who do I call when it breaks?" is a primary buying criterion, your support model is your product. Global SaaS companies that treat support as a cost center lose here, every time.
This has a product implication: your onboarding, your documentation, your error messages — they all need to be in the user's language, at their level of technical comfort. A restaurant owner in Cairo doesn't want to read a knowledge base article. They want a two-minute video in Arabic, or a WhatsApp number.
I've watched global platforms enter this market repeatedly and fail in predictable ways.
They don't understand the operational reality. A restaurant in Dubai might serve four cuisines, change its menu weekly, handle delivery, dine-in, and takeaway simultaneously, and process orders in three languages during a single shift. Products built for the linear, single-cuisine, English-only model of a San Francisco cafe don't map onto this complexity.
They optimize for the wrong metrics. Global SaaS optimizes for self-serve activation — minimize friction, let users figure it out. In MENA hospitality, the highest-converting onboarding is often high-touch: a human sets up the menu, configures the POS, trains the staff. The "self-serve" optimization actually hurts conversion because it removes the trust-building human contact.
They ignore the infrastructure context. Internet reliability varies. Device fragmentation is real — many restaurants run operations on mid-range Android tablets, not iPads. Offline-first isn't a nice-to-have; it's a requirement. I built Menyo Pro's order system to queue offline and sync when connectivity returns because I watched orders get lost when the WiFi dropped.
The market gaps I see are not in building better versions of global tools. They're in building tools that understand the region.
Vertical restaurant operations. Not just a POS — a full operations platform (menu, ordering, kitchen display, analytics) built for how MENA restaurants actually work. Multi-language, multi-currency, WhatsApp-native, offline-capable. Foodics proved the market; the next wave is deeper vertical integration.
AI-powered localization at scale. The reason most platforms don't support Arabic well is that it's expensive to do properly. An AI layer that handles real RTL layout, dialect-aware content, and local payment integration could be infrastructure that every regional SaaS needs.
Hospitality personalization. The Gulf has a culture of hospitality that goes deep. Platforms that use AI to personalize guest experiences — remembering preferences across visits, suggesting items based on dietary restrictions (halal, allergens), adapting service to cultural norms — have an edge that generic global tools can't replicate.
B2B marketplace infrastructure. The supply chain between restaurants, suppliers, and distributors in MENA is still largely manual. WhatsApp groups, phone calls, paper invoices. There's a massive opportunity in digitizing this while respecting how business actually gets done here.
Every product decision in this market comes down to one question: does this respect how things actually work here?
Not how they work in theory. Not how they work in Silicon Valley. How they work in a restaurant in Riyadh, a hotel in Cairo, a cafe in Dubai. The products that win are the ones built by people who've sat in those restaurants and watched the friction happen.
The market is growing. The opportunity is real. But it's not a technology opportunity first — it's an understanding opportunity. Get the understanding right, and the technology follows.