Configuration Attributes

Some products need more than a quantity and a price — they need inputs. How many users? Which region? Is it billable? Configuration Attributes are how you capture that: the fields a rep fills in when configuring a product, defined by you per product, with the data type, validation, defaults, and pricing you choose.

You manage them in Product Manager: open a Product record, go to the Pricing tab, and select Configuration Attributes.

Defining an attribute

Each definition has:

  • Name — the label the rep sees.
  • API name — the stable key the value is stored under.
  • Display order — where it sits among the product’s attributes.
  • Data type — Picklist, Multi-Select Picklist, Text, Number, Date, or Checkbox. This drives how the rep supplies a value, which validation fields apply, and which pricing model the attribute uses.
  • Validation (type-specific):
    • Number — Min value, Max value, Decimal places.
    • Date — Min date, Max date.
    • Text — a Validation pattern (regex).
  • Default value (optional), Description.
  • Required and Active toggles.
  • Global attribute — share this attribute across products (see Global attributes).
  • Dimensionally variable (Pinion+) — let the value differ per MDQ segment (see Dimensional attributes).
The Edit attribute dialog showing Name, API name, Display order, Data type, Default value, Description, and the Required / Active / Global attribute / Dimensionally variable toggles
Defining a configuration attribute: name, data type, defaults, and the Required / Active / Global / Dimensionally-variable toggles.

How reps supply a value

The Data type decides what the rep sees in the configurator:

  • Text / Number / Date — the rep types or picks a value, validated against the rules you set.
  • Checkbox — a single on/off toggle.
  • Picklist / Multi-Select Picklist — the rep chooses from values you define. Only these two value-backed types have a values list.

Pricing an attribute

Selecting or entering a value can adjust the line — this is config-attribute pricing. Each data type has its own pricing model. (How the result flows into the final line price is covered in Pricing Methods.)

Picklist / Multi-Select — per-value pricing

For a Picklist or Multi-Select attribute, manage its options under the definition. Each value has:

  • Label (what the rep sees) and Value (the stored value);
  • Price override ($) — set the line’s price for this value outright — or a Price delta to adjust it. The delta carries an Amount ($) / Percent (×) unit selector, so you can add a flat amount or a percentage;
  • Display order and an Active toggle.
The Edit value dialog for a picklist value showing Label, Value, Price override, Price delta with an Amount/Percent unit selector, Display order, and Active
A picklist value — each can carry a Price override ($) or a Price delta (Amount or Percent). This is config-attribute pricing.

Number — pricing bands

A Number attribute is priced with bands — ranges of the entered number, each with its own rate. Each band has:

  • Lower bound and Upper bound — inclusive. Leave the lowest band’s lower bound blank for a floor of 0; leave the highest band’s upper bound blank for an uncapped top.
  • Per-unit rate ($) — the contribution is entered value × this rate.
  • An optional Price override ($) or Price delta (with the Amount/Percent unit) that layers onto the rate — set override or delta, not both.
  • Display order and an Active toggle.
The New pricing band dialog showing Lower bound, Upper bound, Per-unit rate, Price override, Price delta with unit selector, Display order, and Active
A Number-attribute pricing band: a value range, a per-unit rate (contribution = value × rate), and an optional override or delta layered on.

Checkbox — true / false pricing

A Checkbox attribute prices two sides independently:

  • When checked (true) — a Price override ($) or a Price delta (Amount/Percent).
  • When unchecked (false) — the same pair.

On each side, override and delta are mutually exclusive, and either side may be left blank for no price effect.

The checkbox pricing editor with a When checked (true) section and a When unchecked (false) section, each with Price override and Price delta fields
Checkbox pricing — set a price effect for the checked and/or unchecked state; override and delta are mutually exclusive on each side.

Global attributes

Toggle a definition Global to reuse the same attribute across many products instead of redefining it on each. When global, an Apply to products picker lets you choose which products it’s assigned to; the definition’s primary product is always assigned.

Dimensional (per-segment) attributes — Pinion+

By default an attribute is set once per line. Mark a definition Dimensionally variable to let its value differ per segment of a multi-year / MDQ deal — for example a support tier or seat count that changes year over year. This is a Pinion+ capability and applies to products that have dimensions configured.

In the configurator’s segment grid, Pinion uses a first-segment-defines model:

  • The first segment defines the value — its cell shows the actual attribute values and writes the line-level value.
  • Subsequent segments default to “Inherit” (showing segment 1’s value, styled as inherited). A rep can override an individual segment, or clear the override to fall back to inherited.
  • The effective value resolves segment override → segment 1 (line) → definition default.
An MDQ segment grid across Year 1 / Year 2 / Year 3 with dimensionally-variable Seat Tier and Region rows — Year 1 defining (Executive, US), Year 2 overriding (Standard, APAC), Year 3 inheriting
A dimensionally-variable attribute across MDQ segments — Seat Tier and Region carry a 'varies by segment' badge: Year 1 defines (Executive / US), Year 2 overrides (Standard / APAC), Year 3 inherits. Each segment's Total still reads $100.00 — the value varies per segment but doesn't yet move the price (see below).

Activating and removing

  • Toggle a definition, value, or band Active / Inactive — inactive ones stop applying without losing the definition.
  • Removing a definition removes it cleanly; you don’t have to delete its values or bands first.
The configurator's Configuration Breakdown editor for Acme Seat License — three rows combining Seat Tier, Region, and a Billable checkbox, each with its own quantity, unit price, and total
The payoff: configuration attributes in the configurator's Configuration Breakdown editor — each combination of Seat Tier / Region / Billable carries its own quantity, unit price, and line total, and they sum to the line's configuration total.