---
title: Introduction to commerce content modeling
---

> 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).

This module guides you in designing a full commerce content architecture in Xperience by Kentico. You will follow a step-by-step approach, starting with core product modeling and building up to full-page presentation.

> **Info:** We recommend that you complete the [Content modeling guide](https://docs.kentico.com/modules/content-modeling-guide.md) before taking this module.

You will begin by modeling a **standard product content type** that doesn't require _commerce capabilities_, like pricing or shipping. Next, you will look at **products with SKUs** that represent traditional products. After that, you will look into modeling **product page content types**, which connect your content to your audience. Finally, you will explore the _presentation layer_, using commerce widgets and page templates in _Page Builder_ to bring everything together.

The module ends with a **guided walkthrough of the pet store example** from the XbyK Training guides project. This part is more technical, but very straightforward. You will see a real-world example of how the modeling decisions shape the actual code.

In the end, you will have a clear, repeatable framework for architecting commerce content in Xperience – one grounded in **atomic content modeling** principles and validated against a working reference implementation.