UNECE Rec 20 Unit Code Validator

Paste a column of unit-of-measure codes and this tool checks each one against the UNECE Rec 20 unit codes standard, flags anything that is not a valid common code, and explains what the valid ones mean in plain language. It is built for distributors cleaning supplier feeds before they hit a PIM, ERP, or marketplace mapping.

What it checks

The validator runs each code in your list through a set of structural and reference checks:

• Known code lookup — confirms the code exists in the common UNECE Recommendation 20 unit-of-measure list (for example MTR for metre, KGM for kilogram, LTR for litre, EA/H87 for piece, MTK for square metre, MTQ for cubic metre).
• Format sanity — flags codes that are the wrong length, lowercase, or contain stray spaces, quotes, or trailing characters from a sloppy CSV export.
• Common-vs-uncommon — distinguishes the widely used common codes from rarely seen ones, so you know when a code is technically valid but likely to break a downstream channel.
• Free-text impostors — catches human-readable units like pcs, each, meters, kg, or box that suppliers drop into a code field where a standard code belongs.
• Suggested mapping — where a free-text or near-miss value is recognizable, proposes the matching standard code (for example meters → MTR, pcs → H87).
• Duplicates and blanks — surfaces empty cells and repeated entries so you can quantify how much of the column is actually populated.

How the UNECE Rec 20 unit codes are validated

UNECE Recommendation 20 (“Codes for Units of Measure Used in International Trade”) gives each unit a short alphanumeric code so a quantity can move between systems without ambiguity. A “box of 12” sent as free text means nothing to an ERP; sent as KGM, MTR, or H87 it is unambiguous across languages and platforms. The standard underpins GS1, EDI, and most B2B feed formats, which is why a single bad unit code can silently corrupt pricing, shipping, or pack-size logic.

The validator works by matching each input against a reference set of the common codes and their descriptions, then applying lightweight format rules to catch the typical feed-export errors. A furniture distributor importing dimensions in centimetres, an MRO supplier listing fasteners by the hundred, a CPG vendor selling by the litre, and an industrial cable supplier quoting by the metre all hit the same failure mode: the unit field is a mix of standard codes, local abbreviations, and free text. This tool separates the three.

Validation tells you which codes are wrong; it does not fix the root cause. If your unit field is unreliable across thousands of SKUs, the durable fix is to normalize units as part of enrichment — deriving the correct Rec 20 code from the source attribute and recording where each value came from. That is the kind of canonical, provenance-tracked normalization Claro’s product enrichment layer is built to do at catalog scale.

Related resources

FAQ

What is a UNECE Rec 20 unit code? +

It is a short alphanumeric code defined by UNECE Recommendation 20 that identifies a unit of measure used in international trade — for example MTR (metre), KGM (kilogram), LTR (litre), or H87 (piece). The codes let a quantity move between ERP, PIM, EDI, and marketplace systems without relying on free-text labels that differ by language and vendor.

What is the UNECE code for 'each' or 'piece'? +

The two codes you will see most often for a single sellable item are EA (each) and H87 (piece). Many trading partners and feed formats prefer H87. If a supplier sends pcs, pc, unit, or each as free text, this validator flags it and suggests the standard code so your pack-size and pricing logic stays consistent.

Why does my unit code fail validation even though it looks correct? +

The most common causes are case (mtr instead of MTR), hidden whitespace or quote characters from a CSV export, a local abbreviation in a code field (kg instead of KGM), or a valid but uncommon code that a downstream channel does not accept. The tool labels which of these applies so you know whether to clean the data or map it to a different code.

Is this tool free and does it upload my data? +

Yes, it is free with no login. All checks run locally in your browser, so your pasted or uploaded list never leaves your device and there is no file-size limit imposed by a server. You can run supplier or catalog data through it without a data-sharing review.

How do I fix bad unit codes across a whole catalog? +

For a one-time cleanup, validate, map the flagged values to standard codes, and re-import. For an ongoing feed problem, the lasting fix is to normalize units during enrichment — derive the correct Rec 20 code from the source attribute and record its provenance — so new supplier files are corrected automatically instead of fixed by hand each time.