Rubens Knowledge Base

Strategic language planning is critical for maintaining a cohesive user experience and ensuring your 3D configurator aligns perfectly with your global brand identity. By proactively managing how your interface and product data communicate with users, you prevent friction and ensure that the digital journey feels native to every market you serve.

Automatic Detection versus Explicit Control: By default, the Rubens UI automatically detects a user's language based on browser settings or IP address, which influences standard wordings for buttons, overlays, and system messages. While this ensures immediate accessibility, it can lead to a disconnect if the configurator UI appears in a different language than your host webshop. Thinking about localization early in the project phase ensures that every touchpoint — from UI buttons to parametric labels — speaks your customer's language and follows your brand's specific tone of voice.

Controlling Language via Localization Settings: You can explicitly define the configurator’s language by setting localization parameters to match your webshop’s supported languages, providing a consistent user experience regardless of the user’s personal browser settings. Without these settings, the configurator may show standard wordings in a language that conflicts with your platform's content. If you offer the configurator in only one language, you can lock this via Tenant Settings in the Rubens Admin, whereas multi-language webshops should set the locale via the integration snippet to ensure the 3D experience synchronizes with the current site version.

Technical Documentation: Localization

The Rubens Configurator provides native support for several standard user interface languages, ensuring all standard buttons, system overlays, and navigation elements are handled automatically based on the user's locale.

The following languages are currently supported:

• English
• German
• French
• Italian
• Spanish
• Dutch
• Polish
• Czech
• Danish
• Swedish
• Portuguese
• Russian

If your target market requires a language that is not currently included in our standard offering, please reach out to us and we will check if implementation is possible for your specific project.

Technical Parameter and Script Translations: During the initial scripting and setup phase, labels and namings for specific product parameters are defined within the product logic. We provide a dedicated translation file that covers all scripted elements, ensuring that complex technical options are clearly understood by users in every market. Once these translations are integrated into the product logic, they work in tandem with your Rubens Admin settings to provide a fully localized and professional 3D configuration experience.

Managing Translations for Product Content: Product names, material names, and tool-tips are managed directly within Rubens Admin to ensure high-quality localized content for every item in your catalog. By using the language selector located at the top left of the interface, you can switch between language versions to enter translations manually for individual items. For larger catalogs, you can export your data — such as Catalog Additional Info for tool-tips or the main product lists — as a CSV file, add the necessary translations in bulk, and re-import them to update your entire digital portfolio efficiently.

Strategic Localization Support: Setting up a complex multi-language environment requires careful coordination between technical integration and content management. If you need further support in managing translations, setting up new language versions, or optimizing your localization strategy for a global rollout, our professional services team is available to guide you through the setup phase and provide the necessary translation files for your project.

Contact us at: service@roomle.com