Localization · 24 languages

Every member,
in their own language.

24 languages built in — English, German, French, Italian, Spanish, Korean, Japanese, Mandarin, Arabic, Persian and more. Each member and staff account picks its own. Dates, currency, copy, and right-to-left layout follow them across every venue.

Try the demo Talk to us

All 24 languages enabled on every plan, including Starter.

Catalog · 24 locales

Every language,
in the box.

Each entry ships with its own translations, date-fns locale, and BCP-47 tag — so dates, times, and currencies render the way customers expect at home.

  • English

    en

  • English (UK)

    en-gb

  • Deutsch

    de

  • Français

    fr

  • Español

    es

  • Italiano

    it

  • Português

    pt

  • Nederlands

    nl

  • Polski

    pl

  • Lietuvių

    lt

  • Dansk

    da

  • Norsk

    nb

  • Svenska

    sv

  • Suomi

    fi

  • Türkçe

    tr

  • Українська

    uk

  • Bahasa Indonesia

    id

  • فارسی

    fa

  • العربية

    ar

  • 한국어

    ko

  • 日本語

    ja

  • 简体中文

    zh-cn

  • 繁體中文（台灣）

    zh-tw

  • 繁體中文（香港）

    zh-hk

The problem

One-language software
leaves money on the table.

Most venue tools ship in one or two languages — and the "translation" is a mangled Google Translate pass that staff turn off within a week. Members fall back to English they don't fully understand, mistype dates, miss reminders, and abandon checkout.

The fix isn't a translation widget bolted onto a single language. It's a platform where every screen, every email, every receipt and every TV display ships in real localized copy — and where the rig you call "Big Brother" in English shows up as "Didysis brolis" for your Lithuanian member.

GTLane treats localization as a first-class concern, not a plugin. Every translatable field is multilingual JSON, every user has their own language, and every locale ships with its own date-fns rules and right-to-left support where it matters.

What single-language tools can't do

  • Show a Korean member their booking flow in Korean
  • Render the lounge TV in Arabic without a separate build
  • Translate rig and package names per locale, not per tenant
  • Format dates as `mar 15` for FR and `Mar 15` for US
  • Default a Polish customer to Polish without staff intervention
How it works

From sign-in
to receipt, in their language.

01

Pick your venue's default

In Settings → Languages, choose the default for new visitors. The dashboard, member portal, and email templates ship with content in every supported language out of the box.

02

Members and staff override

Each profile has its own language picker. Members see their dashboard, receipts, and reminders in the language they pick — staff see admin in theirs. No conflicts.

03

Translatable content stays in sync

When you create a rig or membership tier, fill in the English name plus any locales you want. Members see the version in their language; if it's missing, the platform falls back to English so nothing ever breaks.

Capabilities

Localization that
actually localizes.

Per-user language preference

Every member and staff account picks its own language. Sign-in screens, dashboards, receipts, and emails all switch — no shared tenant-wide setting that compromises somebody.

Localized dates, times, currency

Each language ships with its date-fns locale and BCP-47 tag, so calendars, timestamps, and currency formats match what your customer expects in their region.

Right-to-left ready

Arabic and Persian render right-to-left across the dashboard, member portal, and TV display — without hand-tweaked layouts or rebuilt components.

Translatable content fields

Rig names, package descriptions, membership perks, and rewards are stored as multilingual JSON. Members see them in their own language; you maintain a single record per item.

Auto-detect from country code

New customers default to a language inferred from their nationality — Korean for KR, Polish for PL, English for everywhere we can't tell. Override anytime from their profile.

Same platform, no upcharge

Localization isn't a premium tier. Every plan ships with all 24 languages enabled. Add a new locale in your venue, and members in that language can use the system the same day.

Comparison

Built-in localization
vs everyone else.

Generic SaaS Spreadsheets GTLane
24 languages out of the box Partial
Per-user language preference
Right-to-left support (Arabic, Persian)
Localized dates, times, currency PartialManual
Translatable rig / package / perk content Manual
Auto-detect from customer nationality
No premium tier upcharge Partial
Pit-stop pricing

One hour of rental.
Per rig. Per month.

Whatever you charge for one hour on a sim — that's your monthly fee per rig. No upfront payment. No setup fees. The math couldn't be simpler.

Your monthly bill — calculator

Rigs
×
$
Your hourly rate
=
$120 / month
Hourly rate × rigs equals your monthly bill. Same simple formula whether you run 2 rigs or 20.

No upfront payment

Start today. We bill you next month.

No setup fees

Self-guided onboarding gets you live in 24h.

Cancel anytime

Month-to-month. No long contracts.

Claim launch pricing
FAQ

Frequently asked questions

Which languages are supported?
GTLane ships with 24 languages: English (US and UK), German, French, Italian, Spanish, Portuguese, Dutch, Polish, Lithuanian, Danish, Norwegian, Swedish, Finnish, Turkish, Ukrainian, Bahasa Indonesia, Persian, Arabic, Korean, Japanese, Simplified Chinese, Traditional Chinese (Taiwan), and Traditional Chinese (Hong Kong). Every language is enabled on every plan.
Can each member pick their own language?
Yes. Language is a per-user setting, not a per-venue one. A member from Berlin and a member from Tokyo using your venue both see the booking flow, dashboard, receipts, and emails in their own language. Same for staff: front-desk in Polish, ops manager in English, no conflicts.
How do dates and currency formats work?
Each language ships with its own date-fns locale and BCP-47 tag. So a French member sees `mardi 15 mars · 19h00` and a US member sees `Tue, Mar 15 · 7:00 PM`. Currency display follows the locale's separator and grouping conventions automatically.
What about right-to-left languages?
Arabic and Persian (Farsi) render right-to-left across the entire platform — admin dashboard, member portal, lounge TV display, and emails. We don't ask you to maintain two separate UIs; the layout flips at the component level so adding more RTL locales later is a one-line catalog change.
Can I translate my own content — rig names, package descriptions, perks?
Yes. Any field that members see — rig names, package descriptions, addon labels, membership perks, reward descriptions — is stored as a multilingual JSON dictionary. The admin edit screen shows a tab strip per language so you can fill in translations as you go. English is required as the canonical fallback; the rest are optional.
What happens if a translation is missing?
The platform falls back to English on a per-field basis, so nothing ever ships blank. A member browsing in Korean will see the Korean rig name where you've set one, and the English name where you haven't. That means you can roll out a new locale incrementally without holding back the whole launch.
How is the customer's language detected on first visit?
On checkout we look at the nationality the customer enters and map it to a likely language — Polish for PL, Lithuanian for LT, Korean for KR, and so on. Members can change it in their profile any time. New visitors with no nationality default to your venue's primary language.
Can I add a new language that's not in the catalog?
Adding a new locale requires a backend catalog change plus a translation pass — not a self-service operation today. If you operate in a region that's not covered, contact us. We've added new locales for operators in days, not months.

Open the doors
to every member.

Try the live demo in your own language, or talk to us about a locale that's not in the catalog yet.

Try the demo Contact us