Common problems and patterns iWeb sees.
How this system fits next to commerce, PIM and ERP.
Questions we get asked.
When is a separate CMS worth it for ecommerce?
When editorial volume, brand campaigns or multi-brand publishing is real. Many estates run well on the native commerce CMS without a separate system.
Where does the CMS / commerce boundary sit?
Product data lives in PIM and the commerce platform. CMS owns editorial: brand, campaign, support. Mixing the two usually leaks product data into editorial templates and back again.
Which commerce platforms can a CMS sit alongside?
The pattern is platform-agnostic. iWeb CMS work has run mostly alongside Adobe Commerce and Magento; the same boundary applies on other commerce platforms with a CMS that supports the content model.
How does SEO metadata get owned?
Per content type. Editorial pages own their metadata in the CMS; catalogue pages own theirs in the commerce platform. Rules are governed and tested rather than hand-edited per page.
Can editors publish without engineering involvement?
Yes, where the content model is governed. Block templates, review workflows and a defined editorial role keep publish paths safe.
When is the native commerce CMS enough?
When editorial volume is limited, campaigns are sparse and brand publishing is light. A separate CMS earns its place when those things are real, not by default.
Which CMS systems does iWeb work with?
The decision is client-led. iWeb has worked with Contentful, Storyblok and Adobe Experience Manager alongside Adobe Commerce and Magento, with the boundary held cleanly between editorial and product data.
How does the CMS connect to commerce and PIM?
The CMS owns editorial. The PIM owns product attributes, media and channel rules. The commerce platform reads from both. Product data does not leak into editorial templates.
What are the typical CMS failure modes?
Content models that quietly absorb product data, editorial publish paths that bypass review, and SEO metadata owned in two places at once. iWeb names ownership per content type rather than per page.
Can iWeb take over an existing CMS?
Yes. The team reads the content model, the editorial workflow and the integrations in place first, then writes down what to keep, stabilise or change.
Where does SEO metadata live in a CMS-plus-commerce estate?
In the CMS for editorial pages and in the commerce platform for catalogue pages. The rules are governed per content type and tested rather than written down once and forgotten.
How is CMS kept stable in long-term support?
Editorial publish paths are monitored, content models are versioned and changes go through review. The CMS is treated as a platform, not as a spreadsheet.