Migration Guide
All tenants must complete the migration by September 12, 2025. Contact your SCAYLE Account Manager for questions.
While the legacy system has not yet been fully deprecated, tenants who are still using the Crowdin-based translation setup can continue to access the corresponding documentation. Guidance on how to manage checkout translations via Crowdin remains available until the transition to the SCAYLE Panel is complete.
Crowdin Translations vs. SCAYLE Panel - Key Changes
| Feature | Legacy System (Crowdin) | New System (SCAYLE Panel) |
|---|---|---|
| Where to manage? | External Crowdin UI | ✅ Directly in SCAYLE Panel |
| Translation visibility | Delayed updates | ✅ Near real-time updates |
| Default translations | Manual per project | ✅ Automatically provided |
| Language setup | Manual initialization | ✅ Based on shop/country setup |
| Overwrites | Not easily manageable | ✅ Shop- and language-specific |
| AI Translation | Not available | ✅ DeepL integration for suggestions |
What Happens During Migration: Translation Layer Logic
While some tenants are still using the legacy Crowdin system, the checkout will continue to prioritize translation sources using the fallback hierarchy.
The following table shows how the system resolves which translation to display, during the transition period:
| Layer Name | Hierarchy | Description |
|---|---|---|
| Panel Translations | 1 - Highest priority | These are custom translations made by tenants directly in the SCAYLE Panel. If a translation key is defined here, it will always be used. |
| Crowdin Translations | 2 - Being phased out | Previously managed through Crowdin, these translations take priority over default ones, but will be removed as the system moves fully to the SCAYLE Panel. |
| Locale-Specific Defaults | 3 - Medium priority | For example, if a shop is configured with de_DE, the default German translations are loaded automatically—no extra setup required. |
| Global Default (en_GB) | 4 - Lowest priority | This is the fallback language. If no translation is found in any of the layers above, the system uses the English (UK) default (en_GB).If customers see English text, it usually means that a translation is missing in their local language. |
Migration of Custom Locales from Legacy (Crowdin) to SCAYLE Panel
When migrating from the legacy Crowdin system to the SCAYLE Panel, tenant-specific locales and overrides are handled carefully to preserve your setup. Below is how the system behaves depending on your configuration:
What Happens During Migration?
- Custom locales used in Crowdin (e.g.,
hr_HR,de_AT) will be automatically migrated to the SCAYLE Panel. - All translation keys and values from Crowdin will be imported and published automatically in the new system.
- These migrated locales will behave as custom locales, meaning:
- They will not receive automatic updates for new translation keys.
- Tenants are responsible for manually maintaining those translations over time.
In the legacy Crowdin translation system, it was common to use country-specific locales for the same language. For example, Germany used de_DE and Austria used de_AT, even though both use the German language.
To reduce maintenance and improve performance, we recommend switching manually to one of the SCAYLE-provided default locales (e.g., switch de_AT to de_DE) whenever the same language can be used across markets.
