• About Us
  • The Value Of Tourism
  • Why Tratok?
  • Tratok Features
  • Tokenomics
  • Buy Tratok
  • Buy TRAT → Explore Platform →

    Missed the localization? Well its back and improved.

    Global Ecosystem

    Sixteen Languages. And Yes, We Translated The Fine Print Too.

    Menu labels are the easy part. Cancellation terms, wallet flows, a genuine right-to-left rebuild, and live translation of every review, listing and message the moment it is written are not. Here is what full localisation actually means on Tratok.

    Carol

    Community Manager, Tratok

    I have a small test I run on every service that calls itself multilingual.

    I switch it into another language. Then I go and find the cancellation policy.

    Nine times out of ten, the navigation is beautifully translated, the buttons are perfect, the marketing copy sings. And then the instant something actually matters, the money, the refund window, the terms you are about to agree to, it quietly snaps back into English. Sometimes with an apologetic little asterisk.

    That is not localisation. That is a translated menu bar with a monolingual product hiding behind it.

    Tratok runs in sixteen languages. All the way down.

    The sixteen

    English

    English

    Français

    French

    Español

    Spanish

    Deutsch

    German

    हिन्दी

    Hindi

    日本語

    Japanese

    한국어

    Korean

    Русский

    Russian

    العربية

    Arabic, RTL

    Türkçe

    Turkish

    中文

    Chinese

    Português

    Portuguese

    Bahasa

    Indonesian

    Tiếng Việt

    Vietnamese

    ไทย

    Thai

    Italiano

    Italian

    Most apps translate one layer. We did four.

    Localisation is not one job. It is four, and they get progressively harder and progressively more expensive. Most platforms stop after the first.

    1

    The interface

    Buttons, navigation, labels. The layer everybody does, because it is the layer everybody can see in a screenshot.

    2

    The booking flow

    Search inputs, guest counts, date pickers, party sizes, time slots. Every field you touch on the way to a confirmation, across stays, activities and dining.

    3

    The wallet

    Deposits, withdrawals, network selection, transfers, balances. The screens where a misunderstanding costs you actual money rather than a mildly confusing afternoon.

    4

    The fine print

    Cancellation terms. Refund previews. What you actually get back and by when. This is the layer almost nobody bothers with, and it is the only one that matters when a trip goes sideways.

    You should not have to read a refund policy in your second language. Especially not at an airport. Especially not at speed.

    The part we could not translate in advance

    Those four layers have something in common, and it took me embarrassingly long to notice it.

    Every one of them could be done ahead of time. Buttons, wallet screens, cancellation terms. All static. All translated once, shipped in the box, done.

    But almost everything that makes travel genuinely useful is not static. It was written by a person, in their own language, and quite possibly about ninety seconds ago.

    The host mentioning that the front gate sticks and you have to lift it slightly. The review from someone who stayed in that exact room last week and thought the traffic noise was worth flagging. The listing description a family in Chiang Mai wrote about their own guesthouse, in Thai, because Thai is the language they think in.

    None of that can be pre-translated. At the moment we ship, it does not exist yet.

    So Tratok translates it as it happens.

    Chat

    with your host

    Reviews

    every one of them

    Descriptions

    written by providers

    Comments

    across the community

    One review. Written once. Read by everyone.

    A guest writes, in Japanese

    駅から近くて、朝食がとても美味しかったです。

    Tratok engine, in-house

    You read, in Spanish

    Cerca de la estación, y el desayuno estaba delicioso.

    وتقرأ بالعربية

    قريب من المحطة، والإفطار كان لذيذاً.

    Nobody presses a button

    I want to be specific here, because this is where most platforms quietly give up and hope you do not notice.

    You have seen the pattern. A small “Translate this review” link sitting under a wall of text you cannot read. It looks generous. Consider what it actually does: it turns reading other people’s experiences into an active decision, taken one review at a time, and almost nobody bothers more than twice.

    So you end up reading only the reviews written by people who happen to share your language. That is not a smaller sample of opinion. It is a skewed one.

    On Tratok there is no button, because there is no decision. Reviews arrive in your language. Chat arrives in your language. The host writes in Thai, you read it in Portuguese, and neither of you did anything at all.

    Why “in-house” matters far more than it sounds like it should

    On paper that phrase reads like an engineering footnote. It is not. It is the entire reason the section above is possible.

    Most platforms rent translation from a third party and get billed by the character. And the instant translation carries a per-character price tag, it stops being a product feature and becomes a budget line. Budget lines get rationed.

    Translate the listing but not the reviews. Translate on tap, so you only pay when somebody asks. Truncate at two hundred characters. Every one of those is a finance decision wearing a product decision’s clothes, and you can feel it in the interface.

    Tratok’s translation runs on technology we built ourselves. That changes three things, and all three of them land on you rather than on us.

    Speed

    No round trip out to somebody else’s API and back. Chat behaves like chat, not like chat paying a translation tax on every message.

    Cost

    No per-character invoice landing at the end of the month. Translating one more review costs us close to nothing, so we do not ration it. There is nothing to ration.

    Privacy

    Your conversation with your host is not couriered off to an external vendor to be read and handed back. It stays inside the platform.

    Right-to-left is not a font change

    Here is the thing people underestimate about Arabic support.

    It is not “display the same screen with different characters.” The entire layout has to mirror. Navigation flips. Back arrows point the other way. Progress bars fill from the opposite side. Prices, dates, form fields, the reading order of a booking summary, all of it reverses.

    Get one element wrong and the screen feels subtly, maddeningly broken in a way that is hard to articulate and impossible to ignore.

    The same booking summary, both directions

    Left to right

    Booking details

    Free cancellation

    1,240 TRAT

    Confirm booking

    Right to left

    تفاصيل الحجز

    إلغاء مجاني

    1,240 TRAT

    تأكيد الحجز

    Look at the progress bar. It does not just sit there. It fills from the other side, because in Arabic that is the direction progress moves. That single detail is the difference between a product built for a language and a product that had a language bolted onto it.

    Tara speaks too

    A concierge who only works in English is not a concierge. She is a language test.

    Tara searches real listings, prepares bookings, handles cancellations and answers questions about your trip in your language, not in a machine-translated approximation of it bolted on after the fact. Ask her in Thai, get an answer in Thai. Ask her in Portuguese at two in the morning because your connection got cancelled, get an answer in Portuguese.

    Why I keep going on about the fine print

    Because booking a hotel in your second language is fine. Slightly effortful, occasionally funny, ultimately harmless.

    Agreeing to a cancellation policy in your second language is how people get hurt. You skim. You assume it says what these things usually say. And then the trip changes and you discover it said something else entirely.

    Travel is the one product category where the customer is, almost by definition, far from home and slightly out of their depth. Building it English-first and translating the pretty bits later is a choice. We made a different one.

    The world’s travel token, and the obligation attached to that phrase

    We call Tratok the world’s travel token. Its a lovely phrase but also it is the sort of thing anyone can put on a slide and nobody can be held to.

    So here is the version I will actually defend.

    TRAT is a utility token. Its whole job is travel redemption. And a utility token that only works comfortably for people who happen to read English is not a world travel token. It is a travel token for a slice of the world, with an ambitious marketing department.

    A global rail only means something if the person sending, the person receiving, and every single word correspondence between them all work in whatever language each of them actually thinks in. The review. The listing. The message at midnight about the sticking gate. Otherwise you have built a very sophisticated way of serving precisely the customers everybody else was already serving.

    Sixteen languages in the product. Everything else translated the moment it gets written.

    Stay tuned for more updates on additional features.

    Carol

    Community Manager, Tratok

    On TRAT. TRAT is a utility token used to redeem travel, stays, activities and dining within the Tratok ecosystem. Nothing in this post is investment advice, and nothing here should be read as a statement, forecast or implication regarding token value.

    Never miss an update

    Get new Tratok articles by email — the moment they publish, or as one weekly digest.

    Delivery frequency