Localization & Multi-Language

Overview

SalesOS serves global sales teams operating across multiple countries, languages, and currencies. The Localization module ensures every user sees dates, numbers, currencies, and interface text in their preferred format — while maintaining data consistency across the organization.

Whether your team spans two time zones or twenty countries, SalesOS adapts the experience to each user's locale without fragmenting your underlying data model.

Supported Languages

SalesOS supports the following interface languages with full UI translation:

Languages with less than 100% coverage fall back to English for untranslated strings.

Setting User Language Preference

Individual User Settings

Each user controls their own language preference:

1. Click your avatar in the top-right corner
2. Select Settings > Preferences
3. Under Language, select your preferred language
4. Click Save

The interface refreshes immediately in the selected language. This setting affects:

• Navigation menus and labels
• Button text and tooltips
• System messages and notifications
• Help text and empty states
• Date and number formatting (unless overridden separately)

Automatic Detection

On first login, SalesOS detects the user's browser language setting and suggests it as the default. Users can accept or change this during their personal onboarding.

Organization Default Language

Setting the Default

Administrators set the organization-wide default language in Settings > General > Localization. This language is used for:

• New user accounts before they set a personal preference
• System-generated emails (unless the recipient has a preference)
• Shared reports and dashboards viewed by users without a preference
• API responses when no Accept-Language header is provided

Fallback Hierarchy

When rendering text, SalesOS follows this resolution order:

1. User's personal language preference
2. Organization default language
3. English (US) as the ultimate fallback

Date and Time Formats

Format Options

Configuration Levels

Relative Dates

SalesOS displays relative dates (e.g., "2 hours ago", "Yesterday", "Last week") in activity feeds and timelines. These are always rendered in the user's selected language.

Week Start Day

Configure whether the week starts on Sunday (US convention) or Monday (ISO/European convention). This affects:

• Calendar views
• Weekly reports
• "This week" filter definitions

Number Formatting

Decimal and Thousands Separators

Percentage Display

Percentages follow the same locale rules:

• US: 85.5%
• European: 85,5%

Configuration

Number formatting is typically inherited from the language preference but can be overridden independently in Settings > Preferences > Number Format.

Currency Settings

Multi-Currency Support

SalesOS supports full multi-currency operations, enabling organizations to:

• Track deals in the customer's local currency
• Report roll-ups in a primary (home) currency
• Display converted amounts alongside original values
• Handle currency at the line-item level in quotes and orders

Primary (Home) Currency

Set your organization's primary currency in Settings > General > Localization > Currency. The primary currency is used for:

• Dashboard totals and roll-ups
• Pipeline value summaries
• Forecast calculations
• Default currency for new records

Supported Currencies

SalesOS supports 150+ currencies with ISO 4217 codes. Common currencies include:

Exchange Rates

Automatic Updates

SalesOS fetches exchange rates automatically from financial data providers. Rates are updated:

• Real-time rates — Updated every hour for active trading currencies
• Daily rates — Snapshot at market close for all supported currencies
• Historical rates — Preserved for accurate historical reporting

Manual Rate Override

Administrators can set manual exchange rates for specific currency pairs when your organization uses contracted rates:

1. Go to Settings > Localization > Exchange Rates
2. Select the currency pair
3. Enter your custom rate
4. Set an effective date range
5. Choose whether to override automatic rates or use manual as fallback

Rate Lock on Records

When a deal is created, the exchange rate at creation is stored on the record. This ensures:

• Deal values remain consistent regardless of rate fluctuations
• Pipeline snapshots reflect the rate at the time of forecast
• Historical reports show accurate values

Optionally, configure deals to use the rate at close date rather than creation date.

Currency Conversion

On Reports and Dashboards

All multi-currency reports show values converted to the viewer's preferred display currency (defaulting to the organization's primary currency). A currency toggle allows switching between:

• Converted — All values shown in one currency
• Original — Each value shown in its native currency
• Both — Shows original with converted amount in parentheses

Conversion Display

When displaying converted amounts, SalesOS shows:

$85,000 USD (approximately 78,200 EUR)

The conversion indicator helps users understand that the displayed amount is derived, not the actual transacted value.

Rounding Rules

Timezone Handling

Organization Timezone

The organization timezone determines:

• Default scheduling for reports and automations
• "Business hours" definitions
• Deadline calculations (e.g., end of day for tasks)

User Timezone

Each user's timezone (auto-detected or manually set) controls:

• Display of timestamps throughout the UI
• Calendar event display
• Activity log timestamps
• Notification delivery timing
• "Today", "This week" filter boundaries

Timezone in Collaboration

When multiple users in different timezones view the same record:

• Each user sees timestamps in their local timezone
• Meeting times display with timezone abbreviation (e.g., "3:00 PM EST")
• Task due dates are evaluated against the assignee's timezone
• Automated sequence sends respect the recipient's timezone

Timezone List

SalesOS supports all IANA timezone identifiers (e.g., America/New_York, Europe/London, Asia/Tokyo). The timezone selector groups options by region and shows the current UTC offset.

RTL (Right-to-Left) Support

Supported RTL Languages

• Arabic (ar)
• Hebrew (he)

What RTL Affects

When a user selects an RTL language:

• The entire interface layout mirrors (navigation on the right, content flows right-to-left)
• Text alignment flips to right-aligned by default
• Icons and directional indicators reverse
• Charts and graphs maintain left-to-right data flow (numbers always read left-to-right)
• Form fields accommodate RTL text entry

Mixed Content

When RTL users encounter LTR content (e.g., English company names, URLs, code snippets), the bidirectional text algorithm handles display correctly. SalesOS uses Unicode bidirectional control characters where needed.

Translating Custom Fields and Picklist Values

Multi-Language Field Labels

For organizations with users in multiple languages, custom field labels can be translated:

1. Go to Settings > Custom Fields
2. Select a field
3. Click the Translations tab
4. Add translations for each language your organization uses

Users see field labels in their language preference. If no translation exists, the default (original) label is displayed.

Picklist Value Translation

Dropdown and multi-select picklist values can also be translated:

Translation Workflow

1. Create fields and values in your primary language
2. Export the translation file (CSV with columns per language)
3. Send to translators or fill in yourself
4. Import the completed translation file
5. Verify in the UI by switching your language preference

Localized Email Templates

Template Language Variants

Create email templates in multiple languages with automatic selection:

• When sending to a contact, SalesOS checks the contact's preferred_language field
• If a template variant exists in that language, it is used automatically
• If no variant exists, the default (organization language) template is used
• Users can override the selected variant before sending

Merge Field Localization

Merge fields in templates respect locale settings:

Signature Blocks

Maintain separate email signature blocks per language. The appropriate signature is appended based on the template language being used.

Regional Compliance Settings

Data Residency

For organizations subject to data sovereignty requirements:

• Select your data region during setup (US, EU, APAC)
• Data remains within the selected region
• Cross-region data transfers are logged and can be restricted

Compliance Frameworks

Configure locale-specific compliance settings:

Locale-Aware Features

Certain features behave differently based on regional settings:

• Phone number formatting — Validates and formats based on country code
• Address fields — Adapt layout to regional conventions (e.g., postal code placement)
• Tax ID fields — Validate format based on country (VAT, EIN, GST, etc.)
• Business hours — Respect regional working days (Mon-Fri vs. Sun-Thu)

Best Practices

• Set organization defaults first — Configure the organization-level language, timezone, currency, and date format before inviting users. These defaults ensure a consistent starting point for everyone.
• Let users personalize — Encourage team members to set their individual preferences during onboarding. A user in Tokyo should not have to mentally convert timestamps from Eastern Time.
• Use ISO 8601 for integrations — When configuring webhooks, API connections, or data exports, use ISO 8601 date format to avoid ambiguity between international date conventions.
• Keep exchange rates current — If your deals span multiple currencies, ensure automatic rate updates are enabled. Stale rates lead to inaccurate pipeline valuations.
• Translate what your team sees daily — Prioritize translating custom field labels and picklist values over less-visible elements. Start with the fields that appear on list views and record detail pages.
• Lock rates on deal creation — For accurate forecasting, use the "rate at creation" strategy. Fluctuating currencies should not cause your pipeline value to shift without any sales activity.
• Test RTL layouts — If you have RTL users, test the full workflow in an RTL language before rolling out. Some custom components may need adjustment.
• Document locale decisions — Record your organization's chosen conventions (date format, week start, currency rounding) so new team members and administrators understand the rationale.
• Use contact language fields — Populate the preferred_language field on contacts so email templates and customer-facing documents automatically render in the right language.
• Audit quarterly — Review your localization settings quarterly as your team expands into new regions. Add new currencies, languages, and timezone coverage proactively.