Attribute Mapping
The Conrad Category Attribute Mapping page manages the assignment between Mirakl product attributes and BC item attributes per category.
Open the Page
- Via search: Conrad Category Attr. Map
- Via the Conrad Dashboard → Categories → Action Attribute Mapping
Overview
Conrad/Mirakl requires specific mandatory and optional attributes for each product category (e.g., color, weight, EAN). These are synchronized via the PM11 API and can then be linked to existing BC item attributes.
Workflow
- Sync categories — Via Categories → Sync Categories
- Sync attributes — Via Categories → Sync Attributes (PM11 API)
- Create mappings — Via Categories → Create Mappings (creates mapping entries for all attributes of a category)
- Auto-match — Via Categories → Auto-Match (attempts automatic assignment by name)
- Manual refinement — Manually assign remaining attributes to a BC item attribute
Fields (Category Attribute Mapping)
| Field | Description |
|---|---|
| Category Code | The Conrad category this mapping applies to. |
| Mirakl Attribute Code | The technical code of the Mirakl attribute. |
| Mirakl Attribute Label | The display name of the Mirakl attribute. |
| Required | Whether this attribute is mandatory for product upload. |
| Item Attribute ID | The assigned BC item attribute (manual or via auto-match). |
| Item Attribute Name | The name of the assigned BC item attribute. |
| Default Value | A default value used when no item attribute value exists. |
| Active | Whether this mapping is considered during product export. |
| Sort Order | Order of attributes in the export. |
| Auto Matched | Whether the assignment was made automatically by auto-match. |
| Exclude from Equipment | Exclude attribute from equipment generation. |
FactBox: Mirakl Attribute Details
The FactBox on the right side shows details for the selected Mirakl attribute:
| Field | Description |
|---|---|
| Code | Technical attribute code. |
| Label | Display name. |
| Type | Data type (TEXT, NUMERIC, LIST, MULTI_LIST, DATE, BOOLEAN, MEDIA). |
| Type Parameter | Additional type parameters (e.g., character limit). |
| Description | Description text from Mirakl. |
| Example | Example value. |
| Accepted Values | For LIST/MULTI_LIST: The allowed values. |
Actions (Category List)
| Action | Description |
|---|---|
| Sync Attributes | Synchronizes all Mirakl attributes for the hierarchy of the selected category (PM11 API). |
| Attribute Mapping | Opens the mapping page for the selected category. |
| Create Mappings | Creates mapping entries for all attributes of the selected category. |
| Auto-Match | Attempts automatic attribute assignment via name matching. |
| Mirakl Attributes | Opens the list of all synchronized Mirakl attributes. |
Auto-Matching Logic
Auto-matching attempts to automatically assign BC item attributes based on their name. The matching order:
- Exact code — Attribute code matches BC attribute name exactly
- Exact label — Mirakl label matches BC attribute name exactly
- Case-insensitive — Comparison ignoring case
- Partial containment — BC attribute name is contained in Mirakl label (or vice versa)
Auto-match after creating attributes
If you create or rename BC item attributes later, you can run Auto-Match again. Manually assigned attributes will not be overwritten.
Mirakl Attributes (Reference Page)
The Conrad Mirakl Attributes page shows all attributes synchronized via PM11 as a reference.
| Field | Description |
|---|---|
| Code | Technical attribute code. |
| Label | Display name. |
| Hierarchy Code | The hierarchy this attribute belongs to. |
| Required | Whether the attribute is mandatory in at least one category. |
| Type | Data type. |
| Variant | Whether the attribute is a variant attribute. |
| Date Synced | Last synchronization. |
Tips
Check required attributes
Before your first product upload, verify that all attributes marked as Required have either a BC item attribute or a default value assigned.
LIST/MULTI_LIST attributes
For attributes of type LIST or MULTI_LIST, Conrad only accepts predefined values. These are displayed in the FactBox. Make sure your BC item attribute values match the allowed values.
New attributes after category changes
When Conrad introduces new required attributes, synchronize again and run Create Mappings — existing assignments are preserved, only new ones are added.