Overview
The Value Mapping module in Supplier Data Manager (SDM) translates supplier-provided attribute values into the accepted option values defined in your system. For example, a supplier might send "Light Blue" or "Duck Blue" for a color field — Value Mapping lets you map those variants to your standardized option, such as "Blue."
Value Mapping applies to select and boolean attribute types only. It also supports multi-select scenarios, including consolidating multiple source values into a single target option.
SDM remembers every mapping you confirm. When the same supplier value appears in future jobs, SDM automatically suggests or applies the previous mapping, keeping your catalog consistent over time.
For the end-user guide to the Value Mapping module, see the dedicated guide.
Interface
In the Value Mapping step of a job, SDM displays a list of select and boolean fields that have unmapped values. By default, only fields with at least one unmapped value are shown. To see all fields, uncheck the Unmapped fields only filter.
When you open a field for editing:
- The available target options from your taxonomy appear on the left.
- The supplier-provided values to be mapped appear on the right.
- Drag a supplier value from the right onto the corresponding target option on the left to create the mapping.
When multiple supplier values are selected, all mapped values remain visible on the right with a blue border.
Configuration
The configuration described here is a reference summary. The API documentation is always authoritative — verify details there before relying on this page.
Root-level parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
keep_unmapped |
boolean | false |
When true, values with no mapping are passed through unchanged. When false, unmapped values are set to null. |
map_empty |
boolean | false |
When true, empty (null) values from the input file are surfaced in the mapping interface and can be mapped to a target option. When false, fields that contain only null values are hidden from the mapping interface. |
block_learning |
boolean | false |
When true, confirmed mappings are not saved to the mapping history. Disable learning when you do not want this job's mappings to influence future suggestions. |
max_requirement_level |
string | required |
Filters which fields are included based on their requirement level. |
Field-level parameters
In addition to the standard field configuration options (fields, groups, include_fields, exclude_fields), each field in the Value Mapping step accepts:
| Parameter | Type | Default | Description |
|---|---|---|---|
max_distance |
integer | 0 |
Maximum fuzzy-match distance used when suggesting target options for a supplier value. A value of 0 disables fuzzy matching. |
Importing value mapping results from a file
You can bulk-import pre-configured mappings by uploading a file directly from the SDM admin. This is useful for bootstrapping mappings or migrating them from an external tool.
To upload a mapping file in SDM admin:
- Navigate to the Value Mapping step configuration in the SDM admin.
- In the Create Value Mapping Results from File section, attach your file.
- Save. SDM processes the file and creates the mapping records.
Supported file formats
SDM accepts Excel (.xlsx), JSON, and CSV files. The file must contain the following columns or keys:
| Field | Required | Description |
|---|---|---|
column |
Yes | The attribute name. |
group |
No | The product family or group. Leave empty if not applicable. |
old |
Yes | The supplier-provided input value to map from. |
new |
Yes | The target option value to map to. |
Column headers must be in lowercase for CSV and Excel files. For JSON files, provide an array of objects with the same keys.
CSV/Excel example:
| column | group | old | new |
|---|---|---|---|
| color | Light Blue | Blue | |
| color | shirts | Duck Blue | Blue |
| gender | Man | Unisex |
JSON example:
[
{"column": "color", "old": "Light Blue", "new": "Blue"},
{"column": "color", "group": "shirts", "old": "Duck Blue", "new": "Blue"},
{"column": "gender", "old": "Man", "new": "Unisex"}
]
If a mapping already exists, the import skips it rather than creating a duplicate.
How SDM learns from mappings
Each time a mapping is confirmed in a job, SDM increments an internal usage count for that mapping pair. When a new job contains the same supplier value for the same attribute, SDM uses this history to suggest the most frequently used target option automatically.
Setting block_learning: true disables this for a specific step, so confirmed mappings from that job are not saved to the history.