ZenotiHelp

Translate custom form content

ZTZenoti Docs Team Updated October 26, 2026 3 min readGuide

Zenoti supports translating form titles, field labels, custom list values, and the custom data labels (Guest Custom Data, Service Custom Data, Unified Form) into every language that is enabled for your organization. Guests see the form in whichever language they have selected on the Webstore, kiosk, or MyZen; providers see the form in their own UI language inside the appointment view.

Note: Form localization applies to forms built with the modern form builder. Legacy (HTML-based) form text is delivered exactly as authored and is not dynamically translated.

Before you begin

  • The Enable V3 form localization setting must be turned on for your organization. Without it, language variants are not saved and the form is delivered in the authored language only.
  • The Enable localization on web setting must be turned on if you want translations to appear on the Webstore.
  • The languages you want to translate into must be enabled as active languages for the organization.
  • Prepare the translated text in advance. Zenoti stores translations that you paste or type in; it does not machine-translate on your behalf.

Permission: Edit under CustomFields in the Administrator section of the security role — Required to manage form definitions and add translations.

What you can translate

Content Scope
Form title Per form definition
Section and field labels Per form definition
Dropdown and radio option labels Per custom list value
Help text, placeholder text, and content blocks Per form definition
Custom data labels ("Guest Custom Data", "Service Custom Data", "Unified Form") Organization-level; set on the Configure form settings page under Labels

Supported languages

Zenoti ships translations for the following languages. Additional languages can be requested through your Zenoti contact.

Code Language
da Danish
de German
en-IN English (India)
en-US English (United States)
es Spanish
es-419 Spanish (Latin America)
fi Finnish
fr French
fr-CA French (Canada)
it Italian
nb-NO Norwegian Bokmål
nl Dutch
pt Portuguese
sv Swedish

Translate a form

  1. Navigate to Configuration > Forms > Form creation > Custom forms.
  2. Open the form you want to translate.
  3. Switch the form builder's language selector to the target language (for example, fr for French).
  4. Replace each visible label, option, and content block with the translated text.
  • Field names, section headings, and help text come from the form definition.
  • Dropdown and radio option labels come from the underlying custom list; open the list and add a translation per value.
  1. Repeat for each additional language.
  2. Save the form. Zenoti stores a translation per language alongside the authored text.

Translate the custom data labels

The top-level labels ("Guest Custom Data", "Service Custom Data", "Unified Form") appear in the appointment book, the guest profile, and reports. They are set organization-wide and have their own translation entries.

  1. Navigate to Configuration > Forms > Essentials > Labels.
  2. Select a language from the language selector.
  3. Enter the translated label text (up to 250 characters per label).
  4. Save.

How translations are delivered

  • Appointment view (Web) — The provider's UI language determines which translation the form renders in.
  • Webstore — The guest's selected Webstore language determines the form language.
  • Kiosk — The kiosk's configured language determines the form language at check-in.

If a specific translation is missing for the requested language, Zenoti falls back to the authored (default) text for that field.

Keeping translations in sync

Zenoti does not automatically update translated strings when you change the original (authored) label. If you rename a field label or update consent text in the default language, each translated version of that label remains unchanged until you manually update it.

After editing any label in the default language:

  1. Open the form's language selector and switch to each active language in turn.
  2. Locate the changed label — it still displays the old translated text.
  3. Update the translated text to reflect the change.
  4. Save.

If you skip this step, guests using non-default languages will see the old translation alongside the updated default-language content.

Tips

  • Translate the most frequently used forms first — guest intake, consent, and membership forms typically produce the highest translation-coverage value.
  • Review translations with a native speaker before publishing. Machine-translated clinical content can mis-render in regulated settings.
  • If a form uses a macro (for example, {{GuestFirstName}}), leave the macro token untranslated. The macro resolves to a value that the system does not translate.
Was this article helpful?
Your feedback helps us improve our documentation.