---
title: Avoid common modeling mistakes for commerce pages
---

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

## Avoid common modeling mistakes

Don't create overly complex _wrapper pages_ by adding too many fields, and keep your wrapper focused on channel-specific needs.

### Plan for future channels from the start

Design your reusable _Product_ content type with multi-channel delivery in mind, even if your project needs only a website today. We recommend avoiding channel-specific assumptions when modeling the core product data. This makes it easier to add mobile apps, microsites, or email campaigns later.

### Never duplicate data between your reusable content and wrapper

Apply this rule: if data is universal and describes the product itself, it belongs in the reusable _Product_ only. Developers need to ensure that the data is properly displayed across different channels.

We've seen a common mistake where editors added the same _product description_ to the _product_ and then to a _product page_ (and to _emails_) using a _widget_. We recommend avoiding this data duplication. When editors copy some information from the _Product_ content type to the wrapper, you're defeating the purpose of the two-layer architecture. It creates confusion about which description is authoritative and makes content updates difficult.

Provide editors with a widget to display core product data, and introduce [widget properties](https://docs.kentico.com/guides/architecture/content-modeling/model-website-presentation-components.md) so editors can use the properties strategically to override or even personalize the product data when needed.

### Use Page Builder to present product data

Use _Page Builder_ widgets and templates for presenting product data on _wrapper pages_ rather than adding presentation fields to the _Content tab_. Widgets provide greater flexibility, support personalization for different audience segments, and enhance the editing experience. You can [create page templates](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-guide/design-website-content.md#design-content-using-templates) with pre-configured widget zones to speed up content creation, even if you create content through API.

### Establish governance rules for shared content from the start

Define clear ownership of _Product_ vs. _page content_. Set up [workflows](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md) and [permissions](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/page-permission-management.md) before you build a large amount of content. It's much harder to retrofit governance onto an existing content model than to build it in from the beginning.

> **Warning:** **Test the editing experience early.** Have developers or solution architects create sample content items using your proposed model. If the initial workflow passes, validate that the model makes sense from the editors' perspective. Ask editors to create a few products with real data and display this data on _website pages_ to identify any friction in the workflow. Iterate on the page model before you roll it out to your full team.

## Next steps

You've learned the architecture and modeling principles for commerce pages using the wrapper pattern, and you can implement it in your Xperience project.

Once your content model is in place, work with your development team to build the page templates and widgets that will present this product data on your website. As your content library grows, revisit your [folder organization](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md), [workflows](https://docs.kentico.com/documentation/developers-and-admins/configuration/workflows.md), and [permissions](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/page-permission-management.md) to ensure your governance structure scales effectively with your expanding product catalog.