Categories are created and managed via API and the platform supports unlimited category creation and hierarchical nesting through parent–child relationships.
However, excessive category depth or use of categories may negatively impact usability and search performance. It is recommended to combine well-structured categories with attribute-based filtering and sorting rather than relying exclusively on taxonomy depth.
Structural Rules
- An item must belong to at least one category.
- An item may belong to multiple categories.
- A parent category may contain zero or many child categories.
- A child category has exactly one parent.
- Category hierarchy: Parent = Level 0, Child = Level 1, Grandchild = Level 2.
Items can move across categories where such reassignment can be performed either:
- Within the admin portal UI, or
- Via API.
Only the parent item should be updated when changing categories. Updating category IDs in the request body will overwrite the Item’s existing category associations.
Updating Categories via Admin Portal
See How do I edit a category/sub-category? article.
Updating Categories via API
The PUT request must include all categories you want the item to belong to. Omitting a category removes the item from it.
PUT api/v2/merchants/{merchantID}/items/{itemId}
{
"Categories": [
{ "ID": "category_D_id" },
{ "ID": "category_B_id" },
{ "ID": "category_C_id" }
]
}| Note: Omitting any category from the array removes the item from that category. Always include the full intended category set in PUT requests. |