Group-level price overrides
Overrides applied above the account level: how many, how large, and who approved them.
Why it matters
Overrides above the account level bypass every rule below them. Counting them, and who approved them, is how central strategy and local execution are reconciled.
Act when
Frequent large-scale adjustments
Thresholds are set per business; the ones written as x and y are placeholders your team fills in.
What it may signal
Central strategy and local execution in conflict.
What to do
The templates that respond when this metric moves.
- Customer-specific pricingtemplate
- Contract renewal plantemplate
How it’s defined
- Formula
sum('Override value') / sum('List revenue')- Required context
- Price lists, Approval workflow
- Dimensions
- Group, Approver, Family
- Cadence
- Reviewed monthly
- Lineage
- Every value traces to the invoice line or governing record it was computed from.
- Use in
- Alerts: an agent watches it against a rule and alerts you when it trips.
Relevant industries
All industries
See Group-level price overrides on your commercial data.
We will show how Revomo defines, monitors and connects this metric to commercial action, using representative data or your own.