Help Center

Ciwi AI Translator: Shopify Translation Workflow & Credits

Learn how Ciwi AI Translator organizes Shopify translation tasks, language publishing, and translation credits before starting your first workflow.

Ciwi AI Translator is a Shopify localization app for configuring target languages, creating translation tasks, reviewing content, and publishing language versions. Check your available AI translation credits and task estimates before starting a large job.

What the app covers today

  • Language management: add target languages, publish or unpublish them, and turn automatic translation on for supported languages.
  • Translate v4 jobs: choose target languages, choose Shopify content modules, choose an AI model, estimate credits, and create one job per target language.
  • Review workflow: use Manage Translation to inspect and edit translated products, pages, navigation, metafields, theme content, and more.
  • Quality controls: keep brand terms stable with glossary entries and review output before publishing.
  • Storefront localization: configure the language and currency switcher, geolocation behavior, and multi-currency display.
  • Billing and support: check available credits, buy extra credits when needed, and contact support from inside the app.

What content can be translated

The current codebase covers more than flat page copy. Ciwi can work with products, collections, blogs, articles, pages, navigation, filters, shop information, policies, metafields, metaobjects, theme text, email templates, delivery methods, shipping templates, and optional custom Liquid content.

How merchants usually use it

  1. Add a target language on the Language page.
  2. Optionally set glossary terms that should stay fixed.
  3. Open Translate v4 and choose languages, modules, and model.
  4. Review translated content in Manage Translation.
  5. Publish the finished language version for the storefront.

Good to know

The help center content below is aligned with the current app routes and data model. Some older public URLs remain the same for continuity, but the guidance now reflects the actual v4 workflow and billing behavior in code.