Shopify Translations

The Translations page controls storefront text for Retail Cloud Connect Shopify App Blocks. Use it for Online Store 2.0 themes that install the Search Results, Product Grid, Recommendations AI, and Document Search App Blocks from the Shopify theme editor.

For Online Store 2.0 App Block installs, do not add a custom window.Nimstrata.translations object for normal translation work. The app saves translations into Shopify metafields and the App Blocks inject the right language data before the storefront JavaScript starts.

What the App Handles

Use the Translations page to edit:

• App Block Translations: shopper-facing search, collection, recommendation, product-card, document-search, and local-inventory copy such as Local Store, Change Store, and Pick up in store
• Up to five Dynamic Autocomplete example queries configured in Autocomplete settings
• Filter Display Labels: filter headings such as Brand, Color, Size, Price, and custom attribute labels
• Product card button text from every enabled Search, Dynamic Autocomplete, and Recommendations card in Production and named profiles

Use Filter Value Translations from the Filters & Data page to edit:

• Raw filter values
• Merged filter labels
• Color family values

Language Selection

The Retail Cloud Connect Shopify App reads published shop locales from Shopify. The main Translations page includes the primary locale and published secondary locales.

Primary-locale display labels are the default labels used by Filters & Data. Editing a primary-locale filter display label updates the underlying filter display name.

Secondary-locale display labels override the default label for that storefront language.

Product Titles and Descriptions

Product content translation is disabled by default. For each secondary language, merchants can opt in and choose one Shopify source for the product title and one for the product description:

• Shopify's translated product field
• A product metafield

The app imports only the selected source for each field. It does not substitute another translated field when the selected value is blank. When Shopify has more than one regional locale for the same language, such as French for Canada and France, the exact Shopify locale must also be selected.

Translated Google Cloud attributes use the base language. For example, fr-CA produces rcc_fr_title and rcc_fr_description.

These attributes are indexed and searchable as text. They are not returned in Google results or used for dynamic facets, exact matching, or Recommendations AI filtering, and the import re-applies these controls on every run.

After changing product content translation settings, run a full import. Live product sync applies the same source rules, while the full import is the guaranteed reconciliation path for native Shopify translation changes.

Search Query Pluralization

Automatically pluralize Spanish and French search queries is a billing-plan feature (AUTOMATIC_QUERY_PLURALIZATION). In production it appears only for plans that include the feature; Platform grants it outside production. The card is shown when the shop publishes a secondary Spanish or French locale, or when the setting is already enabled. If the plan later loses the feature, an enabled setting stays visible so it can be turned off, but it cannot be turned back on.

When enabled, a single-word search from a Spanish or French storefront is sent to AI Commerce Search as its plural (for example, camisa → camisas, robe → robes). It only applies when the catalog language is English, and queries are not translated. Phrases, and searches from other languages, are unchanged. Shoppers and search analytics still see the original query.

The setting applies to the whole shop, not the language selected on the page, and is stored as the AUTOMATIC_QUERY_PLURALIZATION import setting with empty data. The storefront API caches it for up to 10 minutes. Brand names, product names, English words and other proper nouns can also be pluralized.

AI Translation

AI translation actions are available for secondary locales. The app only fills blank rows by default and keeps existing manual translations unless a row is explicitly targeted.

Primary-locale text is edited manually because it is the source copy for the store.

Storefront Behavior

Search and collection App Blocks load translations in this order:

1. Shipped theme-extension locale defaults
2. Merchant-edited App Block Translations
3. Filter display-label and filter-value translations

Filter-specific translations win over generic storefront copy when both exist.

Online Store 1.0 or Manual Theme Installs

For an Online Store 1.0 or manual asset install, enable Enable translations on 1.0 themes in the Core Components App Embed. This outputs the translated storefront copy and merchant-configured filter translations without requiring search or collection App Blocks.

For the primary storefront locale, the App Embed also exposes the default filter display names configured in Filters & Data. Secondary storefront locales continue to use their language-specific filter display-label overrides.

Only define window.Nimstrata.translations manually when the store cannot use the Core Components App Embed. Define it before loading the Nimstrata storefront bundle:

window.Nimstrata = window.Nimstrata || {};
window.Nimstrata.translations = window.Nimstrata.translations || {};
window.Nimstrata.translations.default = {
  'search.placeholder': 'Search',
  'toolbar.refine_filters': 'Refine Filters',
  brands: 'Brand',
};

window.Nimstrata.translations.filters = {
  sizes: {
    sizes: 'Size',
    M: 'Medium',
    L: 'Large',
  },
};

For the full manual property reference, see Window Nimstrata Properties.