Sign Customiser

Choose the customiser language on Shopify and Universal

Copy page

Set up one multilingual customiser and control how Shopify and Universal choose a published shopper language.

Last updated:

Use one customiser with several published languages. Shopify normally follows the shopper’s active Store language. Universal can use an explicit language code, a storefront signal, browser preferences, or the customiser default.

You no longer need one duplicated customiser per language. Existing duplicates can stay in place, but new multilingual setup should use the Languages page in one customiser.

Shopify

  1. Add and publish each shopper language under Customisers -> [customiser] -> Settings -> Languages.

  2. Enable the matching storefront languages in Shopify Markets.

  3. Translate the surrounding theme, navigation and page copy with Shopify’s translation tools or another Store translation app.

  4. Open the Sign Customiser theme block and leave Language code override blank for normal automatic matching.

  5. Test each live Store language route.

The theme block follows Shopify’s active storefront language for supported inline, iframe, app-embed and modal integrations. Use Language code override only when a special template or landing page must force one exact published language.

Add and publish languages through the same Languages page. To request one exact published language for a hosted link or iframe, add language_code to the URL:

HTML
<iframe src="https://web.signcustomiser.com/embed/YOUR_CUSTOMISER_ID?language_code=fr" style="width:100%; height:700px"></iframe>

For the supported custom element, use its language attribute:

code
<sign-customiser-embed customiser-id="YOUR_CUSTOMISER_ID" language-code="fr"></sign-customiser-embed>

Without an explicit language, a storefront language signal or browser preference may select a published match. Otherwise the customiser uses its default language.

Matching regional variants

  • An exact published language code wins.

  • A broad code such as fr can match one published regional French variant when there is only one clear choice.

  • When several published regional variants could match, the customiser uses the default instead of guessing.

  • An explicit language_code must match exactly. An invalid or unpublished explicit code goes directly to the default.

Provide a language selector when needed

Sign Customiser has no shopper-facing language switcher. Shopify shoppers use the Store’s language selector. A Universal site must provide its own selector or language links if shoppers need a visible choice. Sign Customiser does not translate copy outside the customer customiser.

Test before launch

  1. Publish the target customiser language.

  2. On Shopify, test the live Store language route, not only the admin preview.

  3. On Universal, test an explicit target code, a matching browser preference, an unsupported code, and no code.

  4. Create a test product in at least one non-default language and check the cart wording.

  5. Check the selected font’s character coverage and test right-to-left layout separately.

Troubleshooting

  • The default always appears. Publish the target, check the platform signal, remove an invalid override, and check for ambiguous regional variants.

  • The customiser translates but the Shopify theme does not. Translate the surrounding theme and page content in Shopify.

  • The wording is correct but direction is wrong. Follow Use right-to-left languages.

  • Old wording appears. Publish the current draft, then reload.

Need to create or publish the target first? Follow Add, translate, preview and publish a language.