Skip to main content
Back to E-commerce Dictionary

Content Model

Content and digital asset managementIntermediate Level

A content model is a structured plan of the content types you manage, the fields each type has and how the types relate to each other.

Image by · CC BY 4.0

What is Content Model?

A content model is a structured plan of the content types you manage, such as products, categories and brands, the fields each type has, and how those types relate to each other. It works as a blueprint: every item of a type gets the same fields, so content stays consistent and reusable. For product data, a content model sets which attributes a product type needs (a shoe has size, material and width, a TV has screen size and resolution), which are required, which values are allowed and how variants link to a parent product. It differs from a data model, which describes how a database stores data. The content model describes content as editors and channels use it. The attribute modeling guide shows how to design one for a catalog.

Why Content Model matters for e-commerce

Without a content model, every product gets whatever fields the person entering it thinks of. Shoppers then cannot compare products, filters miss items and channels reject listings that lack required attributes. A clear content model makes product data predictable. Every product of a type has the same attributes, filters work across the catalog, and you can send the same structured data to a webshop, a marketplace and a feed without rewriting it per channel.

Examples of Content Model

  • 1Content type: Shoe, Fields: brand, size, material, width, color, Relations: variants per size and color
  • 2Content type: Television, Fields: screen size, resolution, refresh rate, energy label, Relations: linked accessories
  • 3Content type: Category, Fields: name, description, image, Relations: parent category and products
  • 4Content type: Brand, Fields: name, logo, story, Relations: all products of the brand

How WISEPIM Helps

  • Product families define which attributes each product type gets, so the content model is applied to every product.
  • Attribute management and the Attribute values page keep field definitions and allowed values in one place.
  • Variants link sizes and colors to a parent product, following the relations in your model.
  • Quality Guard rules flag products that miss required fields of their family.

Learn more about Product Enrichment: enrich product data with AI at scale.

Common mistakes with Content Model

  • Creating too many types and fields, which makes the model hard to maintain.
  • Designing only for today's channels and having to rebuild when a new channel arrives.
  • Modeling for the database instead of for the people who write and read the content.
  • Designing without editors, developers and marketers at the table.
  • Using free text where a list of allowed values would keep data consistent.

Tips for Content Model

  • Start with your most important product types and their must-have fields.
  • Involve editors, developers and marketers from the first draft.
  • Use allowed value lists for attributes shoppers filter on.
  • Document every type and field with a short description and an example.
  • Review the model when you add a channel or a new product type.

Trends around Content Model

  • Composable content: small reusable blocks that headless frontends assemble per channel.
  • AI-assisted modeling: tools suggest attributes and values from existing product data.
  • Models built for AI shopping: structured attributes that AI assistants can read and compare.
  • Standard taxonomies as a base: models that map to Google product categories, ETIM or GS1 from the start.

Tools for Content Model

  • WISEPIM: a PIM with product families, attribute management and variants to apply a content model to product data.
  • Akeneo: a PIM with families, attributes and associations for modeling product content.
  • Contentful: a headless CMS where you define content types and fields.
  • Sanity: a headless CMS with schemas defined in code.

Related Terms

Also Known As

Content structureContent schemaProduct data modelInformation architecture

Frequently Asked Questions

It is a blueprint of your content: which types exist, which fields each type has and how the types connect. Every product of the same type then gets the same set of fields.

A data model describes how a database stores data, with tables, keys and relations. A content model describes content the way editors and channels use it, with content types, fields and rules. A content model often sits on top of a data model.

A shoe type with fields for brand, size, material, width and color, where each size and color is a variant of one parent product. A television type would have screen size, resolution and energy label instead.

Structured content can be created once and reused on every channel. Each channel picks the fields it needs, so you do not rewrite product data per webshop or marketplace.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

Keep exploring

Hand-picked next steps to go deeper.