Price Increase Management

Announce five points. Land five points.

Most increases leak away through exceptions, overrides and quiet grandfathering. Plan the increase by segment, decide up front who is capped or held to contract, route every exception for approval, and measure how much of it held.

Price & Quote Management/Annual List Increase/Contractor 2026

The 2026 increase applied to one segment's price list, with caps, contract holdouts and one exception in review. The data is illustrative.

The plan
A 2026 list increase effective January 5: 5% for contractors, 4% wholesale and 7% retail, 5.0% on average.
What it shows
The Contractor 2026 list after recalculation. 5,720 of 6,240 lines move up, 520 stay at contract prices, and Harbor Mechanical is held to its 3% cap.
What happens next
38 exceptions below plan wait in Pricing Review while the other 6,202 lines are approved. Then the list publishes, and the quarter is measured.
01 · Plan the increase

Plan the increase before you announce it.

Set the increase by segment in a decision table, then test it. As announced, 5.0% adds about $168K of gross margin a month. After contract holdouts and account caps the plan is 4.6%, worth about $155K a month, and that is the number to hold the business to.

Planning & Forecasting / Decision Models / 2026 increase test

A decision model comparing the increase as announced with the increase after caps and holdouts. The data is illustrative.

  • Scenarios against a baselineName each case, override its inputs, and compare every scenario on one chart.
  • Know what the caps costThe gap between the two increase lines is what holdouts and caps give away: about $13K a month here.
  • Your volume responsePrice elasticity is an input you set or estimate from your own history. Here it is -0.6.
Decision table

The increase by segment, as one table.

One rule per segment returns its increase, valid for 2026. “Any” matches every value, and a catch-all rule covers the rest. The price lists look the increase up.

Simulate

Check which rule a line will use.

A retail customer buying brass valves matches rule 3, so its lines take the 7.0% retail increase.

How it works: decision tables and scenarios
Decision models
A decision model runs on your own data. Only the baseline scenario is built in; every other case is one you name. Results update when the model runs, on demand or when its source refreshes.
The 4.6% input
The capped scenario’s 0.046 price change is the planned increase after caps and holdouts, weighted by 2025 revenue and entered as an input.
Rules by segment
The decision table returns an increase for each segment and product group, valid from January 5 to December 31, 2026. The priority number sets the order rules are tried.
Estimates, not promises
Expected results depend on the elasticity you use. Testing a lower and a higher value shows how much the answer depends on it.
02 · Set caps and exceptions

Decide who is capped, held or excepted, on the record.

Columns on the commercial model apply the plan, hold contract lines at their price and cap strategic accounts. When someone agrees a lower increase by hand, it stays, and it is marked as an exception.

Increase columns

The rules of the increase, written as columns.

Planned Increase comes from the decision table. Max Increase is zero for contract lines and the account cap where one exists. Applied Increase takes the lower of the two, and Increase Basis says why.

Exceptions

An agreed exception survives the next recalculation.

Lakeside Contractors’ elbow was lowered to 2.5% by hand. With Preserve Edits the cell keeps that value when the list refreshes, and Increase Basis reads Exception.

Decision Optimization Early access

Or have Revomo propose the increase line by line.

Instead of one rate per segment, set the goal (the $1.86M a year the plan is worth) and the same guardrails, and get a recommended increase for every customer and product, each explained and sent through the same approval workflow.

A prototype of the Decision Optimization workspace, in early access with selected customers. Decision optimization workflow: patent pending.

How it works: contracts, caps and exceptions
Contract lines
Contract prices come from your contract data in Revomo, as a dataset or kept with Contract Pricing & Renewals. Without it, the formula has nothing to hold those lines to.
Account caps
Caps are a dataset your team maintains. A customer without a cap falls back to the planned increase.
Lookups bind by name
Renaming the decision table or a dataset can leave a column empty. Lineage shows what depends on a source before you change it.
Decision Optimization
In early access with selected customers. It uses guardrails like these, and its recommendations publish only through your approval workflow or limits you agree in advance.
03 · Approve and publish

Approve the exceptions, then publish once.

When the list recalculates, an automation approves every line that is not an exception. The 38 exceptions wait in Pricing Review, and the approved list goes to the people and systems that use it.

Approval workflow

Only exceptions wait for a person.

Review runs per line item. Lines whose Increase Basis is not Exception are approved when the list recalculates, and the pricing manager is notified about the rest.

Publish

Send it where prices are used.

Export the approved list to a connected CRM as a background job, generate a price notice as a document, or share a live link.

On the record
  • Effective dateContractor 2026 carries its effective date, January 5, 2026, in its header.
  • Previous revisionThe 2025 prices stay as the previous revision, so every new price shows its change against them.
  • Audit logEvery hand edit, approval and reason, with who made it and when.
How it works: approvals and publishing
Your policy
States, actions and who may take each one are set in the lifecycle policy on the commercial model. Approval steps do not carry deadlines today.
Many lines at once
To change many lines yourself, a bulk update filters records, sets a field by value or formula, simulates the effect, then submits it for approval.
Where prices go
Exports reach Databricks and Salesforce today and run as background jobs. For your ERP, the method is agreed in the Activation and Success Plan.
Quotes
Quotes built on the same price lists start from the new prices.
04 · Measure what held

Account for every point of the increase.

After the first quarter, the 2026 increase had realized 4.4% against 4.6% planned and 5.0% announced. The bridge shows where each point went: 0.4 to decisions made up front, 0.2 lost after the list was published.

Dashboards / 2026 increase

Planned against realized by segment, and the bridge from the announced increase to the realized one. The data is illustrative.

  • Planned against realizedBy segment, customer or product family, from invoice lines joined to the published list.
  • The old price, foundOrders still invoiced at the 2025 price are their own step in the bridge, 0.1 points here.
  • Alerts on refreshAn automation alerts the segment owner when a customer’s realization gap moves by a point or more since the last refresh.
How it works: measuring realization
A view you build
Realization is a view that joins invoice lines to the published price list and computes the increase each line carried. You define the measure; Revomo does not ship a fixed one.
When it updates
The view and the dashboard update when their data refreshes, on a schedule or on demand.
Into the next cycle
The customers and families that fell short are where next year’s plan and caps start.
05 · What powers it

What powers it.

The capabilities that do the work, what every subscription adds, and where to start.

Capabilities it uses

In every subscription

Start here

Related solutions: Cost Recovery & Repricing, Cost, Tariff & Freight Recovery, Price Realization & Pricing Leakage.

FAQ

Common questions

How do you stop the exception spiral without freezing the business?

By putting exceptions on the record rather than banning them. An exception is a hand edit to a line’s increase: it survives the next recalculation, a formula marks it as an exception, and it waits for the approver your workflow names while the rest of the list moves on. Concessions still happen, but each one is visible, attributed and measured against the increase you announced.

What about accounts that were quietly grandfathered years ago?

They show up. Every line that does not take the planned increase says why, such as a contract price or an account cap, and realization by customer shows who is still paying old prices. Grandfathering becomes a decision someone makes and owns. Where your contract terms are in Revomo, contract lines can be held out of the increase at their contract price.

Will sales accept this?

Sales gets fewer surprises. Reps see the new price and the reason behind it, the plan, an account cap or a contract, before customers do. Only exceptions wait for a person, routed by the approval workflow to the approver it names, and the reason for every decision stays on the record.

Can we model the increase before we announce it?

Yes. A decision model compares scenarios, such as the increase as announced and the increase after caps and contract holdouts, against a baseline, using a price elasticity you set or estimate from your own history. The results are estimates, so test a range before committing.

How do we know how much of the increase actually held?

By comparing what was invoiced with what was published. A view joins invoice lines to the published price list, and a dashboard shows planned against realized by segment, with a bridge that separates planned holdouts from approved exceptions and orders still invoiced at the old price. It updates when the data refreshes.

Does Revomo change the prices in our ERP?

It depends on the system. Approved price lists export to connected Databricks and Salesforce destinations, generate as documents, or share as a live link; for your ERP, the method is agreed in the Activation and Success Plan. Orders still invoiced at the old price show up in the realization view, so a missed update is found.

Can Revomo recommend the increase line by line?

In early access. Decision Optimization recommends a price for every customer and product line that meets a goal you set while holding your guardrails, such as contract prices and account caps, and explains each one. Recommendations go through the same approval workflow. It is available to selected customers.

Make the next increase land.

Bring last cycle’s announced and realized increase. We will show you where it leaked, and how the next one holds.

Plate B2 · Series 2026