Languages and markets
This is the second step of onboarding, and it comes before syncing your catalogue for a reason: what you choose here decides what the import builds.
Why this comes first
Section titled “Why this comes first”Your content is published per language. When Rubikc turns your catalogue into cubes, it does that for the languages you have told it about — so a language you add afterwards will not have content waiting for it.
You can add languages later, and people do. It is just more work than choosing them now.
Your default language
Section titled “Your default language”Pick the language most of your customers use. It is what a visitor gets when Rubikc has nothing better to offer them, and it is the one your content is built around.
The languages you support
Section titled “The languages you support”Add every language you intend to sell in. Adding one tells Rubikc that content should exist for it — it does not translate anything by itself, and it does not publish anything.
If you are not sure whether you will need a language, adding it costs little. Removing one later is the more disruptive direction.
What happens next
Section titled “What happens next”With your languages set, the sync and transform steps know what to build. After that, each language is published separately — see Publish in another language.
You can change all of this later in Settings, under Localization.