A Distributor Requested ETIM Data. What Should You Do Next?

If a distributor asks for ETIM data, do not start by opening a blank spreadsheet and guessing class codes. First confirm what they need: ETIM release, target country or market, exchange format, product range, mandatory feature expectations, media requirements, sample-file process, and deadline. Then build a phased delivery plan: classify a representative subset, validate the export, fix the source-data gaps, and only then scale to the full range. The work is part classification, part supplier-data cleanup, and part change control.

This article is for manufacturers and suppliers receiving that request for the first time. The distributor may be trying to load your range into a technical catalog, prepare a BMEcat feed, satisfy a customer portal, or improve webshop filters. In each case, the practical question is the same: how do you turn scattered PDFs, spreadsheets, PIM fields, and product images into structured ETIM classes and feature values without inventing data?

Ask these questions before you classify anything

The fastest successful projects begin with these answers. The slowest ones classify hundreds of products against the wrong release and then redo the work.

What the distributor probably expects

A credible ETIM delivery usually includes more than an EC class code. Expect the distributor to look for:

• Class assignment at a valid ETIM product class, not a broad family label.
• Feature completion for the required features in that class, using the expected value type, unit, or controlled value where applicable.
• Source consistency between feature values, datasheets, product titles, media, and any existing PIM fields.
• Exchange-format validity if the output is BMEcat, ETIM xChange, or a portal template.
• Data-quality validation before import, including missing mandatory values and incompatible units.
• Media and document alignment so images, datasheets, manuals, and certificates attach to the same product identity.
• Ongoing maintenance when ETIM releases, product generations, or distributor requirements change.

For background on the model itself, start with ETIM in BMEcat and the ETIM classification workflow.

A practical phased delivery plan

1. 1
   Collect the source evidence

   Gather PIM exports, ERP item masters, supplier spreadsheets, product datasheets, installation manuals, images, and any existing BMEcat or XML files. Label every source by date and product range. This becomes the evidence base for classification and feature values.

2. 2
   Resolve product identity before feature mapping

   Confirm which records represent the same sellable product. Do not classify duplicate records separately, and do not attach one datasheet to every variant in a family without checking MPN, wattage, size, voltage, or packaging differences. Claro’s catalog matching use case is directly relevant here.

3. 3
   Classify a representative sample

   Choose a sample that covers simple products, edge cases, and high-volume items. Assign candidate ETIM classes and record why each class was chosen. If a product only maps to a parent concept or a neighboring class, mark it for review rather than forcing it.

4. 4
   Populate features from sourced attributes

   Extract values from existing fields and documents, normalize units, and keep provenance for every populated feature. If the source says “230 V” in a datasheet, store the source; if a value is inferred from a product family, label it as lower confidence.

5. 5
   Validate the sample file with the distributor

   Send a small export in the target format and ask for validation feedback before scaling. Use Validate an ETIM XML Export if the output is XML-based, and distinguish schema validity from semantic approval.

6. 6
   Scale in batches and keep exceptions visible

   Process the full range by family or category, not one giant batch. Route missing values, conflicting sources, and uncertain class assignments to reviewers. Avoid hiding exceptions in free-text notes that cannot be validated later.

7. 7
   Plan release maintenance

   Record ETIM version, mapping date, reviewer, and source evidence. When ETIM, ECLASS, or distributor requirements change, you need to know which records are affected and why the previous decision was made.

What not to promise

Do not promise:

• complete ETIM coverage before you know the requested release and mandatory feature set;
• production-ready BMEcat or ETIM xChange before a sample file passes validation;
• feature values that have no source evidence;
• one-to-one reuse of an ECLASS or internal taxonomy mapping without review;
• zero human review for ambiguous products or source conflicts;
• permanent completion without a maintenance process for new products and release changes.

Authoritative references to keep nearby

Use the recipient’s instructions as the final acceptance rule, but keep the standards context explicit. ETIM International’s model information describes the classification model entities as product groups, product classes, synonyms, features, values, and units. The ETIM Viewer is useful for checking class details, features, values, synonyms, and version differences during review. If the distributor asks for BMEcat, validate the exchange container separately from the ETIM class-and-feature content.

A supplier’s internal cleanup work should connect to the same operating model Claro uses for supplier onboarding, product classification, catalog matching, and product deduplication: resolve identity first, classify once, keep source evidence, and avoid duplicating effort across equivalent records.

Where Claro fits

Claro is not a PIM replacement. It is the upstream product-data layer that helps teams prepare trusted records for the systems they already run. For an ETIM request, Claro can help with:

This keeps the workflow grounded: automate extraction, matching, normalization, provenance, confidence, review queues, and write-back; keep specialist or commercial decisions with the people accountable for the catalog.

Related

FAQ