Section 25 — Storefront: Language & Translation Controls
CatalogPilot supports translation-aware enrichment while preserving strict control over how and when translated content is generated and delivered.
This section explains how language handling works and what merchants should (and should not) expect from translation features.
Core Principle: CatalogPilot Does Not Create Languages
CatalogPilot does not create new languages in your catalog.
Translations are only applied when:
- The language already exists in your eCommerce platform
- Products are already present in that language upstream
- The merchant explicitly enables translation delivery
CatalogPilot enhances existing multilingual catalogs — it does not invent or auto-expand them.
Language Selection Controls
Within Storefront Settings, merchants may see a list of available languages.
These represent:
- Languages already configured in the platform
- Languages detected during catalog synchronization
Selecting a language here:
- Enables enrichment for that language after approval
- Does not trigger enrichment immediately
- Does not create translated products or pages
Languages act as delivery permissions, not generation triggers.
Translation Execution Order
CatalogPilot enforces a strict sequence to prevent drift:
- Primary language enrichment runs first
- Merchant reviews and approves primary language content
- Translation enrichment runs only after approval
- Translated content inherits approved structure and intent
This ensures:
- Translations are anchored to validated source content
- Machine interpretation remains consistent
- Errors do not propagate across languages
Translation Scope & Limitations
Translations apply only to:
- Fields that exist in both languages
- Products that already exist in the platform catalog
- Supported enrichment fields (titles, descriptions, metadata, etc.)
CatalogPilot will not:
- Translate languages that don’t exist
- Generate partial language trees
- Infer or fabricate missing translations
If a product does not exist in a given language upstream, it will be skipped.
Pricing & Billing Behavior
When applicable:
- Translation enrichment is billed at up to 50% of the primary enrichment fee
- Translation charges only apply after approval
- No translation charges occur without explicit merchant action
Exact pricing is always shown before confirmation in batch estimates.
Recommended Best Practice
CatalogPilot recommends:
- Enriching and approving the primary language first
- Enabling translations incrementally
- Reviewing translated content at a glance rather than field-by-field
This maintains speed, consistency, and accuracy across large catalogs.
Key Takeaway
Language controls in CatalogPilot are protective by design.
They ensure that:
- Nothing is translated prematurely
- No language content drifts from approved intent
- Multilingual catalogs scale safely and predictably
CatalogPilot enhances what already exists — and only when you allow it.
