Assortment Planning - Categorization Structure Level Schemas

3 min. readlast update: 04.07.2026

 

Purpose

Categorization Structure Level Schemas define the hierarchical structure used to organize assortment elements such as products, services, and fixed assets.

A schema determines the number and order of category levels used to classify assortment elements. This ensures that catalog structures remain consistent across the organization and that all items follow the same hierarchical categorization model.

These schemas act as the structural foundation for organizing catalogs and supporting navigation, filtering, reporting, and assortment analysis.


Access Path

Control Center → Assortment Planning → Categorization Structure Level Schemas

This configuration area is part of the Assortment Planning administrative setup and is typically managed by system administrators or catalog administrators.


Categorization Structure Schemas Overview

The Categorization Structure Level Schemas landing page displays all schemas configured in the system.

For each schema, the list displays:

Field Description
Name Name of the categorization schema
Companies Defines the organizational scope where the schema is available

Schemas may be defined as Tenant-Wide, allowing them to be used across all companies in the system.

From this page, administrators can create, review, and manage categorization structures.


Available Actions

From the landing page, users can:

  • Add Categorization Structure Level Schema – Create a new schema
  • Open an existing schema – View or edit its configuration
  • Refresh – Reload the schema list
  • Include Deleted – Display deleted schemas
  • Export – Export the list of schemas
  • Customize Columns – Adjust the columns displayed in the table

These options allow administrators to manage the structural foundation of the assortment catalog.


Creating a Categorization Structure Level Schema

Step 1 – Create the Schema

Click Add Categorization Structure Level Schema.

Complete the following fields:

Field Description
Name Name of the schema that will define the categorization hierarchy
Companies Defines the scope where the schema is available (Tenant-Wide or company-specific)

Select:

  • Save – Creates the schema
  • Save and New – Saves the current schema and opens a new creation form

Once saved, the schema can be configured with its categorization levels.


Defining Categorization Levels

After creating a schema, open it to access the Schema Details view.

This screen allows administrators to define the hierarchical levels that will structure the assortment catalog.

Each row represents one classification level within the hierarchy.

Example:

Level Example Meaning
Level 1 Category
Level 2 Subcategory
Level 3 Product Family
Level 4 Product Type

The number of levels can be adjusted depending on the organization’s catalog structure.


Managing Schema Levels

When editing a schema, the following actions are available:

Add New Level

Select Add New to insert an additional hierarchy level.

Edit Level Names

Each level can be renamed to reflect business terminology.

Examples:

  • Department
  • Category
  • Subcategory
  • Service Type
  • Asset Group

Reorder Levels

Levels can be reorganized using the drag handles to adjust their hierarchical order.

Remove Levels

Unnecessary levels can be removed if they are no longer required.


How Categorization Schemas Are Used

Categorization schemas are applied when organizing assortment entities such as:

  • Products
  • Services
  • Fixed Assets
  • Programs or bundles

When a categorization structure is used, the defined levels ensure that items are classified consistently across the system.

For example:

Architecture Services
→ Design
→ Residential
→ Interior Design

This structure enables:

  • Better navigation of catalogs
  • Consistent classification
  • Improved reporting
  • Easier filtering and analysis

Best Practices

  • Keep category hierarchies clear and logical.
  • Avoid creating too many levels, which can complicate navigation.
  • Align level names with business terminology.
  • Use tenant-wide schemas when the same structure is shared across companies.
  • Review schemas periodically to ensure they remain aligned with the business catalog structure.

Related Articles

Assortment Planning – Configuration Overview
Assortment Planning – Product Variant Categorization
Assortment Planning – Price Lists
Assortment Planning – Price Guards
Assortment Planning – Programs
Assortment Planning – Managing Products
Assortment Planning – Managing Services
Assortment Planning – Managing Fixed Assets


 

Was this article helpful?