Localization & classification
Translate and classify for every market
Two things that look like admin work and are actually market access. A catalog only in German is invisible to the Austrian subsidiary's Polish buyer. A catalog without eCl@ss classification cannot be loaded into most large customers' procurement systems at all. This area covers the translation workflow and the classification standards — both of which are where B2B catalog projects go over budget.
Understand
- How catalog translation works — Localizable attributes, fallback, workflow, and what to translate first.
- Classification standards — eCl@ss, ETIM, UNSPSC, and why your customers care.
- Catalog exchange formats — BMEcat, Datanorm, and the customer-specific Excel.
Set up
- Add a language — Locale, fallback, which attributes, who translates.
- Map attributes to a classification — Your attributes → eCl@ss features.
- Catalog export profiles — BMEcat, Datanorm, Excel — per customer.
Work with it
- Translate the catalog — The translator's workflow.
- Classify products — Assign classes and fill features.
- Export a catalog for a customer — Run, validate, deliver.
Keep it healthy
- Translation quality — Untranslated, machine-only, stale after source change.
- Classification version updates — eCl@ss releases twice a year. What changes.