---
title: "Product Catalog: Mixed Fashion and Non-Fashion Catalogs"
slug: "product-catalog-mixed-fashion-and-non-fashion-catalogs"
status: "new"
updated: 2026-09-25T14:18:08Z
published: 2026-09-25T14:18:08Z
canonical: "docs.mapp.com/product-catalog-mixed-fashion-and-non-fashion-catalogs"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Catalog: Mixed Fashion and Non-Fashion Catalogs

**25 September 2026** Fashion-enabled Product Catalogs can now contain fashion and non-fashion products in the same feed. Until now, every variant in a Fashion-enabled catalog was validated against the full set of fashion attributes, so products without them, such as jewellery without a size, were rejected on import. The new Enrichment Type attribute marks each variant as a fashion product or not, and the import validates it accordingly.

## Key Benefits

- **Product attributes for all products**: non-fashion products are now imported instead of rejected, so their attributes become usable in Mapp Intelligence and Mapp Engage like those of any other product.
- **Clear requirements per product type**: the import mapping marks attributes that only fashion products need as Mandatory for fashion.
- **Fashion enrichment only where it applies:** Mapp Fashion processes only products marked as fashion. If you previously used placeholder values to import non-fashion products, mark them as none to exclude them from enrichment.

## How does it work?

Each variant has an Enrichment Type of `fashion` or `none`. During import, variants are grouped by this value and each group is validated separately. Variants marked `fashion` must include all attributes that are Mandatory for fashion, for example Size, Style ID, and Brand. Variants marked `none` only need the attributes that are mandatory for every product. Mapp Fashion only uses and enriches variants marked `fashion`. This applies to CSV imports and to the Product Catalog API.

If no Enrichment Type is provided, new variants and variants without a stored value are treated as `fashion`. Existing variants keep their stored Enrichment Type. That is why nothing changes for existing catalogs until you add the attribute. If your catalog mixes fashion and non-fashion products, add Enrichment Type to your product data. [How Catalog Data Flows](/v1/docs/connect-product-catalog-how-catalog-data-flows#enrichment-type-on-import) shows an example with clothing and jewellery in one file.

## Availability

Enrichment Type is available for all Fashion-enabled Product Catalogs. For the full list of attributes and the rules for each Enrichment Type, see [Mixed Catalogs and Enrichment Type](/v1/docs/connect-product-catalog-product-attributes-model#mixed-catalogs-and-enrichment-type).

> [!NOTE]
> Beta
> 
> The Product Catalog is currently in Beta and is not yet available to all customers. Availability is being expanded gradually. Functionality, configuration, and behavior may change before general availability.