---
title: Define fields for the reusable SKU product content type
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Prototype the content model with Content modeling MCP server

Before we dive into the details of modeling **Product SKUs**, let’s start by prototyping the content type using Xperience’s [Content modeling MCP server](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md).

The MCP server provides an _end-to-end guided process_ for gathering content type requirements, designing widgets, and creating the foundation of our **Product SKU** content type. We'll refine this foundation to meet the specific needs of _Pawsome Pets_.

### Gather project requirements

The process begins by gathering project requirements through a series of steps. Information like your industry, target markets, marketing channels, and editor experience helps the agent suggest a content model that fits your needs.

![Start of the content modeling workflow](https://docs.kentico.com/docsassets/modules/prototype-with-content-modeling-mcp-server/content_modeling_workflow_1.png "Start of the content modeling workflow")

Additional details, such as the number of websites, channels, content volume, and reuse strategy, help the MCP agent design an appropriate content model.

![MCP server requests additional project information](https://docs.kentico.com/docsassets/modules/prototype-with-content-modeling-mcp-server/content_modeling_workflow_2.png "MCP server requests additional project information")

After collecting all the details, the server summarizes the results and proceeds to the next phase.

![Summary of gathering requirements phase](https://docs.kentico.com/docsassets/modules/prototype-with-content-modeling-mcp-server/content_modeling_workflow_summary.png "Summary of gathering requirements phase")

### Design content types

The MCP server uses your input and Kentico’s [best practices](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-guide.md) to create content types tailored to your business and website. These include reusable content for _pets_, _accessories_, _articles_, _FAQs_, and _customer testimonials_. The server also suggests webpage content types, such as _HomePage_, _PetDetailPage_, anc _PetListingPage_ to display product data.

![Overview of content types the MCP server suggests based on the project requirements](https://docs.kentico.com/docsassets/modules/prototype-with-content-modeling-mcp-server/content_types_pet_store_overview.png "Overview of content types the MCP server suggests based on the project requirements")

### Use your agent to analyze the prototypes

For this material, let’s look at how the _Content modeling MCP server_ created prototypes for the _Pet_ and _Product_ content types.

Both content types use _CoreContentSchema_ built with [reusable field schema](https://docs.kentico.com/documentation/developers-and-admins/development/content-types/reusable-field-schemas.md) feature. This schema includes a _title_, _summary_, _thumbnail image_ and _category_.

Unlike the _ProductSKU_ content type, which covers all accessories _Pawsome Pets_ sells, the _Pet_ content type represents animals. It doesn't include a [Stock Keeping Unit](https://www.shopify.com/blog/what-is-a-sku-number).

![Overview of Pet and Product content types](https://docs.kentico.com/docsassets/modules/prototype-with-content-modeling-mcp-server/pet_and_product_sku_content_types.png "Overview of Pet and Product content types")

| Content type structure                          | Product (SKU) content type                                                                                                                                                                                                                                      | Pet (non-SKU) content type                                                                                                                             |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Core content schema&#xA;(Reusable field schema) | Title<br>Summary<br>Thumbnail<br>Category                                                                                                                                                                                                                       | Title<br>Summary<br>Thumbnail<br>Category                                                                                                              |
| Dedicated content type fields                   | SKU<br>Product name<br>Description (rich text)<br>Price<br>Sale Price<br>Brand<br>Species (Taxonomy 1–10 tags)<br>Stock Status                                                                                                                                  | PetName<br>Species (Taxonomy)<br>Breed<br>Age<br>Gender<br>Size<br>Description (Rich text)<br>Price<br>Availability<br>Health Details<br>Special Needs |
| Relationships                                   | ImageAsset (1–10 photos)(required)<br>VideoAsset (0–3 videos)<br>Feature (0-10 Features) (reusable badges like "Eco-Friendly")<br>Related Products (0–6 related products)<br>Related Testimonials (Product Reviews)<br>Related Articles (for content marketing) | ImageAsset (1-10 photos)(required)<br>VideoAsset (0-3 videos)<br>Testimonials                                                                          |

> **Note:** These results are from an early stage of the content modeling process. The content types in the diagram do not yet include final definitions for data types, UI form components, or fields for editor-defined relationships. Complete content type definitions, including field-naming recommendations, are finalized at the end of the [content modeling MCP server's workflow](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md).

To view the relationships between suggested content types, ask the LLM agent to summarize them in a [Mermaid-style graph](https://mermaid.ai/open-source/intro/index.html). This graph shows the structure of the main and supporting content types.

> **Tip:** Depending on the agent you use to create the model, you may need to adjust the generated [Mermaid diagram](https://mermaid.js.org/) for proper display. For example, you might need to replace `\n` with `<br/>`.

The diagram illustrates relationships between nine content types, including _Pet_, _Product_, _ImageAsset_, _VideoAsset_, _Feature_, _Article_, _Author_, _Testimonial_, and _FAQ_.

In the commerce context, both the _Pet_ and the _Product_ content types relate to _Image asset_, _Video asset_, and _Testimonial_ content types. Additionally, the MPC server suggested that the Product content type relates to Feature, other related products for cross-selling, and article content type for content marketing.

You can see how these nine content types (_Pet_, _Product_, _ImageAsset_, _VideoAsset_, _Feature_, _Article_, _Author_, _Testimonial_, and _FAQ_) are related. Both _Pet_ and _Product_ content types connect to _ImageAsset_, _VideoAsset_, and _Testimonial_ types. The MCP server also suggests that the _Product_ content type relates to the _Feature_ (for additional details), other related _products_ (for cross-selling related products), and the _Article_ type (for content marketing).

![Relationships between content type](https://docs.kentico.com/docsassets/modules/prototype-with-content-modeling-mcp-server/content_type_relationships_mermaid_diagram.png "Relationships between content type")

> **Tip:** Not all commerce implementations need a _ProductSKU_ schema. If your commerce objects genuinely represent physical products requiring inventory tracking, include _ProductSKU_ as a reusable field schema alongside _ProductFields_ and other product-specific fields and schemas to ensure consistent SKU identification across all product-related content types.
>
> However, if you’re selling services, subscriptions, digital downloads, or other non-inventory items that don’t need traditional SKU tracking, a simple identifier field on each content type may be enough. Avoid adding schemas you won’t use to streamline the content model.

This material uses _Product_ with _SKU_ identification (_ProductSKU_) as an example to demonstrate solutions for common commerce modeling challenges.

In real projects like _Pawsome Pets_, you might need separate content types for different categories, such as _Pet_, _DogFood_, and _DogCollar_. This approach simplifies editing and tailors content types to specific data needs. We focus on universal patterns you can adapt to your catalog, rather than prescribing one “ideal” product model.