# Creating Grouped Items Using Data Manager

> Source: https://help.getedara.com/en/articles/16221355-creating-grouped-items-using-data-manager · Category: Extensions Store › Data import (advanced mode) · Last updated: 2026-08-24 · العربية: https://help.getedara.com/ar/articles/16221355-%D8%A5%D9%86%D8%B4%D8%A7%D8%A1-%D8%A7%D9%84%D8%A3%D8%B5%D9%86%D8%A7%D9%81-%D8%A7%D9%84%D9%85%D8%AC%D9%85%D8%B9%D8%A9-%D8%A8%D8%A7%D8%B3%D8%AA%D8%AE%D8%AF%D8%A7%D9%85-%D8%A7%D8%B3%D8%AA%D9%8A%D8%B1%D8%A7%D8%AF-%D8%A7%D9%84%D8%A8%D9%8A%D8%A7%D9%86%D8%A7%D8%AA

When managing items with multiple variants, such as size or color, you may need a faster way to create grouped items or update them in bulk instead of handling each item individually.

## Creating Grouped Items Using Data Manager

[Video: Creating Grouped Items Using Data Manager](https://www.youtube.com/watch?v=9S_UlSOC85I)

1. Go to “System”.
2. Open the “Extension Store” page.
3. Click on “ **[Data](https://importmanager.edara.io/)** [**Manager**](https://importmanager.edara.io/) ”.
4. Enter your Edara account email and password.
5. Click on “ **Sign in** ”.
6. Click on “ **Grouping Items** ”.
7. Choose “Create New”.
8. Click on “ **Download Template** ”.
9. Fill in the template file.
10. Upload the form file after entering the required data.
11. Click on “ **Validate Data** ”.

The system will validate the imported data. If any errors are detected, they will be displayed, and you can export an error file for review, correct the data, and upload the file again for validation.

1. Click on “ **Start Import** ”.
2. Click on “ **Done** ”.

![Creating Grouped Items Using Data Manager — Click on “Done”.](https://help.getedara.com/images/ext-tools/16221355/01.en.gif)

> **Notes:**
>
> 1. Each row in the template represents one child variant, and rows with the same parent are automatically grouped.
> 2. The first row of each group must include the parent data, such as Description and Classification, along with the first child variant.
> 3. Additional rows represent child variants only, and should include option values while leaving parent fields empty.
> 4. Child rows inherit shared data such as Classification, Brand, and Tax from the parent row.
> 5. You can select up to three option values per child, and all children must use the same set of options.
> 6. Each child must have a unique combination of option values.
> 7. If the child's Code or SKU is left empty, it will be generated automatically by the system.
> 8. Make sure all option values exist in the predefined values and belong to a single property.
> 9. Delete any sample rows in the template before uploading the file.
> 10. You can refer to the example and the instruction file attached within the template file to learn how to enter the data correctly before starting the import process.