---
title: Meta-classes and meta-fields
slug: commerce-connect-14/docs/meta-classes-and-meta-fields
docTags: 
createdAt: 2026-07-23T10:25:32.050Z
---

Meta-classes are the low-level equivalence of catalog content types, and meta-fields are the low-level equivalence of those content types' properties. Using content models is the recommended approach, but in some cases, meta-fields may be imported from an external system or carried over from a legacy implementation.

Use solid naming conventions and standards when creating fields and classes. While complex data types (images, files) are supported by the metadata system, their use can have a negative impact on performance. To avoid this, use the Optimizely asset/media system and/or image file servers. Use meta-classes to model different types of commerce content.

The following example shows a meta-class named Fashion\_Product\_Class to model fashion products in a sample fashion catalog. The designer of this catalog creates a different meta-class to model fashion variants/SKUs called Fashion\_Item\_Class. The main difference between the two classes is the additional meta-fields on the item class to support the variant's size and color.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/W_8xC8TVPRxYURwPom-Ov-20260723-102637.png "catalogguidelines1.png")