Skip to main content

Header names and their mapping to Magento attributes

Learn how Elovate export headers map to Magento attribute codes and best practices for editing and re-importing product data

Updated over a week ago

When you create an export job in Elovate, the output file is generated based on the attributes you select. Each column header in the export corresponds directly to a Magento attribute code, not the attribute’s display name.

For example:

Export file header

Magento attribute label

Example value

sku

SKU

EXAMPLE-001

name

Product Name

Dining Chair

price

Price

99.95

color

Color

Green

category_ids

Categories

12, 18


Why attribute codes are used

Magento uses attribute codes as the internal identifiers for product data. While the display names (labels) can change per store view or language, attribute codes remain consistent across your store and are what Elovate references when importing or exporting data.


Mapping and understanding headers

  • Standard Magento attributes like sku, name, price will match Magento’s default attribute set.

  • Custom attributes will appear with their own attribute code (e.g., brand, material_type).

  • Multi-select attributes will export as comma-separated values in a single cell.

  • Category IDs are numeric and represent the Magento category entity IDs.

  • Dropdown attributes in Google Sheets exports will include the option labels as selectable items, making them easier to edit and re-import.


Practical tips

  • Don’t rename headers when re-importing. Elovate relies on these codes to correctly map the data back to Magento attributes. However if they are different, you can easily adjust this in the import mapping.

  • If you are unsure of what an attribute code means, you can check it in Elovate -> attributes

  • For large exports, consider using product templates so you can easily reuse the same header set.

Did this answer your question?