What is CLDR (Common Locale Data Repository)?

The Common Locale Data Repository (CLDR) is the open dataset maintained by the Unicode Consortium that describes how locales actually behave — how dates, numbers, currencies, pluralization, and even calendar systems are written and read across hundreds of languages and regions. It is the silent infrastructure behind nearly every well-localized storefront.

Definition

CLDR ships locale data in XML and is consumed by ICU, the standard internationalization library available in virtually every runtime: Java, JavaScript via Intl, Node, PHP, Python, Swift, .NET, and more. It encodes patterns for number formats (1.234,56 in de-DE vs. 1,234.56 in en-US), date and time patterns (24-hour clocks, week start days, era names), currency display names and symbols, plural rules (English has 2 plural categories, Russian has 4, Arabic has 6), measurement systems, and territory metadata. CLDR is updated twice yearly and is the canonical source for "how does this locale really work".

Why it matters

Hand-rolling locale logic is one of the most common ways for ecommerce platforms to break silently. A handwritten "de" formatter that uses a dot instead of a comma will produce 1.234.56 EUR — technically wrong, instantly distrust-inducing. CLDR removes that risk by providing canonical, peer-reviewed data. For Composable-Commerce stacks operating across many locales, leaning on CLDR-backed APIs like Intl.NumberFormat and Intl.DateTimeFormat means new locales onboard with correct defaults from day one, without bespoke per-market formatting code.

Use cases

A storefront uses Intl.NumberFormat with locale "de-CH" to render CHF prices with the correct apostrophe thousands separator (CHF 1'234.00) rather than reinventing the format. A subscription service uses CLDR plural rules so renewal messaging works correctly in Russian, Polish, and Arabic without hardcoded if-else branches. A retailer uses CLDR's territory metadata to map countries to default currencies and likely languages, feeding its Locale Fallback chain. CLDR pairs naturally with Translation Memory and l10n workflows: translators handle the words, while CLDR ensures that the numbers, dates, and quantities around them are always rendered correctly.

Related

Explore Multi-Brand and Multi-Market.