A pricing decision can be economically sound when approved and still fail by the time it reaches the customer.

I am Josh, and welcome back to the show.

This episode considers revenue management execution, where pricing, availability, discount, and capacity decisions move from commercial intent into systems, channels, sales activity, and operating practice.

A revenue management decision begins with an intended commercial position. Management may approve a price increase, protect capacity for higher-value demand, restrict a discount, change an availability rule, revise a channel rate, or reduce the amount of inventory released into a softer market. The financial expectation is attached to that decision before the transaction occurs.

Revenue management execution determines whether the decision survives the path into the market. A price increase may be approved while legacy customer terms remain unchanged in the billing system. A discount limit may be agreed while sales teams continue using local exceptions. Capacity may be protected in one system while another channel still has access to the inventory. A rate may change centrally while a branch, market, or partner continues selling against an older commercial position.

The outcome is a difference between intended economics and transaction economics. The approved price, availability rule, or discount policy can remain documented correctly while the customer receives a different commercial position. Identifying who is responsible for that difference is an essential part of revenue management execution.

Pricing governance determines who has authority to approve a decision or an exception. Pricing discipline describes whether the commercial rules are applied consistently. Execution depends on the operating sequence that follows, where the approved decision has to reach customer-facing systems, sales activity, channel settings, contracts, availability rules, and operating commitments.

That sequence can break at several points. A system may update late, a sales team may use an old price, a partner may receive incomplete instructions, a branch may keep a local promotion active, or an account may remain protected by a contract term that was overlooked when the broader pricing decision was approved. Each failure raises a practical question: who owns the correction, and how quickly does the information reach everyone affected?

Pricing execution and pricing performance can therefore weaken without a new pricing decision ever being made. Management may believe the commercial position is stable because the approved rates and rules have not changed, while actual transactions move through exceptions, manual workarounds, inconsistent channel updates, or local practices that produce a different result.

The financial consequence can remain hidden because each transaction still looks legitimate. The customer was quoted a price, the order was accepted, the service was delivered, and revenue was recorded. The weakness appears when the transaction is compared with the commercial position management believed was in force.

Execution also matters in capacity decisions. Management may intend to hold inventory for higher-value demand, while local teams release it early because they are measured on utilization or immediate revenue. The period can then show fuller capacity and weaker realized economics, even though the original revenue management decision was designed to protect margin.

Incentives can widen the execution problem when different functions are rewarded for different parts of the commercial outcome. A sales team may prioritize booked revenue, a branch may prioritize utilization, and an operating team may prioritize service completion, while the approved revenue management decision was designed to protect realized rate or contribution. Each function can act rationally against its own measure and still produce a transaction pattern that moves away from the intended economics. Resolving that conflict requires clear ownership of the commercial outcome, not simply another instruction to follow the approved price.

Demand forecasting can be affected as well because the observed sales record reflects the execution that occurred. If inventory was released too early, the resulting volume can make demand appear stronger at the lower rate. If capacity was withheld longer than intended, the observed sales may understate demand that could have been captured. Execution therefore shapes the commercial history later used to inform future pricing and capacity decisions.

Channel execution creates another source of variation. A central price may change while resellers, distributors, marketplaces, or booking channels update at different times. Customers then see inconsistent prices, and the business can create channel conflict through timing rather than through the pricing decision itself. The realized rate can vary simply because the same decision reached different channels on different days.

Revenue management execution becomes especially important when exceptions accumulate. One local exception may be commercially reasonable, while repeated exceptions across branches, accounts, channels, or customer groups can change the realized position of the wider business. The approved price still exists, yet the transaction record reflects a different commercial reality.

The useful evidence therefore sits close to the transaction. Management needs to know which price was intended, which price was offered, which exception was used, which channel carried the sale, which capacity rule applied, and which customer terms were actually executed. That record also needs to reach the people who can correct the problem, whether responsibility sits with revenue management, sales operations, account management, technology, or a channel partner.

Pricing discipline becomes visible in repetition. If the same override appears across many accounts, if one branch consistently uses older terms, or if one channel updates later than others, the issue is no longer a single exception. The response must address the recurring handoff or approval problem rather than treating every affected transaction as an isolated mistake.

By the time the period closes, those differences can appear as weaker price realization, unexpected mix, channel inconsistency, fuller capacity at weaker rates, or margin that does not match the decision management believed it had made. Effective execution depends on identifying discrepancies early, assigning responsibility and confirming that corrections reach every affected channel and operating team.

To learn more, read our Revenue Management Execution report, which examines the financial variance between approved pricing decisions and actual transactions, including the effects of overrides, delayed updates, and inconsistent implementation.

To discuss revenue management execution with our team, visit cityshiftfinance.com.

Thanks for tuning in.