Request access
Menu

Translate your entire Magento store without breaking a single layout.

A Magento module sends your content to our translation engine. CMS pages, PageBuilder layouts, products, categories, attributes, blogs and menus come back translated, with markup, widgets and links intact, ready to save per store view.

Request access Read the docs
Store view

Storefront, Default Store View

New

Merino trail hoodie

€129.00

Warm on the climb, dry on the way down. 100% merino wool.

Colour: fjord blue

Size guide

Add to cart

What the AI model is sent

<div data-content-type="row">
  <span class="product-label">⟦1⟧</span>
  <h2 class="product-name">⟦2⟧</h2>
  <p>⟦3⟧ <strong>⟦4⟧</strong></p>
  <p class="swatch-label">⟦5⟧</p>
  <a href="/en/size-guide">⟦6⟧</a>
  {{widget type="Magento\Cms\Block\Widget\Block" block_id="12"}}
  <button class="action tocart">⟦7⟧</button>
</div>

7 text parts in the source

8 tags in, 8 tags out

Link /en/size-guide

One PageBuilder product block, five store views. The words change; the markup, the widget and the price never pass through the model, and the size-guide link follows the store view.

From install to a translated store view in three steps

The module stays light: it loads your content, saves the result and runs the queue. Parsing, prompts, retries and link rewriting run on our side, so improvements reach you without a module upgrade.

  1. Install the module

    Download it from your dashboard, unzip it at the Magento root and run setup:upgrade. Translate buttons appear on pages, blocks, products and categories.

  2. Paste your API key

    Under Stores, Configuration, BrassDev, Translator. Each key is bound to your store’s domain, so it won’t work anywhere else.

  3. Translate

    Choose target store views and fields, then pick how the work should run.

Five ways to run a translation

Translate now
One page, block, product or category, translated and saved while you wait.
Schedule
Add it to the queue. The module’s cron works through the queue in the background.
Pre-translate for review
Translations wait in a review grid, source beside translation. Edit, apply or reject each store view before anything goes live.
Bulk translate
Every CMS page, product, category or attribute of one type, queued in a single submit. Made for launching a new store view.
Automatic crons
Nightly runs find products and categories with missing translations and fill only the gaps. Existing translations are never overwritten.

Everything a store view needs, not just product names

Core Magento content and the extensions most stores run, translated from the same admin screens your team already uses.

Content

  • CMS pages

    Title, content, heading and meta fields

  • CMS blocks

    Footer blocks, banners, promos

  • PageBuilder layouts

    Rows, tabs, sliders, banners and buttons, including text stored inside JSON settings. Magezon layouts too.

Catalog

  • Products

    Name, descriptions, meta fields and custom options

  • Categories

    Name, description and meta fields

  • Attributes

    Frontend labels, option values and swatches, Amasty ShopBy filter tooltips

Extensions

  • Amasty Blog

    Posts, categories, tags and authors

  • Amasty Product Tabs and Labels

    Saved as a per-store copy

  • Snowdog Menu

    Node names, descriptions and image alt text, with custom URLs localised

Built so a bad translation can’t break your store

Language models are good with words and careless with markup. So the model never gets your markup.

  • Placeholders, not promises

    Text is lifted out and replaced with numbered tokens before anything reaches the model. Scripts, styles, URLs, widget directives and PageBuilder settings stay on our side.

    <a href="…">⟦6⟧</a>

  • A structure check on every fragment

    Each translated part is compared tag for tag with the source. If a tag went missing or moved, the translation is rejected.

    8 tags in, 8 tags out

  • Nothing half-saved

    A field that fails is never written. Your store keeps what it had, and the reason appears in your usage log.

    title saved
    content left unchanged

  • Links follow the store view

    Internal links get the target store’s code, and your own replacements are applied, so German pages link to German pages.

    /en/size-guide
    /de/size-guide

  • Multi-domain aware

    Running one domain per store view? Links to your own domains are re-anchored to the target store’s domain.

    shop.co.uk/sale
    shop.de/sale

A monthly plan with a clear credit allowance

Credits follow the real cost of the AI model, so you always know what a month of translation costs. A typical product uses 10–40 credits per language.

Compare plans and how credits work

Prices in euros, excluding VAT.

Questions merchants ask first

Do I need my own OpenAI or Anthropic account?

No. The AI model is part of your plan, and its cost is covered by your monthly credits. You only need the Magento module and an API key from us.

Does it work with Hyvä, Luma or a headless storefront?

Yes. Translation happens on content in the Magento admin, so your storefront theme doesn’t matter.

What happens when a translation fails?

The failed field is not saved, so your store keeps its current content. Fields that succeeded are saved as usual, and your dashboard shows what failed and why.

Can someone review translations before they go live?

Yes. Use Pre-translate: translations wait in a review grid where you can edit, apply or reject them per store view.

Is our content stored or used to train models?

We don’t store the content of your pages; we keep request metadata such as time, size, languages and token counts for billing. Our AI providers’ API terms exclude training on API data.

Can we use it on staging as well as production?

Yes. Each API key is bound to one domain (wildcards like *.example.com work), and plans include more than one key. All keys draw from the same monthly credits.

What happens when we run out of credits?

By default, extra usage is billed per 1,000 credits at your plan’s rate. If you prefer a hard stop, we switch overage off for your account and requests are refused until the next month.

Tell us about your store. We’ll set up your account.

There’s no self-signup. Send us your store URL and the languages you need, and our team creates your account and first API key.

Request access

or write to emilsb+salesemail@scandiweb.com