Home
/
Use cases
/
Product attribute mapping across every supplier
Use case

Product attribute mapping across every supplier

Attribute mapping connects each supplier's fields and values to your own attributes. Map once, save it per supplier, and reuse it on every new file.

Try it on your own data
Product attribute mapping across every supplier

Product attribute mapping connects the way each supplier describes a product to the way you do. SKULaunch maps supplier fields to your attributes and supplier values to your allowed values, saves those mappings per supplier, and applies them every time a new file arrives.

The problem

Every supplier has its own vocabulary. One sends "Colour", another "Finish", a third "Col". One writes "Stainless Steel", another "S/S", another "304". Unless those are mapped to a single attribute with a single set of values, your filters fragment, search misses products and comparisons fall apart.

Most teams fix it file by file in spreadsheets, which means the same mapping decisions are made again every month. The knowledge of what "Batt" means for one supplier lives in one person's head, and when that person is on holiday the range waits.

Before and after

An illustrative example across three suppliers to a bathroom and kitchen retailer, for kitchen taps.

Before: three supplier files

Supplier A: Finish = "Brushed SS". Supplier B: Colour = "Stainless". Supplier C: Col/Fin = "BRSH NICKEL".

After: one attribute, one set of values

  • Attribute: Finish
  • Supplier A "Brushed SS" to Brushed stainless steel
  • Supplier B "Stainless" to Stainless steel
  • Supplier C "BRSH NICKEL" to Brushed nickel
  • One Finish filter on the website with three clean options

How it works in SKULaunch

  1. Map fields. On import, each supplier column is matched to one of your attributes, with suggestions based on the column name and contents.
  2. Map values. For select attributes, supplier values are matched to your controlled list, so "S/S" and "Stainless" become the same value.
  3. Save the mapping. Field and value mappings are saved as a template for that supplier and reused on every future file.
  4. Handle the leftovers once. New fields or values that have no mapping yet are raised for a decision, then added to the mapping for next time.

Attribute mapping: field mapping is the easy half

Most tools stop at matching column headers. That is the easy half. The hard half is value mapping: deciding that "BZP", "Zinc plated" and "ZP" are one value, that "2m" belongs in a length attribute in millimetres, and that "Yes" in a column called "Batt" means a battery is included. Value mapping is what makes filters work and what makes data from fifty suppliers look like it came from one. It is also where most of the manual effort hides, which is why it needs to be saved and reused rather than redone.

The value mappings you will meet

  • Abbreviations. "SS", "BZP", "BLK" expanded to your full value.
  • Synonyms. "Stainless" and "Inox" to Stainless steel.
  • Codes standing in for values. A material grade such as "304" may need mapping to a material and a grade attribute.
  • Units inside values. "2m" split into a number and a unit, then converted to the unit your attribute uses.
  • Combined columns. "Col/Fin" holding colour on some rows and finish on others, which needs splitting before it can be mapped.
  • Booleans. "Y", "1", "Included" and "TRUE" to one yes value.
  • Values in the wrong column. Pack quantity typed into the title, or IP rating in the description.

A worked example: one supplier's first file

An illustrative first file from a new tap supplier, and the decisions it needs:

  1. Confirm the suggested field matches. "Finish" to Finish, "EAN" to GTIN, "Spout Reach mm" to Spout reach.
  2. Decide on the unclear columns. "Col/Fin" only ever holds finish for this supplier, so it maps to Finish. "Range" maps to Product line. "Internal ref" is ignored.
  3. Map the values. "BRSH NICKEL" to Brushed nickel, "CP" to Chrome, "Y" in Aerator to Yes.
  4. Save it. The next file from this supplier arrives with all of those decisions already made, and only new columns or values need attention.

Common mistakes

  • Mapping to the supplier's model instead of yours, so your attributes change every time a supplier changes theirs.
  • Creating a new attribute for every unfamiliar column, until the model has three attributes for colour.
  • Mapping fields but leaving values free text, so the filter still shows "S/S" and "Stainless".
  • Keeping mappings in a personal spreadsheet instead of saving them against the supplier.

What changes

New supplier files arrive already speaking your language. The mapping effort falls with every file, because decisions made once are applied automatically next time. The knowledge of what each supplier means sits in the platform rather than in one person's spreadsheet, so a new range can be loaded by whoever is in that week.

Common questions

What is attribute mapping in product data?

Matching each supplier's fields and values to the attributes and allowed values in your own product model.

What is the difference between attribute mapping and normalisation?

Mapping connects incoming supplier data to your model. Normalisation cleans the values already in your catalogue. See how to clean up inconsistent values.

Do we need a mapping for every supplier?

Each supplier gets its own saved mapping, but common mappings can be reused across suppliers who use the same terms.

What if our attribute model changes?

Update the mapping for the affected attributes. Other mappings are unaffected.

What happens to columns we have not mapped?

They are raised for a decision: map them to an attribute, add a new attribute, or ignore them. The decision is saved for that supplier's next file.

Does mapping work for standards like ETIM?

Yes. ETIM features and values are mapped to your attributes in the same way, so ETIM and non-ETIM suppliers end up consistent. See how to import ETIM data.

More on mapping and normalisation, how to import supplier spreadsheets, reusing column mappings, and our guide to product attributes.

See it working on your own product data

Upload a supplier file and watch SKULaunch turn it into complete, structured, sales-ready records. Two weeks free, no card, no consultants.

© 2026 SKULaunch Ltd. All rights reserved.
Built for e-commerce teams who are done doing it by hand.