inriver CVL Key Translator

When you export from inriver, multi-value and single-value list fields come out as CVL keys — short internal codes like COL_017 or mat-ss316 instead of the human label a buyer would recognize. This tool maps those inriver CVL keys back to their display values so a supplier export becomes readable, mergeable data during onboarding.

What it checks

Paste an inriver export (or a CVL definition file) plus the key-to-value mapping, and the translator will:

• Resolve CVL keys to display values — turn codes such as BRN_044 into Stainless Steel or FIN_matte into Matte, across single-value and multi-value list fields.
• Expand multi-value cells — split delimited key strings (for example key1;key2;key3) and translate each element so a furniture finish list reads Oak, Walnut, Black instead of three opaque codes.
• Flag unmapped keys — surface any key present in the data export but missing from the CVL definition, so you catch dropped or renamed list values before they reach your PIM or storefront.
• Detect orphaned and duplicate values — show CVL entries that no record uses and labels that map to more than one key, both common after years of supplier edits.
• Report language fallbacks — where a CVL value is localized, indicate which locale was matched and where a default language was used instead.
• Output a clean lookup table — download a translated CSV with both the original key and the resolved value, ready for schema mapping into your canonical model.

How inriver CVL keys work

inriver stores controlled vocabularies — CVLs (Customer Value Lists) — as a set of keys, each tied to one or more localized values. Fields of data type CVL reference those keys rather than storing the label inline, which keeps the value list consistent across thousands of records. The trade-off shows up at export time: unless your export job is configured to resolve labels, you get the keys.

That is fine inside inriver, but the moment a distributor receives a supplier’s inriver export — say a CPG vendor sending finishes, an MRO supplier sending material grades, or an industrial brand sending color families — the keys are meaningless without the matching CVL definition. The translator rebuilds the relationship: it reads the key-to-value pairs (single and multi-value), applies them to every referenced field, and produces readable output. This is the same first step Claro’s onboarding pipeline performs before mapping supplier attributes to your schema and resolving records into a single canonical entry.

How to use it

1. 1
   Paste your export
   Drop in the inriver data export containing CVL keys, in CSV or delimited text.
2. 2
   Add the CVL definition
   Paste the key-to-value mapping (the CVL export) so the tool knows what each key means.
3. 3
   Translate and review
   See resolved values inline, with unmapped and duplicate keys flagged for follow-up.
4. 4
   Export the lookup
   Download the translated table to feed your schema-mapping or import step.

Related resources

FAQ