Catalog structure
Build one category tree Every channel gets its own taxonomy
Drag and drop the tree into shape, file a product in as many categories as it belongs to, and map each one per channel.
- Unlimited nesting depth
- Drag and drop reordering
- One primary category per product
Key features
Nest as deep as the catalog needs
Parent categories, subcategories and levels below that, reordered by dragging a branch to where it belongs.
Map a category per channel
Point a WISEPIM category at the matching category on Shopify, WooCommerce or a marketplace, and exports land in the right place.
Let a category demand fields
Attach required attributes to a category, so a product filed there is asked for the specs that category needs.
Assigning products
Filing products is a bulk action
Filter to a set of products and add them to one or more categories in a single run, without disturbing the categories they already sit in.
How it works
From an empty tree to channel-ready
Three steps: the first two you do once, the third one runs on every export.
01
Build the tree
Add top-level categories for your main lines, then break them down. Drag a branch to a new parent and its subcategories move with it.
A structure that matches how you actually browse the catalog.
02
File the products
Assign products one by one, in bulk from a filter, or by rule. A product can sit in several categories, with one marked primary.
03
Map the tree onto each channel
Link each category to the channel's own category. WISEPIM translates on export, so you keep one tree instead of one per channel.
The same product lands in the right category on every channel.
Create a category
A category takes one dialog
Name it, pick its parent, and it appears in the tree where you put it, with its own description and SEO fields.
The parent decides the place
Pick the parent in the dialog and the category slots straight into that branch instead of at the root.
Description and SEO fields included
A category page needs its own copy: name, description, meta title and meta description live on the category itself.
Moving it later keeps the products
Drag a category somewhere else and the products stay assigned to it. Restructuring changes the shape, not the data.
In practice
One tree, three different catalogs
Where keeping one internal structure and mapping outward saves the duplicate work.
Several brands, several channels
Each brand arrives with its own structure. They all file into one master tree, and the mapping sends each product to the right place per channel.
Result: one tree to maintain instead of one per channel.
Seasonal campaign categories
Add a temporary category for the campaign, assign products in bulk, and remove it afterwards. The core structure is untouched.
Result: a campaign that ends without a cleanup project.
A new marketplace
Map your existing categories onto the new platform's taxonomy once, and the catalog exports categorized from the first run.
Result: no second category tree to keep in sync.
FAQs
Category questions, answered
Depth, multi-category products, channel mapping and safe restructuring.
Still have questions?
Can't find the answer you're looking for? Please get in touch with our team.
Contact SupportNext step
Build the tree onceMap it per channel
Build your tree on your own catalog for free, or bring your current category list to a call and we map it onto your channels.
