Documentation
Product Model
Structure parents, variants, attributes, assets, and channel-specific outputs.
Best for: PIM admins, merchandisers, and taxonomy ownersLast updated: 2026-03-21
Guide overview
A strong product model should support operational ownership, not just field storage. Start with the entities and relationships needed for governance, localization, and downstream publishing.
Separate shared parent content from variant-level sellable attributes and identifiers.
Define attribute groups around operational jobs such as onboarding, QA, compliance, and publication.
Reserve channel overrides for true channel differences so the base record stays reusable.
Attach assets and supporting evidence to the same governance path as product content.
Related docs and next steps
Need implementation support?
Use the docs as your rollout blueprint, then connect them to pricing, tools, and solution pages when you need a deeper implementation plan.