# Nested Product Categories in Reports

**URL:** <https://community.piwik.pro/t/nested-product-categories-in-reports/1846>\
**Category:** Data collection and tags\
**Created:** [March 17, 2023, 5:29pm UTC](https://community.piwik.pro/t/nested-product-categories-in-reports/1846 "2023-03-17T17:29:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![onderval](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/onderval/32/1323_2.png) [@onderval](https://community.piwik.pro/u/onderval)\
**Post date:** [March 17, 2023, 5:29pm UTC](https://community.piwik.pro/t/nested-product-categories-in-reports/1846/1 "2023-03-17T17:29:59Z")

</div>

Hey, this question is kind of a mix between a data collection and a reporting question. I know we can pass the category information of a product as a string or as an array. My question is how are these array translated into the reports? I see that there’s a nested product category

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/piwikpro/original/2X/0/06ed0b0bbf70d4d9f6a6f114aacb99174170e1e3.png)

For example, how’s the following array would be listed in the reports? Does the order within array matter? Like this?

Mountain Bike \> Enduro \> Full suspension \> Carbon frame \> 29 inches

![image](https://europe1.discourse-cdn.com/flex005/uploads/piwikpro/original/2X/2/2a9ecf28f0cf63375abf2e4874be7405a3778ba1.png)

---

<div class="post-metadata">

**Author:** ![Jarek](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/jarek/32/4408_2.png) [@Jarek](https://community.piwik.pro/u/Jarek)\
**Post date:** [March 20, 2023, 8:42am UTC](https://community.piwik.pro/t/nested-product-categories-in-reports/1846/2 "2023-03-20T08:42:26Z")

</div>

Hi @onderval,  
yes, the order of items in `category` matters. Each of them will be saved under separate dimension: `Product category 1`, `Product category 2` etc.

We’re rebuilding e-commerce tracking and reporting and the new improved version will be available in May. Since then you’ll be able to use those dimensions in explorer report and nest one under another. We will also introduce the new dimension `Product category` (without a number) that will store all categories as one value, in your example that would be: `Mountain Bike/Enduro/Full suspension/Carbon frame/29 inches`.

---

<div class="post-metadata">

**Author:** ![onderval](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/onderval/32/1323_2.png) [@onderval](https://community.piwik.pro/u/onderval)\
**Post date:** [March 20, 2023, 8:55am UTC](https://community.piwik.pro/t/nested-product-categories-in-reports/1846/3 "2023-03-20T08:55:38Z")

</div>

Great news, thank you. I hope the improved version includes product-scoped custom dimensions 😅

---

<div class="post-metadata">

**Author:** ![Jarek](https://dub1.discourse-cdn.com/flex005/user_avatar/community.piwik.pro/jarek/32/4408_2.png) [@Jarek](https://community.piwik.pro/u/Jarek)\
**Post date:** [March 20, 2023, 1:18pm UTC](https://community.piwik.pro/t/nested-product-categories-in-reports/1846/4 "2023-03-20T13:18:40Z")

</div>

Product-scoped custom dimensions are planned for the next iteration. It may be released somewhere near the summer but I don’t have the exact dates yet.
