# Is per-locale default content included or an add-on?

Asked by arjun_m on 2025-10-06. Tags: localization, plans, content.

We serve en, zh, and ms from the same storefront in Singapore.

Expected: define default content per locale on each slot as part of the base
plan, since the SDK clearly supports locales.

Actual: localization shows up listed separately from the plan features, so I
want to confirm before I design our content model around it.

Is per-locale default content an add-on, and if so how do the locale options
in the SDK relate to it? we already pass preferredLocale in some fetches so
I'm confused about what is included where.

## 1 answer

### Answer from kenji_t (2025-10-06)

Localization, meaning per-locale default content on slots, is an add-on
rather than part of the base plans. The SDK-level locale plumbing
is always there though, which is why you can already pass `preferredLocale`.

How the pieces fit:

- `preferredLocale` is accepted by all the fetch paths: `croct.fetch`
  options in the JS SDK, `useContent` in React, and `fetchContent` on the
  Next.js server side. It tells Croct which locale variant of the content
  to resolve.
- The CLI config (`croct.json5`) declares `defaultLocale` and `locales` for
  the project, so your tooling knows the locale set up front.
- With the add-on enabled, editors maintain default content per locale in
  the dashboard and the fetch resolves the right one. Without it, you get a
  single default and would handle language variants in your own content
  layer.

One nice detail once it is on: the preview widget shows which locale you are
previewing along with the experience and variant, so QA across en/zh/ms is
straightforward. For a three-locale storefront I would just price the add-on
in from the start rather than model around it.