Login

Discovery & Personalisation

Content transformation & localisation

Brand / region / language / tax adaptation

Standard(per-market config)

In one sentence

What it is

Content transformation and localisation adapt one master product record for each brand, region, language and tax treatment, so a single source of truth still reads as genuinely local everywhere it sells.

How it works

What it does

A master product record — description, attributes, imagery, pricing — is transformed per market as it's served: translated copy for the language, tax-inclusive or tax-exclusive pricing depending on the region's convention, brand-specific tone or formatting where a group operates multiple brands from shared data, and unit conversions where needed. This happens per-market configuration rather than through duplicated content, so a correction to the master record flows through every transformed version rather than requiring a re-translation or re-entry each time. The brand controls which markets get which treatment and can override at the market level where a genuine local difference — not just a translation — is needed.

The problem it solves

Why it matters

For the brand

Serving twenty markets from twenty separately maintained copies of the same content means every product update has to be repeated twenty times, and inevitably some markets fall behind or get missed entirely.

For their customers

A page that's obviously machine-translated, prices shown in the wrong tax convention for their market, or content that clearly wasn't written for their country reads as an afterthought — and shoppers buy less from sites that feel foreign.

For shoppers

How it benefits shoppers

  • Product pages that read naturally in their own language, not as a literal translation.
  • Prices displayed the way their market expects — with or without tax shown, in their currency.
  • Corrections and new information reach every market at the same time, not weeks apart.
  • A consistent brand experience that still feels locally made.

For the brand

How it benefits the brand

  • One master record serves every market without re-entry

    Localisation effort per market

  • Corrections propagate to every language and region at once

    Time to correct content across markets

  • New markets launch on existing content faster

    Time to launch a new market

  • Consistent tax and pricing presentation reduces checkout confusion

    Checkout abandonment by market

  • Local nuance can still be applied where genuinely needed

    Market-specific override usage

In practice

What it looks like

  1. 1

    A product description is updated once in the master record.

  2. 2

    The transformation layer produces the translated, market-appropriate version for each active region automatically.

  3. 3

    Tax-inclusive pricing is shown in markets that expect it, tax-exclusive in those that don't, from the same base price.

  4. 4

    A market team applies a local override for a phrase that needs different framing culturally, without touching the master content.

Where it lands hardest

Strong use cases by industry vertical

  • Health & nutrition

    Permitted health claims differ by market, so localisation must go beyond translation into what can legally be said where — this is where the override capability matters most.

  • Beauty & personal care

    Shade and skin-tone language varies meaningfully across markets; direct translation alone often gets this wrong.

  • Food, drink & FMCG

    Nutritional units and legally mandated wording differ by country, making per-market transformation a compliance necessity, not a nicety.

  • Pet care

    Feeding guidance units (metric vs imperial) and terminology shift by market, and the accuracy of that conversion genuinely matters.

  • Fashion & apparel

    Size systems (UK/EU/US) need market-correct conversion on the same base product, which localisation handles as configuration rather than duplication.

  • Luxury & premium

    Tone and register matter more than volume here — editorial content often needs careful market-level review rather than pure automation.

Common questions & objections

What clients usually ask

Why the platform version wins

This sits directly on the central catalogue rather than as a separate translation management tool, so localisation stays in step with product data instead of drifting out of sync with it.