Skip to content
Blog

Travel agency software GCC agencies actually need

Tekravel Editorial
Written with the help of AI

The demo went well. The vendor flew through a London–Paris search, showed a clean checkout in euros, and when you asked about Arabic they clicked a flag in the corner and the menu flipped to the right. Then you typed a Riyadh–Cairo search for a family, the passenger form asked for a "first name" and a "last name" and nothing else, the date picker stayed left-to-right, and the price sat on the wrong side of its currency code. Nobody in the room said anything. It was a demo.

Most travel agency software GCC agencies get pitched was designed for a European agency and translated afterwards. That is not a moral failing; it is just where the software was born. But the gaps it leaves are not cosmetic, and they show up in exactly the weeks when your agency makes its money. This piece is about those gaps — what a Gulf agency needs from a booking platform that a European one never had to ask for.

Arabic and right-to-left are a requirement, not a feature

A European vendor lists "Arabic" on the same line as "Portuguese". For them it is one more language file. For an agency in Jeddah or Sharjah it is the language most of its customers read first, and right-to-left layout is not a translation problem at all — it is a layout problem that touches every screen.

When RTL is bolted on, the failures are predictable. Tables of flight options read in the wrong order, so the cheapest fare ends up visually last. Icons that mean "next" point backwards. Mixed strings — an Arabic sentence carrying a flight number, a PNR, a price in SAR — scramble because nobody tested the bidirectional text rules. The customer does not file a bug report. They close the tab and send your agent a WhatsApp message asking for a quote, which is the manual work the website was supposed to remove.

Names are the other half. Gulf passports carry long names with family and tribal elements, and airlines want them entered exactly as printed. A form with two short fields forces your staff to guess how to split a name, and a wrong split is a name change, and a name change on some fares is a reissue. Ask the vendor to book a real five-part name end to end and to show you the ticket.

And remember who else reads your site. A Dubai agency sells to Arabic, English, Urdu, Hindi, Persian, Russian and Tagalog speakers, often in the same week. The storefront this article is published alongside ships 40 languages, including right-to-left Arabic, Farsi, Hebrew and Urdu, and each white-label chooses which of them it offers. That is the bar to hold any vendor to: not "we have Arabic", but "show me Urdu checkout on a phone".

Payment: what your customer expects at the last step

European checkout assumes a credit card. A large share of Gulf customers do not reach for one first. Saudi customers expect mada; Kuwaiti customers expect KNET; Bahraini customers expect BENEFIT; almost everyone with a recent iPhone expects Apple Pay; and instalment options have become an ordinary question at checkout rather than an exotic one. Corporate clients want to pay by bank transfer against an invoice, and some walk-in customers still settle in cash at your counter after booking online.

None of this is the booking engine's job alone — it depends on which payment gateway you contract and which schemes that gateway is licensed for in your country. But the platform decides whether you can plug that gateway in at all, and whether a booking can sit in a "held, awaiting payment" state long enough for a bank transfer to clear. Ask that question with a fare that has a ticketing time limit, because that is where it breaks.

Currency matters in a quieter way. A Dubai storefront may want AED by default while still showing SAR, KWD or INR to the visitor who is about to fly home. On our platform each white-label picks its own default currency and the list it offers, and prices convert client-side from a rate table the tenant controls — which means you, not the vendor, decide what rate a customer sees.

The corridors that carry the volume

European agencies tune their search for leisure city pairs. A Gulf agency's bread and butter is different: workers and families flying home and back. Dubai to Kochi, Mumbai and Hyderabad. Riyadh and Jeddah to Cairo, Karachi, Lahore and Dhaka. Doha to Manila and Kathmandu. Kuwait to Beirut. Then Umrah traffic coming the other way, and every summer the outbound leisure wave to Georgia, Azerbaijan, Turkey, Bosnia and Europe.

That shapes what "good search" means. Low-cost carriers and Gulf carriers have to sit in the same result list, sorted honestly. One-way and open-jaw bookings are ordinary, not edge cases. Baggage allowance is the deciding detail for a passenger carrying gifts home, so it has to be visible before the fare is selected, not discovered in the fare rules. And a search tuned only for return trips of two adults will feel broken to a family of seven flying to Peshawar for a wedding.

Hotels follow the same logic. Makkah and Madinah properties are bought by distance to the Haram, not by star rating, and a hotel module that cannot sort or filter on that is not useful for Umrah, however pretty it looks.

Seasonality breaks a flat markup

This is the one that costs real money, so it gets the long section.

Most European platforms let you set a markup as a percentage or a fixed amount per booking, perhaps per supplier. That is fine in a market where demand rises and falls gently. The Gulf calendar does not. Fares to South Asia and the Levant move hard around Eid al-Fitr and Eid al-Adha, school summer holidays empty the cities at once, Hajj reshapes everything touching Jeddah and Madinah, and national holidays add short spikes on top. Ramadan itself flattens some routes and lifts others. The dates move every year with the Hijri calendar, so a rule written for "July" is wrong the following year.

A percentage markup sounds safe until you watch it work through a season.

Markup ruleQuiet weeksEid and summer peaksWhat actually happens
Flat percentage on every fareMargin looks thin on cheap fares; you are uncompetitive on nothingMargin balloons on fares that have already jumped in the customer's eyesCustomers screenshot your price next to the airline's and call you a thief, in a week when you need them most
Fixed amount per ticketReasonableToo small to cover the extra handling — date changes, waitlists, family splitsYour staff work hardest for the least per booking
Different rule per route or fare bandTunableTunableWorks, if the platform lets you change it without a developer and see bookings per rule afterwards
Different rule per customer type (retail, corporate, sub-agent)Protects your B2B pricesStops your sub-agents undercutting your own retail siteEssential once you sell to other agents at all

You can disagree with the last column — some agencies happily run a flat percentage all year and accept the angry calls. But decide it on purpose. The test for a vendor is simple: ask them to change a markup for one route, for one customer type, from tomorrow, and to show you where you would see whether it worked. If the answer involves a support ticket, the answer is no.

What travel agency software GCC buyers should ask a vendor

Take this list into the next demo and make them show, not tell.

  • Run a full checkout in Arabic on a phone, including the passenger form, the payment step and the confirmation email. Then do it in Urdu.
  • Book a long, multi-part passport name and show the issued ticket.
  • Show the default currency and the list of currencies offered, and who sets the conversion rate.
  • Show how a fare is held while a customer pays by transfer, and what happens when the ticketing time limit arrives first.
  • Change a markup for one route and one customer type without contacting support.
  • Require sign-in before search for agency customers, and register a business customer with manual verification — on our platform both are switches per storefront, because many Gulf agencies sell B2B and retail from the same brand.
  • Show sub-agent credit limits and settlement invoices as part of the system, not as a spreadsheet you export to.
  • Switch a service off. If you do not sell attractions, your customers should not see an empty attractions tab.
  • Attach your own domain later without losing the one you launched on.

Nothing on that list is exotic. It is simply the list a European agency never writes, because none of it bites them.

What it costs to get this wrong

The cost is rarely the licence fee. It is the Eid season when your Arabic checkout drops customers back to WhatsApp, and your best agents spend the busiest fortnight of the year re-keying bookings by hand. It is the sub-agent who learns your markup is the same for them as for walk-ins and quietly moves to a consolidator who treats them as a business. It is the name-split mistake that turns a cheap fare into a reissue. A platform migration in the middle of a year costs you a season; choosing badly at the start costs you two.

If you want to see how an Arabic storefront behaves with your own logo before any of those conversations, start one on the white-label wizard — it provisions a branded site on a platform subdomain straight from the form and does not ask for a card. The feature overview lists what each tenant gets. And if your real business is supplying other agencies across the Gulf, the more relevant read is how supplier content is shared with partner agencies.

Tekravel Editorial

Travel technology desk

The Tekravel travel-technology desk writes for the trade: agency owners, consolidators and the developers who integrate them. Every article is checked against the platform it describes before it is published.