In Episerver commerce, we can manage the same structure.
https://world.episerver.com/documentation/developer-guides/commerce/catalogs/catalog-content/
VariationContent | A type for variant/SKU models. |
ProductContent | A type for product models. |
BundleContent | A type for bundle models. |
PackageContent | A type for package models. |
NodeContent | A type for category/node models. |
Please refer Quick Silver for code sample https://github.com/quicksilver/Quicksilver
In Epi, "Catalog Root" is the top most item (comes by default). Under that you can create multiple catalogs and assicuation to your front end CMS sites.
Here "Fashion" (in the left panel) is the catalog and you can create catagories/subcatagories under it. NodeContent is the base class that is responsible to category item. You can inherit it to create multi level hierarchy for categories.
Commerce support a very wide range of setup, some is easy to do than others, but we can cover 99% of the cases. I guess you should understand some basic structure of catalog first. This gives some ideas https://leanpub.com/proepiservercommerce/read_sample (shameless plug)
We are migrating products from a UCommerce database and the client was using the following structure for their products:
I noticed that EPiServer Commerce provides catalogs but I was not able to find the equivalent for the structure I am trying to achieve, what's the best approach ?
Thank you