Localising a booking platform for a new market

The demo goes well until the agency owner takes the mouse. The storefront is in their language, the logo is theirs, the search returns real fares for the route they sell most. Then they scroll past all of it, straight to the checkout, and ask the only question they came with: how do my customers pay for this? If the honest answer is "by international card", the meeting is effectively over, however good the translation was. That moment is the whole subject of localising a booking platform for a new market. The language is rarely what stops a launch. What stops it is everything the language was sitting on top of.
This piece is written for the person who carries a platform into a country — a representative, a partner, someone with the trade relationships the platform lacks. It is the list of things that actually have to change, in roughly the order they tend to bite.
Translation is the part that is already done
On this platform the storefront ships in 40 languages, right-to-left ones included (Arabic, Farsi, Hebrew and Urdu), and each site chooses which languages it offers. So the translation question in a new market is not "can it be translated" but "does it read like our trade wrote it". Have someone who sells tickets for a living read the search, the fare rules and the confirmation email. They will find the three words nobody in your market uses, and those three words cost more trust than any layout bug.
Payment rails decide what the checkout looks like
Every market has a dominant way money moves for a purchase of this size, and it is often not a card. It might be a domestic card scheme that international gateways handle badly, a bank transfer confirmed by a phone call, a mobile wallet, or cash handed over at the agency counter the next morning. Each of those produces a different checkout, and more importantly a different moment at which a booking becomes real.
A card payment settles the question in seconds. A bank transfer leaves a booking held but unpaid, and an airline fare does not wait politely while the transfer clears; the fare can change, the seat can go, the ticketing time limit can pass. So the payment method is not a field on a form. It is a decision about whether you hold, whether you ticket on promise of payment, and who is exposed if the money never arrives. We wrote about one version of this — markets where the phone wallet is the bank — in a piece on mobile money and agency booking, and the logic travels well beyond Africa.
Then currency. Each white-label picks its own default currency and the list it offers, and prices are converted from a per-site rate table. That table is somebody's job. In a market where the local currency moves quickly, a rate updated last month means every price on the site is wrong in the same direction, and the agency either loses margin silently or overcharges until a customer notices. Decide on day one who updates it, how often, and what happens on a public holiday.
For agencies selling to other agencies, the payment question changes shape again. Sub-agents in most markets do not pay per booking; they book on credit and settle weekly or monthly. Credit limits and settlement invoicing exist in the platform as first-class concepts rather than spreadsheets, which helps — but the limits themselves are a commercial judgement about local businesses that only someone on the ground can make.
Script direction, dates and names
Right-to-left is the visible part. The layout mirrors, the menus flip, and that mostly takes care of itself. The trouble lives in mixed strings: a flight number, a PNR, a price with a currency code, a passenger name in Latin letters sitting inside an Arabic or Hebrew sentence. Check every screen that mixes the two, especially the confirmation and the e-ticket, because that is the document the traveller shows at the airport.
Dates are where real damage happens. 04/05 is the fourth of May in one market and the fifth of April in the next, and a traveller who reads their own convention into a confirmation can turn up a month early or a month late. Spell the month out wherever a date is shown to a customer. Some markets also live with more than one calendar in daily life; the ticket stays on the airline's calendar, but the agent explaining it may need to translate.
Names deserve their own line in your plan. The name on the ticket has to match the passport exactly, and the passport is in Latin script even when the customer types their name in their own. Name order, family names, and transliteration habits differ by country. A booking form that does not say clearly "as written in your passport" produces name changes, and name changes cost fees or a new ticket.
Which suppliers matter locally — and which are noise
A global content feed looks impressive in a demo and can be nearly useless in practice. What an agency in your market sells is usually concentrated: a handful of routes, the local flag carrier, the low-cost airlines that dominate short-haul from the main airport, and hotels in the few destinations their customers actually go. If those are thin or missing, no amount of breadth elsewhere compensates.
So before you sign a single agency, list the routes and destinations they sell most and test them yourself. Search the obvious dates. Compare the fares to what the agency already gets. Find out which local carriers sell only direct, because no platform will show them and the agency needs to know that before they promise it to a customer.
On this platform supplier content is shared through supplier groups rather than one-to-one arrangements, and a site sees the suppliers its groups grant it. For a market launch that is useful: a local supplier you bring in can be made visible to the agencies in your network as a group, rather than negotiated site by site. Services are also switched on per site, so an agency that does not ticket flights simply does not show a flight tab. Showing a product nobody can fulfil is worse than not showing it.
Regulatory and licensing checks before you sell
Not legal advice — a list of the questions that should have a written answer, from a local adviser, before the first live booking:
- Agency licensing. Does selling travel to the public in this country need a licence, and does each agency in your network hold one?
- Ticketing authority. Who issues the airline tickets — an IATA-accredited agency, a local consolidator, or the platform's supplier — and is that arrangement in writing?
- Merchant of record. Whose name is on the customer's statement, and who carries the chargeback?
- Invoicing and tax. How must a service fee be invoiced, and is tax due on the fee, the fare, or both?
- Consumer and refund rules. What does local law require when a flight is cancelled or a package changes, and do the terms pages say it?
- Personal data. Are there rules about where passport and payment data may be stored or sent?
- Price display. Must advertised prices include every tax and fee?
Every item here has a short answer in most countries. The point is to have the answer before an agency asks — because an agency that asks and hears "we will check" assumes you have not.
Localising a booking platform for a new market in the wrong order
The expensive mistake is not any single item above. It is signing agencies first and localising afterwards. An agency that launches on a checkout its customers cannot use does not report a bug; it stops logging in. One that gets a wrong-date complaint in week two remembers the platform, not the cause. And an agency that discovers a licensing gap after selling has a regulator's problem that becomes your problem, because you were the one who brought them in. The first impressions in a new market are made once, by the first few agencies, and they talk to each other. We covered what those first weeks look like from the agency's side in how to onboard travel agencies in your market.
What stays central, and what is yours
The engine, the supplier connections, the translations and the admin panel stay with the platform. Every site gets its own admin, with role-based staff permissions, its own bookings, customers, markups and reports. What the platform cannot produce from outside is the knowledge in this article: which payment method your market trusts, which carriers matter, which regulator asks which question. That gap is the reason a country representative exists at all, and the representation page sets out how the role is structured if you are weighing it for your own market.
Translation took the platform a long way toward your country. The last stretch is local, and it is walked by someone who already knows the road.