The product hierarchy is the tree your products are organised into — a root at the top, branches beneath it — and the node a product sits under carries the defaults it starts life with. It's built across two Admin pages: Hierarchy Levels sets the tiers, and Hierarchy Nodes builds the tree.
Hierarchy levels
Levels are the tiers of the tree, and each level has a type. Three types exist: root, primary, and secondary. A type can be followed by group, which means the level is named as a group sitting over the level that follows it. A hidden level is one that's hidden and set automatically when a node under it is chosen — used mainly for exports and integrations.
Build the tiers with Add level. A quirk of the current setup: a secondary level has to be created first, then you set your root. If you only have two levels, those two are what apply; otherwise you carry on — adding the primary, and a sub-secondary if you're not using grouping. The order the levels end up in is: root, primary (with or without group), secondary (with or without group), sub-secondary — so even though you create secondary first, the primary comes in afterwards at a higher level.
Hierarchy nodes
Nodes are the actual branches going out from the root down. The checkboxes above the table filter the list by level, and Filter to sub-tree of narrows it to one branch.
The nodes sit in a table whose columns you can pin, hide and reorder. Edit a node by clicking it — it opens in a popper — or right-click it and choose Edit. Right-click also lets you change a node's parent, reorder it within its own level, reorder its children (the level below), add a child node beneath it, or delete it.
Set up a node
Create a node with Add node (or right-click an existing node and choose Add child node). You always give it a name and place it under a parent, which sets its level.
Give it an icon — it isn't required, but makes it visibly easier in the system.
Everything else is optional — set these to shape what a product created under the node starts with, or leave them and the product gets everything:
Full name — the longer name shown in overviews.
External code — used for integrations.
Article number code — if a specific number or letter in the article number per hierarchy node is needed.
Available product categories — set what available product categories are visible under the node. No adding means all are visible.
Available tag categories — set what available tag categories are visible under the node. No adding means all are visible.
Available custom field groups — set what available custom field groups are visible under the node. No adding means all are visible.
Default units — set as pieces or pairs (or other units set as product units in admin page Units).
Default genders — either inherits from the parent node or sets automatically.
Available size systems — set what available size systems are visible under the node. No adding means all are visible.
Default size system — set a default size system always added to products under this node.
Default assignees — set per default who or which should be owner of the products under this node.
You can always change any of the default settings on the product afterwards.
💡 Setting one of the "available" options on a node claims it: it's then removed from the other nodes unless you set it on them too. So you if you configure this, do it on all nodes — and if nothing is set anywhere, everything shows everywhere.
Moving a product to another node
To move a product to another node, open Products in Admin, enter the product's ID (available in the URL when you are in a product page), pick the hierarchy node to move it to (tick Show only primary nodes to shorten the dropdown, or leave the node unset to clear it), then Run.
Export
You can export your hierarchy into an excel by clicking Export.