Product Families (Product Models)
Build durable product family architecture so every product starts with the right structure, variant logic, and required data.
Common paths
/{workspaceSlug}/settings/product-models/{workspaceSlug}/products/{workspaceSlug}/products/{productId}What a product family controls
In Stackcess, product families are implemented as Product Models. A family controls which fields matter, how variants behave, and which completeness checks are realistic for a class of products.
- Families define product shape, not campaign or season structure.
- Family design impacts onboarding speed, import mapping, and publish quality.
- One poorly designed family can create repeated data cleanup across all channels.
Family boundary decision framework
Create a new family only when structural differences are real and persistent. Over-splitting families creates admin overhead and inconsistent data.
- Split when required fields are substantially different.
- Split when variant axes differ (example: size/color vs capacity/voltage).
- Split when compliance requirements differ by category.
- Do not split solely for merchandising teams, temporary launches, or partner-specific exports.
Variant strategy per family
Define parent/variant behavior before teams create records. This prevents rework when converting standalone records into variant structures later.
- Identify parent-only fields versus variant-level fields early.
- Keep axis definitions stable and business-meaningful (size, color, finish, pack count).
- Document inheritance expectations so editors know when overrides are allowed.
- Validate a sample parent plus three variants before launch.
Family launch checklist
Before enabling a new family for broad use, run this checklist with product ops and channel stakeholders.
- Define family scope and in-scope product examples.
- Confirm required fields and identifier strategy.
- Map field groups and editor order for daily workflows.
- Test completeness in at least two market/channel contexts.
- Approve migration/import mapping and train editors.
Change management for live families
Treat live family changes as controlled releases. Field or axis changes can affect exports, integrations, and partner consumption.
- Prefer additive changes over destructive edits.
- Deprecate and migrate old fields before removal.
- Run impact checks on integrations and templates before publishing schema changes.
- Maintain a family version log for auditability.