Check-in App Translation
The Check-in App Translation add-on lets you translate the Checkinera mobile and web apps into any language — useful for events with non-English-speaking gate staff, multi-country tours, or just localizing the experience for your home market. Strings like “Check in,” “Already used,” “Invalid ticket,” “Scan again” can all be swapped to the language your team works in.
The Check-in App Translation add-on lets you rename every label, button, and status message used across all Checkinera touchpoints: the iOS app, the Android app, and the Checkinera plugin (web app). Once you save your wording, every device that signs in with your site’s WordPress URL and Tickera API key pulls the same strings automatically.
Where to edit
Open Tickera → Settings → Check-in App Translation. You’ll see text inputs for the interface strings staff interact with during check-in (login prompts, success/fail states, search labels, list headers, field names such as Ticket type, Buyer name, Attendee email, confirmation prompts like Are you sure you want to sign out?, and so on). Replace the English text with your preferred wording and Save Settings.
Devices and apps pick up changes the next time they load or sign in—no rebuilds or redeploys needed.
Scope and behaviour
- Affects Checkinera iOS, Checkinera Android, and Checkinera web app UI strings (labels, buttons, prompts, messages).
- Does not affect Tickera strings on your website (checkout pages, shortcodes, admin areas). Those are translated through standard .po and .mo WordPress language files, as explained here.
- Also applies to custom Checkinera builds distributed privately or published to the Google Play Store / Apple App Store by Lifetime license holders who use the source code.
Practical tips
Keep phrases short so they fit on small screens. Prefer clear actions (Sign in, Check in, Cancel, Success, Wrong ticket code). If you rename terms (e.g., “Check-ins” → “Scans”), stick to the same wording everywhere to avoid operator confusion.
Troubleshooting
If a device still shows old text, have staff sign out and back in to refresh strings. If nothing changes, confirm the device is pointed at the correct WordPress URL and using a valid API key for your site; the apps can only fetch translations after a successful login.
Related questions
Was this article helpful?
Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.