This guide will walk you through how to export and import attributes (e.g. brand , color , brakel_levers ) using a CSV file. This will help you avoid manual clicking and save a lot of time when maintaining your store's attributes. It also includes considerations for validation and typical error situations, and explains how to handle select and multiselect options using a separate CSV.

1. CSV Export Attributes

• Where to edit: Use the Products > Attributes > CSV Export Attributes button in the dashboard.
• This generates a ; -delimited CSV file with a structure similar to the following:

attribute_code;title[fi];title[en];is_filterable;is_comparable;is_listable;is_visible_on_front;is_html_allowed_on_front;sort_order;frontend_input
brand;Merkki;Brand;1;1;1;1;0;5;select

Tip: Always start by exporting existing attributes to give you the most reliable basis for any changes you may make.

2. CSV Import Attributes

Edit or create a new CSV

• You can edit the CSV file created in the previous step (e.g. product_attributes.csv ) or create a completely new one with a similar structure.

Column requirements

• attribute_code
  • Required column. Set when updating an existing attribute or adding a new one.
• title[fi] , title[en] , …
  • Multilingual names. You can optionally add languages, such as title[sv] , if the system recognizes them.
• is_filterable , is_comparable , is_listable , is_visible_on_front , is_html_allowed_on_front
  • Fields with values of 0 or 1.
• sort_order
  • An integer that affects the order of the attribute in the user interface.
• frontend_input
  • Allowed values include select , multiselect , decimal , text , textarea , and boolean .
  • Any other value will be rejected or treated with caution.

Validation
The system checks the CSV file before saving:

• The column headings are correct (e.g. title[fi] – not title_fi ).
• Each row has the same number of columns as the header row.
• The data in each row is valid (e.g. attribute_code is not missing).
• If errors are found, the line is either skipped or the import is aborted.

If the validation passes, the CSV structure is ok.

Most common mistakes

• CSV missing header row: The header row is missing or empty.
• expected X columns, got Y: separator error (e.g. wrong number of columns).
• Attribute already exists!: attribute_code is already in use; decide whether to update or change the code.
• frontend_input is missing: default is e.g. text .

Import CSV

• Where to edit: Use the Products > Attributes > CSV Import Attributes button in the dashboard.
• The system displays a notification (“Import Complete” etc.) when the process is successful.

3. Options CSV

If the attribute is of type select or multiselect , the associated option values (such as brand -> sram , scott , bbb ) are handled by a separate CSV Import/Export Options function.

• Where to edit: You can find the corresponding buttons in the admin panel's CSV Export Options and CSV Import Options sections.
• Columns are, for example code;title[fi];attribute;sort_order .
• Please note that these options do not affect the basic settings of the attribute itself, but only the selections (select/multiselect).

4. What types are accepted?

Supported values for frontend_input field:

• select
• multiselect
• decimal
• text
• textarea
• boolean

All is_filterable , is_comparable , etc. fields are booleans with values of 0 or 1.

5. Recommended workflow

1. Export existing attributes by pressing CSV Export Attributes .
2. Open the CSV (e.g. product_attributes.csv ) in Excel, Google Sheets, or another spreadsheet program.
3. Make the desired changes
   • For example, change the content of title[fi] cell.
   • Increase sort_order value or update is_filterable field.
   • Add new rows if you are creating entirely new attributes (remember the new attribute_code ).
4. Import the CSV using the CSV Import Attributes button in the admin panel.
5. Ensure success
   • The system should report “Import Complete” without any error messages.

Summary

• CSV management of attributes is bidirectional: you can export and import the same attributes.
• Column names must be spelled exactly correctly ( attribute_code , title[fi] , etc.).
• Validation ensures that each row has the correct number of columns and that required information is found.
• The system will either update the existing attribute or create a new one, depending on attribute_code field.
• Option values for select and multiselect types are added or updated using a separate CSV.

By following these instructions, you can easily manage attributes without the need for manual configuration. We always recommend testing the process with a smaller CSV file first to ensure the correct structure and avoid potential errors.