---
title: Catalog configuration | Shopware Community Hub
description: >-
  Discover how to design and implement effective catalog configurations in
  Shopware to optimize product discovery and management. This unit covers
  category…
canonical_url: 'https://hub.shopware.com/learn/unit/solutions-architect-catalog-configuration'
---

# Catalog configuration

<LearningObjectives>

- Understand the importance of catalog configuration in the context of different ecommerce business models.
- Learn how to structure a category taxonomy that supports customer browsing and discovery.
- Grasp the fundamentals of creating a robust product data model to enhance product management and customer experience.

</LearningObjectives>

# Introduction to Catalog Configuration in Ecommerce

In ecommerce, the product catalog is at the heart of how your shop presents and organizes its offerings to customers. The structure and setup of the catalog can significantly impact how customers find products, how they interact with the shop, and ultimately, how they make purchasing decisions. From a Solutions Architect's perspective, configuring a product catalog isn't just about listing products in a respective category—it's about creating an intuitive and efficient system that enables customers to discover products and learn enough about them to make an informed purchase decision.

At the foundation of any catalog configuration are two key elements: the category taxonomy and the product data model. These elements must be carefully designed and implemented to ensure a seamless customer experience and efficient product management.

Different types of businesses have different needs when it comes to their product catalogs. For instance, a B2B parts manufacturer may need a catalog organized around the specific types of machinery for which it produces parts, detailing many of its technical specifications, such as compatibility, material, tolerances, and measurements per part. In contrast, a B2C fashion retailer might structure its catalog around lifestyle categories, such as "Night Out" or "Beachwear". The detail page will show the garments both on a model and as an isolated shot, and the content will highlight the experience of wearing the items. These catalogs are designed to resonate with how customers shop by experience and application rather than by simple product type.

## The Category Taxonomy

The category taxonomy, or category tree, is the organizational backbone of your product catalog. It dictates how products are grouped and navigated, influencing how customers explore your offerings.

**Why the Category Taxonomy Matters**:

A well-thought-out category structure can guide customers through their shopping journey, allowing them to explore products in a natural and intuitive way.

**Best Practices for Category Taxonomy**:

- **Keep it Simple**: We generally recommend not going deeper than three layers in your category structure. While more complex product ranges may require additional layers, simplicity helps maintain clarity and ease of navigation. Too many layers can overwhelm customers and make products harder to find.

- **Think Beyond Product Types**: While it's important to categorize products by type, it's equally important to consider the context in which products are used. Grouping products by how customers intend to use them provides a context-driven approach that resonates with customers, supporting the trend of shopping by experience rather than by specific product type.

- **Focus on Customer Experience**: Today's customers are less likely to come to your shop knowing exactly what they want. Instead, they want to explore, research, and browse. Your category structure should support this behavior, making it easy for customers to discover and learn more about products.

## Managing The Category Taxonomy in Shopware Admin

The category tree in Shopware Admin is a powerful tool that goes beyond simply organizing products into categories. It is the backbone of your storefront's navigation, allowing you to build entire menus blending product categories with custom links, content pages, and more.

**Building Menus with the Category Tree**:

In Shopware, each sales channel has two entry nodes. The top category node is the starting point for all navigation in the top menu and the footer menu. Structuring the category tree will directly influence how customers interact with your shop.

The category tree allows you to:

- **Create Product Categories**: Standard categories that group products together. The process is described here: [Create category](https://docs.shopware.com/en/shopware-6-en/catalogues/categories#create-category).

- **Add Custom Links**: External HTTP links or internal dynamic links to content pages or products. More info about this here: [General](https://docs.shopware.com/en/shopware-6-en/catalogues/categories#general).

- **Feature Content Pages**: Highlight important content, such as blogs, FAQs, or policy pages, alongside product categories to provide a comprehensive navigation experience. [Landingpages](https://docs.shopware.com/en/shopware-6-en/catalogues/categories#landingpages).

Additionally, landing pages can be added with tailored product offerings following a specific theme. Each category- or landing page can have a unique layout, allowing flexibility in how products and content are presented.

More info about this can be found in [Categories in Shopware](https://docs.shopware.com/en/shopware-6-en/catalogues/categories) and [Setup footer and service menu](https://docs.shopware.com/en/shopware-6-en/tutorials-and-faq/basic-setup).

**Strategic Planning for Navigation**:

As a Solutions Architect, it's crucial to engage with your client early in the project to map out the navigation tree. This involves sitting down with the client to understand their business goals, customer behavior, and the key elements they want to highlight in their shop.

One of the most effective ways to approach this is by analyzing existing customer behavior through tools like Google Analytics. By understanding how customers currently navigate the site—what pages they visit, the paths they take, and the search terms they use—you can make informed decisions about how to structure the navigation tree.

Considerations might include:

- **Primary Navigation Pathways**: Identify the most important categories and pages that should be easily accessible from the main menu.

- **Supporting Content**: Determine where to place supporting content, such as guides, blogs, or customer service pages, within the navigation.

- **Cross-Linking**: Strategize how to cross-link between categories and content pages to encourage deeper exploration of the site.

## The Product Data Model

The product data model is another critical component of your catalog configuration. Despite its importance, the product data model often doesn't receive the attention it deserves in many ecommerce setups.

**What is the Product Data Model?**:

The product data model defines the structure and relationships of all the data associated with your products. This includes everything from basic information like names and SKUs to more complex data like properties, variants, and specifications. A well-designed product data model ensures that all relevant product information is captured, organized, and accessible. The perfect product data model keeps in mind both the information the customer will need to make an informed purchase decision (E.g. the 'fit' of a piece of garment, or the compatible models of a replacement part), as well as the needs of various systems to work with products (E.g. properties like 'color' for recommendations, or the dimensions for shipping)

**Why is the Product Data Model Important?**:

- **Consistency and Accuracy**: A robust product data model ensures that product information is consistent and accurate across your catalog. This not only improves the customer experience but also reduces the risk of errors that can lead to customer dissatisfaction and returns.

- **Enhanced Search and Filtering**: The product data model also plays a crucial role in enabling advanced search and filtering capabilities. By organizing data effectively, you can ensure that customers find products quickly and easily using various filters, such as price, size, color, or technical specifications.

- **Data-Driven Systems**: In today's ecommerce landscape, data drives many systems, from AI recommendations to search algorithms. These systems rely on structured data to function effectively. For instance, AI-driven product recommendations can only work accurately if the underlying data, such as attributes and product relationships, is well-organized and specific.

### Managing the Product Data Model in Shopware

Shopware provides tools to apply the product data model to products through the Product Admin interface. The process is described in detail here [Create products](https://docs.shopware.com/en/shopware-6-en/catalogues/products).

**Using Properties for Product Characteristics**:

<img src="../../assets/images/properties.png" width="400"/>

Properties in Shopware are predefined characteristics that can be assigned to each product. These properties are used to define features such as color, size, material, and other common attributes that apply to a broad range of products. Once set up, these properties not only help in categorizing and filtering products but also enhance the search functionality, allowing customers to refine their search based on specific criteria.

For example, if you're selling clothing, you might have properties like "Color," "Size," and "Material." These properties can be applied to all relevant products, making it easy for customers to filter the catalog according to their preferences.

Using property types select, boolean, color picker, or price field allow a property to become filterable. This enables a customer to narrow the product listing down in the frontend, on a category or search page, by applying value filters.

More information about the properties can be found here [Properties](https://docs.shopware.com/en/shopware-6-en/catalogues/products#properties).

**Custom Fields for Product Group-Specific Characteristics**:

<img src="../../assets/images/customfields.png"/>

While properties are useful for common attributes across many products, there are cases where specific product groups require unique characteristics that are not shared with other products. This is where **Custom Fields** come into play. Custom Fields allow you to create tailored data points specific to a particular product group.

To manage these group-specific characteristics, you can create a **Custom Field Set** under `Settings > System Settings`. A Custom Field Set groups together related Custom Fields that apply to a specific type of product. For example, if you're managing a catalog of camping equipment, you might create a Custom Field Set called "Camping Tents."

Within this Custom Field Set, you can define various Custom Fields that capture the unique attributes of camping tents, such as:

- **Model Type**: To categorize the tent by its design, such as dome, tunnel, or geodesic.

- **Number of Openings**: To indicate how many doors or entrances the tent has.

- **Vestibule**: A field to specify whether the tent includes a vestibule (an additional covered area) or not.

These Custom Fields can then be assigned to products within that specific group, ensuring that each product has all the relevant information needed for customers to make informed decisions.

Please note that Custom Fields can not be made filterable. For that, properties will always need to be used.

Further information can be found in the article [Custom fields](https://docs.shopware.com/en/shopware-6-en/catalogues/products#custom-fields).

**Product Data Models and Supplier Variability**:

Each type of product may require its own product data model. Moreover, in multi-vendor or multi-supplier setups, it's common to see significant variability in the product data provided by different suppliers. One supplier might provide extensive technical specifications, while another might offer only a basic description.

This variability makes it even more important to establish a clear and consistent product data model that can accommodate differences while ensuring that all necessary information is captured. The more detailed and structured your product data model, the better it can support advanced functionalities like AI-driven recommendations and search.

**Using a PIM System**:

To manage these complexities, a Product Information Management (PIM) system can be incredibly useful. A PIM system allows businesses to centralize and manage product information, ensuring consistency across all sales channels. We will delve into PIM systems in more detail later in the course, but it's important to recognize their value in supporting a robust product data model.
