Your Pricing Problem Is a Product-Data Problem: Reps Override When the Catalog Can't Defend the Price

Your reps aren't overriding list price because they're undisciplined, and a pricing engine won't fix what's actually broken. They override because the product page behind the price gives them nothing to sell against — and a spec-thin SKU is, functionally, a commodity. Before you shop for pricing software, pull your top 50 override lines and look at the catalog pages underneath them. You'll find the real problem.

The exception layer is a symptom, not the disease

Distribution Strategy Group has spent the back half of 2026 on this exact pain point, and it's the right pain point. Their June piece on the exception layer makes a sharp observation: temporary discounts don't get reviewed, they just age into policy, until the exception list quietly becomes the real price book. Their fix is procedural — an aging report, a 60-day renewal clock, a cross-functional council that has to actively bless every holdover discount.

That's good hygiene. It will claw back some margin. It will not touch the reason the exceptions started.

Their January piece gets closer to the root cause and then swerves away from it. It argues reps override system pricing with their own cost-plus math because the pricing strategy "lacks credibility" — and the prescription is executive sponsorship, a dedicated pricing hire, AI tooling to manage special-pricing authorizations. All defensible. But "lacks credibility" is doing a lot of work in that sentence, and the piece never asks the more uncomfortable question: credible to whom, and defended with what?

A rep doesn't lose confidence in a price because leadership failed to hold a kickoff meeting. A rep loses confidence in a price when a customer pulls up a competitor's page mid-call and the two listings look identical — same generic title, four spec fields, one stock photo — except the other guy is $4 cheaper. At that moment the rep isn't defending a strategy. They're defending a blank page. And a blank page loses every time.

What the override actually measures

Run this test on your own catalog. Pick the SKUs with the highest override frequency over the last two quarters. Now pull up those product pages. Our bet — and it's a testable one, not a hunch — is that they cluster hard on thin data: bare part numbers instead of descriptive titles, five or six attributes where a comparable line has thirty, no application or compatibility language, one image.

That's not a coincidence, and it's not really about discipline. When a page can't tell a buyer why this SKU is worth the number on it — the tolerance, the certification, the compatibility with the exact system they're installing it into — the buyer treats it as interchangeable with the cheapest interchangeable thing they can find. The rep feels that pressure on the phone before finance ever sees it in the margin report. The override is the rep pricing the SKU the way the page priced it: as a commodity.

McKinsey has called pricing distributors' single most powerful value-creation lever, and the arithmetic explains why override culture is so expensive to ignore: at an 18% gross margin, a 1% price concession requires roughly 6% more volume just to break even, while distributors that build real pricing capability have captured 200 to 500 basis points of margin uplift. That math is the entire business case for fixing this. It says nothing about which lever to pull first.

Separately, industry pricing analyses put override volume at 20% to 50% of revenue at a typical distributor, at a 500-to-1,000-basis-point margin delta versus system price — which is a bigger number than most finance teams admit to a board. If your exception rate is in that range, you don't have a discipline problem confined to a handful of reps. You have a structural one, and it's worth asking what's structurally different about the SKUs that get overridden versus the ones that don't.

Catalog consistency is the tell

There's a second layer to this that pricing-software vendors never mention, because it isn't in their product: consistency. A catalog where the flagship SKUs are richly specced and the long tail is nearly blank doesn't just under-price the long tail — it teaches every rep working that catalog that data quality is negotiable, and negotiable data quality trains negotiable pricing behavior. We built a signal for exactly this into the Digital Readiness Index behind our Top Distributors 2026 index: it measures the spread between a company's richest and thinnest product page, on the theory that internal variance is as diagnostic as the average. A three-attribute spread scores full marks. A twenty-attribute spread scores zero. Distributors that hold that spread tight tend to be the same ones whose reps aren't improvising prices SKU by SKU — because the catalog isn't improvising the SKU's identity either.

The index's Product Data Depth pillar scores attribute count directly, half a point per structured attribute up to thirty, precisely because attribute count is the number the channel most consistently under-invests in. We didn't build that signal with pricing in mind. But watch what happens when you cross-reference it against override behavior at any distributor willing to share both numbers: the correlation is not subtle. Thin-attribute catalogs and high override rates travel together, for the same reason cheap-looking product pages and price shopping travel together everywhere else in commerce.

Buy the engine second

None of this is an argument against pricing software. Good pricing tooling — segmentation, guardrails, approval workflows — is real infrastructure, and most distributors under-invest in it. But sequence matters. A pricing engine layered on top of a catalog that can't defend its own SKUs just automates the override at machine speed: same guessed price, faster approval, better-looking dashboard, same margin leak. The exception-aging report DSG proposes will catch some of that leakage after the fact. It won't stop a rep from needing an exception in the first place.

The cheaper, faster fix runs the other direction. Fix attribute coverage and description depth on your highest-override SKUs before you shop for a pricing platform, and re-run the override report. If the catalog fix moves the number — and in our experience with distributor data it moves fast — you've just learned your pricing problem was a data problem wearing a pricing problem's clothes, and you saved yourself a platform migration to find that out.

Anglera's whole job is that fix: adding the attributes, spec depth, and structured data a PIM already stores space for but never gets filled in, without replacing whatever pricing or catalog system runs on top of it. Your reps aren't the exception layer. Your catalog is. Fix the page, and watch what happens to the override rate before you sign anything else.