Module: Commerce content modeling
8 of 38 Pages
Define fields for the reusable SKU product content type
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.
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.
Additional details, such as the number of websites, channels, content volume, and reuse strategy, help the MCP agent design an appropriate content model.
After collecting all the details, the server summarizes the results and proceeds to the next phase.
Design content types
The MCP server uses your input and Kentico’s best practices 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.
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 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.
|
Content type structure |
Product (SKU) content type |
Pet (non-SKU) content type |
|
Core content schema (Reusable field schema) |
|
|
|
Dedicated content type fields |
|
|
|
Relationships |
|
|
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.
To view the relationships between suggested content types, ask the LLM agent to summarize them in a Mermaid-style graph. This graph shows the structure of the main and supporting content types.
Depending on the agent you use to create the model, you may need to adjust the generated Mermaid diagram 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).
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.