Attribute mapping

Product attribute mapping: turning every supplier's columns into one model.

Attribute mapping is the work that makes a multi-supplier catalog possible. Done once per supplier and reused, it takes minutes per delivery. Redone by hand each time, it is the reason catalog teams never get ahead.

Build reusable mappings See supplier onboarding

Once per source

A mapping belongs to the supplier, not to the file.

Typed targets

Units and value lists live on the attribute.

Reversible

The original supplier value stays attached to the record.

The four transforms

Almost every mapping is one of four operations.

Naming maps a supplier column heading to your attribute. Typing turns a text value into the type your attribute expects, such as a number with a unit or a value from a controlled list. Unit conversion brings a value into your canonical unit. Value normalization maps a supplier's wording onto your permitted value, so that stainless, stainless steel and SS become one value.

Recognising which of the four you are performing matters, because they fail differently. A naming error is obvious. A unit error is invisible until a product is physically wrong. A value normalization error quietly fragments your filters until nothing groups properly.

Transform	Example	How it fails
Naming	Supplier column Artikelgewicht to attribute Weight	Obvious, caught immediately
Typing	Text 12,5 to number 12.5	Silent locale errors on decimal separators
Unit conversion	Inches to millimetres	Invisible until a physical mismatch
Value normalization	SS and stainless to Stainless steel	Filters fragment, nothing groups

Design

Map to the model, never to the channel.

The tempting shortcut is to map a supplier file straight to the shape a channel needs, because that is the immediate deliverable. It works until there are two channels, at which point you have two mappings per supplier and a matrix that grows by multiplication rather than addition.

Map every supplier into one canonical model, then map that model out to each channel once. With ten suppliers and four channels that is fourteen mappings instead of forty, and a change to a channel's requirements is one edit rather than ten.

Inbound mappings: one per supplier, into the canonical model
Outbound mappings: one per channel, out of the canonical model
No supplier mapped directly to a channel, ever
Canonical units and value lists defined on the attribute itself

Reuse

A mapping is an asset, and it belongs to the supplier.

Suppliers send the same shape repeatedly. If the mapping is stored against the supplier rather than rebuilt for each file, the second delivery costs almost nothing and the tenth costs the same as the second. That is the entire economic difference between a catalog team that scales and one that does not.

Mappings also need versions. When a supplier adds a column or renames one, you want to see that the mapping changed, when, and who approved it, because a silent mapping change is indistinguishable from a data change when somebody later asks why a value moved.

Stored against the supplier and reapplied to each delivery
New or missing columns reported rather than ignored
Versioned, so a mapping change is visible in history
Previewed against the file before the import is accepted

Evidence

Keep the value the supplier sent, next to the value you approved.

Mapping is lossy by design: you are choosing a canonical form. Discarding the original makes disputes unresolvable, because there is no way to tell whether a wrong value was wrong at source or broken by the mapping. Keeping the source observation makes that a five-minute check.

Nexodo keeps source observations separate from the approved canonical record for exactly this reason, and shows a reviewer the competing values from different suppliers side by side. Reusable mappings for CSV and connected Google Sheets are the mechanism, and the import preview is where a mapping problem is caught before it reaches the catalog.

Source observation retained per supplier and per delivery
Approved canonical value separate from what arrived
Conflicts between sources surfaced for a decision
Batch history and rollback when a mapping was wrong

Frequently asked questions

Clear answers before you evaluate a PIM.

How do I handle a supplier that changes its columns every time?

Map on stable identifiers where the file offers any, and configure the import to report unrecognised and missing columns as exceptions rather than skipping them. A file whose shape changed should stop for review, not import quietly.

Should units be converted at import or at publish?

At import. Store one canonical unit per attribute so that comparisons, filters and quality rules all operate on the same scale. Convert outward at publish time if a channel needs a different unit.

What about attributes only one supplier provides?

Add them to the model if they are genuinely useful for that product type, and accept that completeness for that attribute will be partial. Do not create a supplier-specific column in the canonical model, because it will never be filled by anyone else.

How do I know a mapping is right?

Preview it against a real file and inspect the rows it changes, not the rows it leaves alone. Check a sample of numeric attributes for unit errors specifically, since those are the ones no validation rule will catch for you.

Continue your product data research

Supplier product data onboarding

Test Nexodo with a supplier file your team already uses.

Tell us how your supplier files arrive and what your channels reject, and we will tell you whether this workflow fits.

Talk to us See what Nexodo does

A person replies, normally within one business day
Use a representative product sample
We will say plainly if Nexodo is the wrong fit

Product attribute mapping: turning every supplier's columns into one model.

Almost every mapping is one of four operations.

Map to the model, never to the channel.

A mapping is an asset, and it belongs to the supplier.

Keep the value the supplier sent, next to the value you approved.

Clear answers before you evaluate a PIM.

Continue your product data research

Onboard supplier product data without surrendering control.

Find the catalog problems that block a confident purchase.

The Shopify product CSV, column by column, including the rows that confuse everyone.

UNSPSC code lookup: the structure, the segments, and how to classify a real catalog.

Test Nexodo with a supplier file your team already uses.