Attribute-based products
Some products aren't a single SKU — they're a family of configurations. An attribute-based product models the family once: the rep selects attribute values at quote time, and pricing resolves from the chosen configuration.
How it works
Define a product with one or more attributes, each with its allowed values:
| Attribute | Values |
|---|---|
| Region | US, EU, APAC |
| Edition | Standard, Pro, Enterprise |
| Deployment | Cloud, Dedicated |
At quote time the rep picks a value for each attribute, and the line resolves to the right list price and structure for that combination — Pro / EU / Dedicated prices differently than Standard / US / Cloud, from a single catalog entry.
Why not just more SKUs?
The example above would otherwise be 18 SKUs (3 × 3 × 2) — 18 entries to keep priced, named, governed, and mapped at renewal. Attribute-based products keep:
- The catalog small — one product, one set of selling rules, one renewal rule.
- Pricing consistent — the price for each combination is defined in one place, not copy-pasted across SKU variants.
- Reporting clean — every sale of the family rolls up to one product, with attributes available as dimensions.
Use attributes when configurations share an identity and lifecycle; use separate SKUs when the offerings genuinely differ in what they are.
Attributes that drive behavior
Attribute selections aren't just labels — they can drive the rest of the quote:
- Pricing — each combination resolves its own list price, and can carry its own tier structure.
- Auto-selection — choosing a value can automatically attach companion products (select a Dedicated deployment, get its required infrastructure add-on). See Catalog overview.
- Approvals — approval rules can key off attribute values, so a non-standard configuration routes for review automatically.
- Downstream mapping — attributes flow into CRM line items and billing provisioning, so the configured variant — not a generic SKU — is what lands in your systems.
Lifecycle
Attribute-based products participate in the full lifecycle like any SKU: configurations carry into expansions and renewals with their selected values intact, and renewal substitution rules can remap retired configurations onto current ones.