EN
E-Commerce Nov 19, 2026

Multi-Market Product Data: What to Localize and What to Keep Global

Multi-Market Product Data: What to Localize and What to Keep Global

Time to read: 11 minutes

Content

  1. Why translated stores still publish wrong product facts
  2. Four classes: global, translatable, market-specific and channel-specific
  3. The attribute localization matrix
  4. Mirror the classes in platform scopes and the PIM
  5. Translation workflow: source language, machine translation, review and glossaries
  6. Market rules that create required fields
  7. Variants and SKUs per market: when it is not the same product
  8. Publication checks and a new-market readiness report
  9. Exceptions
  10. Test your model
  11. Your next step
  12. FAQ
Bookmark

Product data localization starts with one decision per attribute, not with translation. Before a product publishes in a new country, put every attribute into one of four classes:

Then mirror the classes in your platform's scopes and in your PIM, and block publication in a market, and only in that market, when one of its required fields is missing. The classes also settle approvals: the product-data owner approves changes to global facts, the content lead approves translations, the market owner approves market data (with compliance for legal and safety texts), and the channel manager approves channel data.

Payments, delivery and returns are covered in launching ecommerce in a new country; this guide, for PIM and catalog owners, stays with the product data model.

Why translated stores still publish wrong product facts

A common error is a fact edited in the wrong place, not a bad translation. Someone copies a product into a new language, translates the text and, while the record is open, "corrects" a dimension or a material. The next import overwrites one language and not the other, and two countries now disagree about the same physical product.

Illustrative example (fictional): a German outdoor-furniture maker sells through Shopware 6, with Akeneo as its PIM, and is adding France and the Netherlands. Its old export carried 64 attributes per product, and 9 of them were edited per country in the shop. As a result, dimensions differed between the German pages and the French pages already drafted in the shop for 310 SKUs. Nobody had decided that dimensions are global, so nothing stopped the edits.

The fix is a rule that says which attributes may differ by market, enforced by the systems.

Four classes: global, translatable, market-specific and channel-specific

Four attribute classes and a per-market publication gate ERP, PIM and DAM feed one step: classify each attribute once. Each attribute goes into one of four classes. 1, global: GTIN, MPN, dimensions, materials and images, global scope locked to the source system. 2, translatable: name, description, care text and alt text, store view or language scope. 3, market-specific: price, tax, unit-price base and safety text, website or market scope. 4, channel-specific: marketplace title and feed category, channel or feed mapping. A gate then asks whether the market's required fields are complete. Yes: publish there. No: block there only. ERP PIM DAM Classify each attribute once 1. Global: same everywhere GTIN, MPN, dimensions, materials, images Scope: global, locked to the source system 2. Translatable: one source Name, description, care text, alt text Scope: store view or language 3. Market-specific: market owner Price, tax, unit-price base, safety text Scope: website or market 4. Channel-specific: channel owner Marketplace title, feed category Scope: channel or feed mapping Gate: market fields complete? Yes: publish there No: block there only
ERP, PIM and DAM supply the data. Each attribute gets one class and one platform scope, and a per-market gate publishes a product only where that market's required fields are complete.

Global attributes describe the physical product and its identity: SKU, GTIN, MPN, dimensions, weight, materials, specs and product images. Option values such as a color can stay global while their labels are translated. Identifiers stay global for a reason beyond the store: GS1's GTIN Management Standard requires a new GTIN for a product that is new to the market, and its rule list covers product changes such as declared net content, dimensions or gross weight and the primary brand. Translating a listing is not on that list.

Translatable attributes say the same thing in another language: name, description, care text, image alt text. Each has one source language and one approved translation per target language.

Market-specific attributes may differ between countries that share a language: price, tax class, availability, unit-price base quantity, safety warnings and regulated claims. Each needs a named market owner.

Channel-specific attributes exist because a channel asks for them: a marketplace title with its own length limit, a shopping-feed category, a shorter text for an app.

The attribute localization matrix

Fill one row per attribute with the people who own the data. Each row's platform scope follows its class, as mapped in the next section. This version is filled for the fictional furniture maker; your rows will differ.

AttributeClassSource → ownerAkeneo settingValidation ruleBlocks publication in
SKUGlobalERP → ERP ownerIdentifierUnique, matches ERPAll markets
GTINGlobalERP → product-data ownerIdentifier, read-only13 digitsAll markets
MPN / model numberGlobalPIM → product-data ownerNo value per locale or channelPresentNone
DimensionsGlobalPIM → product-data ownerRead-onlyNumeric, unit setAll markets
WeightGlobalERP → logisticsRead-onlyNumericAll markets
MaterialGlobal valuePIM → product-data ownerSelect, option labels translatedValue from listNone
ColorGlobal valuePIM → product-data ownerSelect, option labels translatedValue from listNone
Product imagesGlobalDAM → content leadShared assetAt least one imageAll markets
Manufacturer name and contactGlobalPIM → complianceNo value per locale or channelPresent; EU responsible person if the manufacturer is outside the EUAll EU markets
Product nameTranslatablePIM → content leadValue per localePresent, translation approvedMarkets of that locale
Long descriptionTranslatablePIM → content leadValue per localePresent, translation approvedMarkets of that locale
Care instructionsTranslatablePIM → content leadValue per localePresentNone
PriceMarket-specificERP price list → market ownerNot in the PIMPresent, above zeroThat market
Tax classMarket-specificERP → financeNot in the PIMRate set for the countryThat market
Unit-price base quantityMarket-specificPIM → market ownerValue per channelPresent where unit pricing appliesThat market
AvailabilityMarket-specificERP → market ownerNot in the PIMStock source mappedThat market
Safety warningsMarket-specificPIM → complianceValue per locale, approval statusRequired language, approvedThat market
Assembly guide (PDF)Market-specificDAM → complianceAsset per localeFile in the required languageThat market
Marketplace titleChannel-specificPIM → channel managerValue per channelWithin the channel's length limitThat channel
Feed categoryChannel-specificPIM → channel managerValue per channelMapped to the feed taxonomyThat feed

How to use it:

  1. Export your attribute list and start with the 20 attributes your products use most.
  2. Assign one class per attribute. If a customer in another country would expect a different value for the same physical product, it is not global.
  3. Name one owner per attribute; the class decides who approves a change.
  4. Write each validation rule and where it blocks publication.
  5. Lock global fields wherever they are edited today. The furniture maker made dimensions, materials and GTIN read-only in the PIM. In Akeneo, a read-only attribute "will only be updated through imports, API or rules"; the help center lists the property for the Enterprise Edition only.

Classification is easier on a consistent catalog. On a BigCommerce catalog project, Dinarys reviewed, updated or downloaded data on over 137,000 products and "had to run some scripts and workarounds to make the data consistent", with AI-assisted categorization. That was catalog cleanup, not localization, but the order of work carries over: make values consistent, then classify. For the wider rulebook, see our guide to PIM practices.

Mirror the classes in platform scopes and the PIM

A class holds only if the systems enforce it: map each class to the narrowest scope that allows the variation it needs.

ClassAkeneoAdobe CommerceShopifyShopware 6
GlobalNo value per locale or channelAttribute scope: GlobalProduct field, not translated or adaptedDefault language only; left untranslated elsewhere
TranslatableValue per localeStore View scope, one store view per languageTranslations (Translate & Adapt, CSV or an app)Translation per language
Market-specificValue per channel, or locale specificWebsite scope; Catalog Price Scope set to WebsiteMarket catalog for products and prices; market adaptationSales channel: products, currencies, countries, domains
Channel-specificValue per channelFeed or connector mappingProduct made available to the sales channelProduct comparison sales channel or connector

Behind the table: Adobe describes store view scope as "typically used to support multiple languages" and says "Commerce does not allow setting a product price for each store", only per website. Shopify catalogs "control which products are available in each market and at what price". Akeneo's "locale specific" property covers cases such as "a Canadian tax only for Canada". In Pimcore, translatable attributes go into localized fields with mandatory languages.

Watch fallbacks. Shopify displays default-language content when a translation is missing; Shopware shows the inherited language's content for untranslated fields; Pimcore checks fallback languages. A fallback hides a missing description from shoppers, so the gate, not the storefront, must catch it; for a safety warning a fallback is never acceptable, which is why warnings are market-specific with a blocking rule rather than merely translatable.

A fallback is not a passWhy a language fallback is not a pass: platforms display another language when a translation is missing, so the per-market gate must block a locale without approved text, and safety warnings never fall back.A fallback is nota passThe gate must catch what fallbacks hidePlatforms fall back fordisplayShopify shows default-languagecontent, Shopware the inheritedlanguage, Pimcore checks fallbacklanguagesShoppers see no gapA fallback hides a missingdescription from shoppersThe gate blocks that marketA locale without an approved name ordescription blocks the marketSafety warnings never fallbackMarket-specific with a blockingrule, not merely translatable

Translation workflow: source language, machine translation, review and glossaries

In the example, French and Dutch names and descriptions are machine translated, then reviewed; assembly warnings never publish from machine output and pass a legal check.

Market rules that create required fields

Unit pricing in the EU. Directive 98/6/EC requires the selling price and the unit price for products offered by traders to consumers. The unit price is per kilogram, liter, meter, square meter or cubic meter, "or a different single unit of quantity which is widely and customarily used in the Member State concerned", and member states may waive it where it "would not be useful". So the net quantity is a global fact, while whether unit pricing applies and its base unit are market-specific fields.

Safety information. Under the General Product Safety Regulation (EU) 2023/988, Article 19, an online offer must show at least the manufacturer's name and contact details, the EU responsible person where the manufacturer is outside the EU, information identifying the product "including a picture of it, its type and any other product identifier", and any warning or safety information "in a language which can be easily understood by consumers, as determined by the Member State in which the product is made available on the market". The manufacturer and identification fields are global (the matrix's manufacturer row; the responsible person applies only when the manufacturer is outside the EU); the language of the warnings is set per member state.

Category law. Food, cosmetics and electrical goods carry their own labeling rules. Those attributes need a regulatory reviewer, not a translator.

Variants and SKUs per market: when it is not the same product

If a market needs a physically different product, such as another plug, voltage, sizing standard or net content, create a separate SKU rather than a market-specific attribute, and assign its GTIN under GS1's rules. GS1 adds that "local, national or regional regulations may require more frequent GTIN changes".

If the product is the same and only the assortment differs, availability is market data. The Undrgoods project involved three regional stores for the UAE, Saudi Arabia and Kuwait, with regional payments, "advanced inventory synchronization across all 3 regional stores" and a custom bundle management solution with "automatic inventory adjustments when bundle components change". The case shows inventory synchronized across three regional stores; it does not describe per-market assortment rules.

Same product or a separate SKU?How to decide between market data and a new SKU: a physically different product gets a separate SKU and its own GTIN, a different assortment is availability data, and a translation needs no new GTIN.Same productor a separate SKU?When it is not the same productPhysically different for amarketAnother plug, voltage, sizingstandard or net content: create aseparate SKUAssign its GTIN under GS1'srulesLocal, national or regionalregulations may require morefrequent GTIN changesSame product, differentassortmentAvailability is market dataTranslated onlyA translation needs no new GTIN

On myfelt's multilingual Magento to Shopify migration, Dinarys transferred a multilingual catalog and built a PDF generator that captures a customer's "color, size, design, and material choices" for production units. A downstream process like that reads option values, which is a reason to keep option codes global; the case page does not describe how option values were modeled.

Publication checks and a new-market readiness report

Run the gate per market and per SKU: if every blocking rule passes, the product publishes there; if not, it stays unpublished in that market only, with the reason recorded. Akeneo's completeness covers part of this: it "is defined by a family, a locale, and a channel", and a product is complete when all its required attributes have a value. Approval status and legal checks need their own rules in the export or a pre-publish job.

Readiness report for the fictional maker, after the matrix:

MarketActive SKUsPassingBlockedBlocking reason
Germany1,2001,200 (all)0None
France1,2001,060 (88%)140French safety text missing
Netherlands1,2001,163 (97%)37Dutch description not approved

The 140 SKUs stay live in Germany and the Netherlands while compliance completes the French texts. Run the check at every release, not only at launch: on Flash Style's Magento 2 platform, with Czech and English content and CZK and EUR pricing, every sprint's QA included "Multi-language content verification". New SKUs that wait in this queue are covered in why new products wait weeks before going live; if missing fields start in supplier files, fix them upstream with catalog and product data management.

Exceptions

Test your model

Classify your 20 most-used attributes, map each to a platform scope, and run one market's readiness check. It passes when every attribute has one class and one owner, no global attribute is editable at a store view or language level, the check lists blocked SKUs with reasons, and blocking one market leaves the others live.

The matrix organizes ownership and checks; it does not replace your compliance review, and the Dinarys cases above show multilingual and multi-store catalog work, not regulatory sign-off.

Your next step

Fill the matrix for one target market and run its readiness check on a sample of SKUs. If you want a second pair of hands on the classification, the scopes or the publication gate, talk to us about PIM consulting and implementation.

FAQ

Should product names be translated or kept global?

Translated from one source language, with an approval status per locale.

Is price a product attribute or market data?

Market data, owned by each market through the platform's market or website scope.

What happens when a translation is missing?

Most platforms fall back to another language for display. Treat that as a safety net, not a pass: the gate blocks a market whose locale lacks an approved name or description, and a safety warning never falls back.

Does a translated product need a new GTIN?

Not for the translation. GS1 ties new GTINs to new products and to listed product changes, though local regulations may require more frequent changes.

Lassen Sie Profis Ihre Herausforderung meistern

Unsere zertifizierten Spezialisten finden die optimale Lösung für Ihr Unternehmen.

Bitte einen gültigen Namen eingeben
Bitte geben Sie ein gültiges Unternehmen ein
Bitte geben Sie eine gültige Telefonnummer an
Bitte geben Sie eine gültige E-Mail-Adresse ein
Kurze Botschaft

    Ihre Nachricht wurde erfolgreich verschickt. Wir melden uns in Kürze! Success icon