When Does a Pricing Exception Become a Pricing Strategy
A pricing exception rarely looks risky on day one. A manager matches a nearby competitor. A regional leader approves a temporary discount after road construction hurts traffic. A revenue manager pauses a planned increase because a facility is behind on occupancy.
Each decision can make sense. The problem starts when those decisions stack up faster than anyone can see.
That is how a self storage pricing strategy can drift. Not through one bad rate decision, but through hundreds of reasonable exceptions that stop being exceptions.
Exceptions are part of good revenue management
A pricing system that allows no judgment will fail in real markets.
Self-storage is local. Demand changes by trade area, season, unit mix, customer segment, and street-level competition. Two stores in the same metro can behave differently because one has climate-controlled 10x10s near full occupancy while another has excess drive-up 10x20s. A new competitor can open across the road. A large business customer can need short-term flexibility. A construction project can block access for months.
That is why exceptions exist.
Common examples include:
Manual overrides to adjust a posted street rate
Local promotions for lease-up, weather disruptions, or low-visibility facilities
Competitor matching when a nearby operator cuts rates
Manager discretion for save attempts or customer-specific situations
Temporary discounts for slow-moving unit types
Delayed rent increases after service issues or access problems
Regional adjustments when a market behaves differently than expected
These tools are not the enemy. They can protect occupancy, reduce churn, and give local teams room to respond to facts that a model may not capture right away.
The risk comes from weak visibility. If leadership can see the decision, the reason, the duration, and the result, an exception remains governed. If not, the exception becomes a shadow pricing system.
The real risk is not one override. It is pattern blindness.
Most pricing breakdowns are not dramatic. They are quiet.
A manual override may reduce a rate by $10 for a valid reason. A local promotion may run for 30 days, then get renewed because move-ins improved. A manager may match competitors on 10x10 units, then apply the same thinking to 5x10s. A regional leader may allow one facility to hold rates because occupancy is below target, while another similar facility follows the standard rate plan.
No single action looks wrong. Taken together, they create a pricing pattern that nobody approved.
This is where pricing governance matters. Governance does not mean blocking every local decision. It means creating a clear record of who changed what, why they changed it, how long the change should last, and whether it worked.
Without that record, leadership sees results but not causes. Occupancy may hold, but at a lower achieved rate. Move-ins may improve, but discounts may attract short-stay customers. A store may look stable, but only because its team has trained the market to wait for concessions.
Pricing exceptions create two kinds of cost.
The first cost is obvious. The facility earns less on affected rentals.
The second cost is harder to see. The organization loses a clean read on demand. If one store follows the rate plan and another store overrides half its quoted rates, comparing performance becomes unreliable. The difference may not be customer demand. It may be local discount behavior.
That weakens rate management across the portfolio.
A hypothetical portfolio shows how drift happens
Consider a 60-store self-storage portfolio across several U.S. markets.
The company has a centralized pricing process. It uses occupancy, unit availability, recent rentals, market position, and rate history to set street rates and rent increases. Regional leaders can approve exceptions. Store managers can request overrides for local reasons.
In January, the process looks disciplined.
By March, local exceptions increase.
One facility near a large road project starts offering a temporary first-month discount because traffic is down. A second store matches a competitor that opened with aggressive web rates. A third facility gives managers more discretion because occupancy in 10x15 drive-up units is below plan. A fourth pauses increases for long-term customers after several access gate issues.
Each choice is reasonable.
By June, the portfolio review gets harder.
Leadership sees three similar facilities with similar occupancy, similar unit mix, and similar market demographics. Yet they are behaving differently.
Facility A keeps pushing street rates and accepts slightly slower move-in volume.
Facility B matches competitors on selected units and fills faster at lower rates.
Facility C uses manager discretion often, but only on phone reservations.
Facility D keeps a promotion active beyond its original end date because the team believes it helps conversion.
Six months later, no one can clearly explain why these stores now follow different pricing behavior.
The original reasons were legitimate. The problem is that the decisions were not consistently documented, reviewed, or retired.
Some questions become difficult to answer:
Which exceptions were temporary, and which became permanent?
Which discounts improved net rental activity rather than shifting demand forward?
Which competitor matches responded to a real threat, and which followed a one-off advertised special?
Which managers use discretion rarely, and which use it as part of normal leasing?
Which facilities have rate plans shaped more by local overrides than by portfolio strategy?
This is the point where pricing exceptions become unofficial policy.
No one announced a new pricing strategy. The portfolio created one anyway.
Duration is where many exceptions turn into policy
Temporary discounts create persistent risk when no one owns the end date.
A discount for 30 days is different from a discount that lasts until someone remembers to remove it. A competitor match for a specific unit type is different from a habit of matching any lower advertised rate. A manager-approved concession for a unique lease is different from a standing permission to negotiate every rental.
Duration matters because customer behavior adapts.
If prospects learn that the posted rate is flexible, the posted rate loses authority. If store teams learn that overrides are rarely questioned, overrides become part of the sales process. If regional leaders renew temporary promotions without measuring outcomes, promotions become the default answer to slow demand.
That does not mean temporary discounts are bad. They can be useful. They need a start date, an intended end date, a reason, and a follow-up review.
The review does not need to be complicated. It should answer direct questions:
Review area | What to look for |
Frequency | How often exceptions occur at each facility, unit type, manager, and region |
Rationale | Whether the stated reason is specific, current, and tied to a measurable condition |
Duration | Whether the exception ended on time, renewed, or remained active without review |
Outcome | Whether the result improved net rentals, occupancy, achieved rate, or customer retention |
Concentration | Whether exceptions cluster in certain stores, unit types, channels, or teams |
The goal is not to create universal thresholds. A high-growth lease-up store may need more exceptions than a mature facility near full occupancy. A storm-affected market may need flexibility that would not make sense elsewhere. A store with a new competitor next door may need different treatment than a store with weak internal sales execution.
The right question is not, “How many exceptions are allowed?” The better question is, “Can we explain the exceptions we made and what happened next?”
Documentation protects judgment instead of replacing it
Many teams resist governance because they hear it as control. That is a mistake.
Good governance protects local judgment. It gives managers and regional leaders a way to act on local facts while keeping the portfolio from drifting into hidden policy.
A useful exception record does not need long comments. It needs enough structure to make later review possible.
For example, an exception request might capture:
Facility and unit type
Current recommended rate and requested rate
Reason for the change
Competitor or market condition, when relevant
Approval owner
Start date and planned review date
Expected outcome
Actual outcome after review
This creates a common language across the portfolio. “Competitor matching” becomes more than a label. It can identify whether the competitor was same unit type, same features, same access, same move-in terms, and same customer channel. A local promotion can show whether it applied to web leads, walk-ins, specific unit sizes, or all rentals.
That detail matters because self-storage pricing is easy to compare poorly.
A $99 web rate from a nearby facility may not be equal to a $119 rate if the cheaper property has lower security, no climate control, limited access, required insurance fees, or a short promotional term. A competitor may advertise a low starting rate while using faster existing-customer increases later. Matching that rate without context can give away value.
Documentation also helps separate market problems from execution problems.
If one facility asks for frequent discounts because competitors are cheaper, the market may need review. If five facilities under one regional team use far more manager discretion than comparable locations, the issue may be process, training, or approval culture. If one unit type draws repeated concessions, the issue may be unit mix, street rate, online merchandising, or true demand.
Governance makes those patterns visible.
The portfolio should review patterns, not just approvals
Approving exceptions one by one is not enough.
A single approval answers, “Is this request reasonable today?” Portfolio review answers, “What are our exceptions teaching us?”
Those are different questions.
A regular review should look across facilities and time. It should examine where exceptions concentrate and whether those concentrations make sense.
Useful review angles include:
Exception frequency
Count the number of overrides, promotions, matched rates, delayed increases, and manager-approved discounts. Compare across similar facilities, markets, and unit types. The count alone does not prove good or bad. It flags where to ask better questions.
Rationale quality
A reason like “market pressure” is too vague by itself. A better reason names the condition. For example, “new competitor opened within two miles with 10x10 climate-controlled web rates 15 percent below our current street rate for first-month rentals.” Specific reasons allow later validation.
Duration behavior
Track whether exceptions expire, renew, or become open-ended. Repeated renewals may signal that the base rate plan needs change. They may also show local teams using temporary tools to avoid a harder pricing decision.
Outcome measurement
Measure what happened after the exception. Did the facility gain rentals it would not have captured? Did achieved rate fall without enough occupancy lift? Did discounts lead to shorter stays? Did delayed increases improve retention enough to justify the revenue tradeoff?
Concentration by person or region
Exceptions often reflect culture. Some managers negotiate more. Some regional leaders approve more. Some teams use discounts as a save tool, while others protect rate integrity. Concentration does not assign blame. It shows where practices differ.
Repeat exceptions on the same unit type
Repeated exceptions on the same size may mean the recommended rate is wrong. It may also mean the sales team has learned to discount that size first. Either way, repeated behavior deserves review.
This is where self storage analytics should support human review. Data can show patterns that individual operators miss. Humans can interpret the local reasons behind those patterns.
Governance should avoid false precision
A portfolio does not need a universal rule that says every facility gets the same number of exceptions. That can create bad incentives.
If the limit is too strict, managers may avoid needed local action. If it is too loose, exceptions become routine. If the rule is mechanical, teams focus on staying below the line rather than making the right decision.
Better governance uses ranges, comparisons, and review prompts.
For example:
Compare exception frequency among peer facilities instead of applying one fixed limit.
Review exceptions that renew multiple times instead of banning renewals.
Look for unusual concentration by unit type, facility, channel, or approver.
Ask whether the original reason still applies.
Ask whether the pricing system should adjust instead of relying on repeated overrides.
This keeps governance practical. It also respects the difference between judgment and noise.
Local teams often see issues early. A manager may notice that callers mention a new competitor before the data shows lost demand. A regional leader may understand why a property near a university behaves differently in summer. A revenue manager may spot that one unit group needs a temporary correction.
Governance should capture those signals, not silence them.
The best systems create a feedback loop. Local judgment informs pricing decisions. Portfolio review tests whether those decisions produced the intended result. The rate plan then absorbs what the organization learned.
That is how exceptions strengthen strategy instead of replacing it.
FAQ
How can leadership tell when pricing exceptions are becoming unofficial policy?
Look for repeated exceptions with the same reason, same facility, same unit type, same channel, or same approver. If the same adjustment keeps recurring and the standard rate plan never changes, the exception has likely become part of normal pricing behavior.
Should store managers have discretion to discount rates?
Yes, when discretion is governed. Managers often know real local conditions before they appear in reports. The key is to document the reason, duration, approval path, and outcome so local judgment does not turn into hidden policy.
Are competitor matches always a problem?
No. Competitor matching can protect rentals when the comparison is valid. It becomes risky when teams match advertised rates without checking unit features, promotion terms, fees, access, availability, and customer segment.
What should an exception review include?
A practical review should examine frequency, rationale, duration, outcomes, and concentration. It should show where exceptions occur and whether they improved performance. It should not treat every exception as a violation.
How often should a portfolio review pricing exceptions?
The right cadence depends on portfolio size, rate-change frequency, and market volatility. Many operators benefit from a regular monthly or quarterly review, with faster checks during heavy leasing seasons, lease-ups, or competitor disruptions.
The takeaway is discipline without rigidity
Pricing exceptions are not failures. They are part of operating a local, competitive, month-to-month business.
The failure is letting exceptions become invisible.
A strong revenue process does not remove human judgment. It gives judgment a record. It shows which decisions were made, why they were made, how long they lasted, and what changed afterward.
That visibility protects pricing discipline. It also helps leadership see when repeated exceptions are no longer isolated decisions. They are signals from the field. Sometimes they point to a local market condition. Sometimes they point to a rate plan that needs adjustment. Sometimes they point to inconsistent practices across similar stores.
A.R.M.S. Revenue Intelligence was built around that reality. Its approach keeps revenue decisions governed, reviewed by people, and connected to portfolio patterns rather than isolated approvals. To see how that works in practice, visit A.R.M.S. Revenue Intelligence.
The question is not whether exceptions should exist. They should. The better question is whether the organization can still explain them six months later.
Comments