
The Pricing Exceptions Living in Your Head
TL;DR: A pricing exception is any price that differs from your list price, granted for a reason that exists only as a memory, and the fix is a one-page record that names the exception, the rule behind it, and who can approve it. Repeat customers, rush work, and special requests each create their own quiet exception, and without a record, the price lives in one head. Writing down the rule lets you keep charging what you already charge while finally knowing why you charged it.
Key Takeaways
- A pricing exception is a price that differs from the list price, granted for a specific and often unstated reason.
- Exceptions accumulate through three common channels: repeat customers, rush work, and special requests.
- The risk is that no one besides the person who gave the discount can explain or repeat it.
- A one-page format with three fields, the exception, the rule behind it, and who can approve it, closes the gap without requiring a pricing overhaul.
- This approach stays neutral on how much to discount. It only asks that the reasoning be written down somewhere other than one person’s memory.
How Pricing Exceptions Start
Pricing starts with a list price, the standard rate posted or quoted before any negotiation happens. Then a regular customer asks for a break, a job needs to move faster than normal, or a customer wants something slightly different from the standard offer. Someone says yes, the job gets priced, and the exception is made. Nobody writes it down because in the moment it feels like a one-time call, not a pattern.
The problem shows up later, when a second employee quotes the same regular customer at full list price, or a different rush job gets turned down for a surcharge the first one never had. At that point, the business has two different answers to the same question, and the customer notices before anyone on staff does. That inconsistency is the rework: a confused customer, a redone quote, or a manager pulled in to settle a dispute that a written rule would have prevented.
The exception itself is rarely the issue: the reason lives in one person’s head, unrecorded, and nobody else can reproduce the judgment that produced it.
The Three Channels Where Exceptions Pile Up
Exceptions rarely come from nowhere. They tend to form along the same three paths, each with its own logic and its own risk if that logic goes undocumented.
Repeat Customers
A repeat customer, someone who orders often enough to expect a different rate than a first-time buyer, usually earns a break through volume or tenure. The logic might be sound: more orders means lower cost to serve, so a lower price makes sense. The trouble starts when the discount outlives the reason, continuing after order volume drops, because nobody set a condition for when it should end.
Rush Work
Rush work, a job compressed into a shorter timeframe than standard, often gets a surcharge, but sometimes gets a discount instead, when a business wants to keep a slot filled or a client happy. Either direction can be reasonable. Neither is reasonable if the next rush request gets a different answer because a different person is handling it.
Special Requests
A special request, a modification outside the standard product or service scope, creates the messiest exceptions because each one can look unique. That uniqueness is exactly why it needs a rule. Without one, every special request becomes a fresh negotiation instead of an application of a known standard.
The price lives in one head, and that head is not always in the building when the next quote goes out.
What Belongs in a One-Page Pricing Exceptions Record
A pricing exceptions record does not need software or a formal policy manual. It needs three fields, filled in consistently, for every deviation from list price.
| Field | What it captures | Example (illustrative) |
|---|---|---|
| The exception | What price was given and to whom | 10 percent off list for a named repeat account (example) |
| The rule behind it | The condition that justifies the exception | Applies to accounts ordering monthly or more often |
| Who can approve it | The role authorized to grant or revoke it | Office manager, reviewed quarterly |
The rule behind the exception turns a one-time favor into a policy someone else can apply.
This format stays deliberately neutral on what to charge or how deep a discount should run. It asks only that the condition be written somewhere a second person can find it. A rule with a stated condition becomes something a second person can apply without guessing.
Keep the record in one place, reviewed on a set schedule rather than left to accumulate indefinitely. A quarterly review catches exceptions that outlived their original condition, like a rush surcharge waived for a client whose rush orders stopped months ago.
I recommend starting the record with whatever exceptions are already active, rather than waiting for a clean slate. A business with many running exceptions will find the first pass the hardest, since the oldest ones often have no remembered reason left.
Who Should Be Able to Approve an Exception
An exception approval structure should name a specific role, not a specific person, so the authority survives staff turnover and so a quote never waits on one individual’s availability. For small operations, this is often the owner or a single manager. For larger ones, it can be tiered by discount size, with small adjustments approved at the front line and larger ones requiring a second signature.
Who can approve it matters as much as what the exception is, because an unauthorized discount creates the same confusion as an undocumented one.
The trade-off is speed against control. A single approver keeps exceptions consistent but creates a bottleneck when that person is unavailable and a quote is waiting. Multiple approvers move faster but need the same written rule in front of each of them, or the inconsistency returns through a different door. I recommend one approver for operations under a handful of staff, and a two-tier structure, small exceptions at the front line, larger ones escalated, once the team crosses that size.
What to avoid: letting approval authority default to whoever happens to be quoting that day. That turns every exception into a fresh negotiation and guarantees two customers will eventually compare notes and get two different stories.
In Practice: Logging a Standing Discount
Situation: An office manager realizes a long-standing customer has been getting a lower rate for over a year, and nobody currently on staff remembers exactly why.
Steps:
- Pull the customer’s order history and note the current rate against the list price.
- Ask the longest-tenured staff member available what condition, if any, prompted the original discount.
- Write the exception, the rate and the account, in the first column of the one-page record.
- Write the rule behind it, such as order frequency or account age, in the second column, based on the best available explanation.
- Name the role authorized to approve or revoke this type of exception in the third column.
- Set a review date, such as the next quarterly check, to confirm the rule still applies.
- Share the completed row with anyone who quotes that account going forward.
Result: A single row exists that any staff member can read to understand why the account’s rate differs from list price, and whether that reason still holds. The test of success is whether a new hire could quote that account correctly without asking a supervisor.
Common mistake: Recording the exception without recording the rule, which leaves the discount in place indefinitely with no condition for revisiting it. Fix this by requiring a rule field to be filled before the exception is considered logged.
If it goes wrong: If no one can reconstruct a plausible rule for an old exception, flag it for a direct conversation with the customer rather than guessing or silently discontinuing it.
This is a general illustration of the method, not a specific client result.
FAQs
How do I know if I have a pricing exceptions problem?
A pricing exceptions problem exists if two staff members would quote the same customer or job differently, or if no one can explain why a current customer pays less than list price. A quick test is to pick three active discounts at random and ask whoever is on shift to explain the reason for each. If the answer is a shrug or a guess, the reason exists in someone’s memory and not in writing.
What is a pricing exception in business terms?
A pricing exception is any price charged that differs from the published or standard list price, along with the specific condition that justified the difference. It covers repeat-customer discounts, rush-work pricing, and adjustments for special requests. The term describes the deviation and its reason together, not just the lower or higher number.
Why does undocumented pricing create confusion for customers?
Undocumented pricing creates confusion because two customers in similar situations can receive different quotes with no visible reason, and a customer who later compares notes with another has no explanation to accept. The confusion comes from the absence of a stated condition that would make the difference make sense.
Should every discount be written down, even small ones?
Yes, even small discounts should be logged if they recur, because a small exception repeated across many customers adds up to inconsistent pricing at scale. A one-time, trivial adjustment made for a single order does not need a permanent record, but any discount likely to be requested again does.
Who should set the rule behind a pricing exception?
The rule should be set by whoever has approval authority for that category of exception, documented clearly enough that a different person could apply it the same way. This keeps the decision from drifting with staff turnover or memory loss over time.
Does writing down pricing exceptions mean I have to standardize all my pricing?
No, documenting exceptions does not require standardizing every price across the board. The one-page format is neutral on how much to discount or whether to discount at all. It only requires that whatever rate is charged has a stated reason and a named approver attached to it.
How often should a pricing exceptions record be reviewed?
A quarterly review is a reasonable starting point, catching exceptions whose original condition, such as order frequency or a one-time rush job, no longer applies. Businesses with high order volume or frequent custom requests may need a shorter review cycle to keep the record current.
Next Steps
Writing down the rule behind a pricing exception takes less time than resolving the confusion it prevents. Save this format for the next time you quote an exception, so the next person who prices that customer or that job has something more reliable than a memory to work from.
