Brand Mapping

Brand mapping normalizes inconsistent supplier brand strings to a canonical brand list. This ensures that "NIKE INC.", "Nike", and "nike" all resolve to the same brand in your catalogue.

Your canonical brand list

Go to Data Mapping → Brands → Manage catalogue brands to see and manage your canonical brands.

Each brand has a:

• Label: display name (e.g. “Nike”)
• Code: unique normalized slug (e.g. nike) — used in export field mappings and pricing rule conditions

Mapping supplier brands

After a feed import, go to Data Mapping → Brands → Supplier mappings.

For each raw brand string from the supplier:

1. Click Map
2. Start typing to find an existing canonical brand or create a new one
3. Click Save

Global vs. supplier-specific mappings

Brand mappings can be global (any supplier) or specific to one supplier. Supplier-specific mappings take precedence over global ones.

Why brand mapping matters

Unmapped brands are stored as raw strings. This causes problems with:

• Pricing rules: a rule like “apply 20% margin to all Nike products” requires the brand to be mapped to the canonical nike code
• Export field mappings: the destination may require a specific brand code or ID
• Product deduplication: when the same product appears in two suppliers with different brand spellings, deduplication by GTIN works regardless of brand — but brand-based deduplication requires mapping

Unmapped brands

Run Data Mapping → Brands → Unmapped to see all raw brand strings that haven’t been mapped yet. This list updates after each import run.