Avoid common modeling mistakes for commerce pages

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 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 with pre-configured widget zones to speed up content creation, even if you create content over API.

Establish governance rules for shared content from the start

Define clear ownership of Product vs. page content. Set up workflows and permissions 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.

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, workflows, and permissions to ensure your governance structure scales effectively with your expanding product catalog.